2008-06-27 22:56:22 +00:00
|
|
|
/*
|
|
|
|
|
* arch/arm/mach-orion5x/rd88f5181l-fxo-setup.c
|
|
|
|
|
*
|
|
|
|
|
* Marvell Orion-VoIP FXO Reference Design Setup
|
|
|
|
|
*
|
|
|
|
|
* This file is licensed under the terms of the GNU General Public
|
|
|
|
|
* License version 2. This program is licensed "as is" without any
|
|
|
|
|
* warranty of any kind, whether express or implied.
|
|
|
|
|
*/
|
2011-07-26 09:53:52 +00:00
|
|
|
#include <linux/gpio.h>
|
2008-06-27 22:56:22 +00:00
|
|
|
#include <linux/kernel.h>
|
|
|
|
|
#include <linux/init.h>
|
|
|
|
|
#include <linux/platform_device.h>
|
|
|
|
|
#include <linux/pci.h>
|
|
|
|
|
#include <linux/irq.h>
|
|
|
|
|
#include <linux/mtd/physmap.h>
|
|
|
|
|
#include <linux/mv643xx_eth.h>
|
2008-07-14 12:29:40 +00:00
|
|
|
#include <linux/ethtool.h>
|
2008-09-25 14:23:48 +00:00
|
|
|
#include <net/dsa.h>
|
2008-06-27 22:56:22 +00:00
|
|
|
#include <asm/mach-types.h>
|
|
|
|
|
#include <asm/mach/arch.h>
|
|
|
|
|
#include <asm/mach/pci.h>
|
2008-08-05 15:14:15 +00:00
|
|
|
#include <mach/orion5x.h>
|
2008-06-27 22:56:22 +00:00
|
|
|
#include "common.h"
|
|
|
|
|
#include "mpp.h"
|
|
|
|
|
|
|
|
|
|
/*****************************************************************************
|
|
|
|
|
* RD-88F5181L FXO Info
|
|
|
|
|
****************************************************************************/
|
|
|
|
|
/*
|
|
|
|
|
* 8M NOR flash Device bus boot chip select
|
|
|
|
|
*/
|
|
|
|
|
#define RD88F5181L_FXO_NOR_BOOT_BASE 0xff800000
|
|
|
|
|
#define RD88F5181L_FXO_NOR_BOOT_SIZE SZ_8M
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*****************************************************************************
|
|
|
|
|
* 8M NOR Flash on Device bus Boot chip select
|
|
|
|
|
****************************************************************************/
|
|
|
|
|
static struct physmap_flash_data rd88f5181l_fxo_nor_boot_flash_data = {
|
|
|
|
|
.width = 1,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static struct resource rd88f5181l_fxo_nor_boot_flash_resource = {
|
|
|
|
|
.flags = IORESOURCE_MEM,
|
|
|
|
|
.start = RD88F5181L_FXO_NOR_BOOT_BASE,
|
|
|
|
|
.end = RD88F5181L_FXO_NOR_BOOT_BASE +
|
|
|
|
|
RD88F5181L_FXO_NOR_BOOT_SIZE - 1,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static struct platform_device rd88f5181l_fxo_nor_boot_flash = {
|
|
|
|
|
.name = "physmap-flash",
|
|
|
|
|
.id = 0,
|
|
|
|
|
.dev = {
|
|
|
|
|
.platform_data = &rd88f5181l_fxo_nor_boot_flash_data,
|
|
|
|
|
},
|
|
|
|
|
.num_resources = 1,
|
|
|
|
|
.resource = &rd88f5181l_fxo_nor_boot_flash_resource,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*****************************************************************************
|
|
|
|
|
* General Setup
|
|
|
|
|
****************************************************************************/
|
2011-05-15 11:32:53 +00:00
|
|
|
static unsigned int rd88f5181l_fxo_mpp_modes[] __initdata = {
|
|
|
|
|
MPP0_GPIO, /* LED1 CardBus LED (front panel) */
|
|
|
|
|
MPP1_GPIO, /* PCI_intA */
|
|
|
|
|
MPP2_GPIO, /* Hard Reset / Factory Init*/
|
|
|
|
|
MPP3_GPIO, /* FXS or DAA select */
|
|
|
|
|
MPP4_GPIO, /* LED6 - phone LED (front panel) */
|
|
|
|
|
MPP5_GPIO, /* LED5 - phone LED (front panel) */
|
|
|
|
|
MPP6_PCI_CLK, /* CPU PCI refclk */
|
|
|
|
|
MPP7_PCI_CLK, /* PCI/PCIe refclk */
|
|
|
|
|
MPP8_GPIO, /* CardBus reset */
|
|
|
|
|
MPP9_GPIO, /* GE_RXERR */
|
|
|
|
|
MPP10_GPIO, /* LED2 MiniPCI LED (front panel) */
|
|
|
|
|
MPP11_GPIO, /* Lifeline control */
|
|
|
|
|
MPP12_GIGE, /* GE_TXD[4] */
|
|
|
|
|
MPP13_GIGE, /* GE_TXD[5] */
|
|
|
|
|
MPP14_GIGE, /* GE_TXD[6] */
|
|
|
|
|
MPP15_GIGE, /* GE_TXD[7] */
|
|
|
|
|
MPP16_GIGE, /* GE_RXD[4] */
|
|
|
|
|
MPP17_GIGE, /* GE_RXD[5] */
|
|
|
|
|
MPP18_GIGE, /* GE_RXD[6] */
|
|
|
|
|
MPP19_GIGE, /* GE_RXD[7] */
|
|
|
|
|
0,
|
2008-06-27 22:56:22 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static struct mv643xx_eth_platform_data rd88f5181l_fxo_eth_data = {
|
2008-08-26 12:06:47 +00:00
|
|
|
.phy_addr = MV643XX_ETH_PHY_NONE,
|
2008-07-14 12:29:40 +00:00
|
|
|
.speed = SPEED_1000,
|
|
|
|
|
.duplex = DUPLEX_FULL,
|
2008-06-27 22:56:22 +00:00
|
|
|
};
|
|
|
|
|
|
dsa: add switch chip cascading support
The initial version of the DSA driver only supported a single switch
chip per network interface, while DSA-capable switch chips can be
interconnected to form a tree of switch chips. This patch adds support
for multiple switch chips on a network interface.
An example topology for a 16-port device with an embedded CPU is as
follows:
+-----+ +--------+ +--------+
| |eth0 10| switch |9 10| switch |
| CPU +----------+ +-------+ |
| | | chip 0 | | chip 1 |
+-----+ +---++---+ +---++---+
|| ||
|| ||
||1000baseT ||1000baseT
||ports 1-8 ||ports 9-16
This requires a couple of interdependent changes in the DSA layer:
- The dsa platform driver data needs to be extended: there is still
only one netdevice per DSA driver instance (eth0 in the example
above), but each of the switch chips in the tree needs its own
mii_bus device pointer, MII management bus address, and port name
array. (include/net/dsa.h) The existing in-tree dsa users need
some small changes to deal with this. (arch/arm)
- The DSA and Ethertype DSA tagging modules need to be extended to
use the DSA device ID field on receive and demultiplex the packet
accordingly, and fill in the DSA device ID field on transmit
according to which switch chip the packet is heading to.
(net/dsa/tag_{dsa,edsa}.c)
- The concept of "CPU port", which is the switch chip port that the
CPU is connected to (port 10 on switch chip 0 in the example), needs
to be extended with the concept of "upstream port", which is the
port on the switch chip that will bring us one hop closer to the CPU
(port 10 for both switch chips in the example above).
- The dsa platform data needs to specify which ports on which switch
chips are links to other switch chips, so that we can enable DSA
tagging mode on them. (For inter-switch links, we always use
non-EtherType DSA tagging, since it has lower overhead. The CPU
link uses dsa or edsa tagging depending on what the 'root' switch
chip supports.) This is done by specifying "dsa" for the given
port in the port array.
- The dsa platform data needs to be extended with information on via
which port to reach any given switch chip from any given switch chip.
This info is specified via the per-switch chip data struct ->rtable[]
array, which gives the nexthop ports for each of the other switches
in the tree.
For the example topology above, the dsa platform data would look
something like this:
static struct dsa_chip_data sw[2] = {
{
.mii_bus = &foo,
.sw_addr = 1,
.port_names[0] = "p1",
.port_names[1] = "p2",
.port_names[2] = "p3",
.port_names[3] = "p4",
.port_names[4] = "p5",
.port_names[5] = "p6",
.port_names[6] = "p7",
.port_names[7] = "p8",
.port_names[9] = "dsa",
.port_names[10] = "cpu",
.rtable = (s8 []){ -1, 9, },
}, {
.mii_bus = &foo,
.sw_addr = 2,
.port_names[0] = "p9",
.port_names[1] = "p10",
.port_names[2] = "p11",
.port_names[3] = "p12",
.port_names[4] = "p13",
.port_names[5] = "p14",
.port_names[6] = "p15",
.port_names[7] = "p16",
.port_names[10] = "dsa",
.rtable = (s8 []){ 10, -1, },
},
},
static struct dsa_platform_data pd = {
.netdev = &foo,
.nr_switches = 2,
.sw = sw,
};
Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Tested-by: Gary Thomas <gary@mlbassoc.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2009-03-20 09:52:09 +00:00
|
|
|
static struct dsa_chip_data rd88f5181l_fxo_switch_chip_data = {
|
2008-09-25 14:23:48 +00:00
|
|
|
.port_names[0] = "lan2",
|
|
|
|
|
.port_names[1] = "lan1",
|
|
|
|
|
.port_names[2] = "wan",
|
|
|
|
|
.port_names[3] = "cpu",
|
|
|
|
|
.port_names[5] = "lan4",
|
|
|
|
|
.port_names[7] = "lan3",
|
|
|
|
|
};
|
|
|
|
|
|
dsa: add switch chip cascading support
The initial version of the DSA driver only supported a single switch
chip per network interface, while DSA-capable switch chips can be
interconnected to form a tree of switch chips. This patch adds support
for multiple switch chips on a network interface.
An example topology for a 16-port device with an embedded CPU is as
follows:
+-----+ +--------+ +--------+
| |eth0 10| switch |9 10| switch |
| CPU +----------+ +-------+ |
| | | chip 0 | | chip 1 |
+-----+ +---++---+ +---++---+
|| ||
|| ||
||1000baseT ||1000baseT
||ports 1-8 ||ports 9-16
This requires a couple of interdependent changes in the DSA layer:
- The dsa platform driver data needs to be extended: there is still
only one netdevice per DSA driver instance (eth0 in the example
above), but each of the switch chips in the tree needs its own
mii_bus device pointer, MII management bus address, and port name
array. (include/net/dsa.h) The existing in-tree dsa users need
some small changes to deal with this. (arch/arm)
- The DSA and Ethertype DSA tagging modules need to be extended to
use the DSA device ID field on receive and demultiplex the packet
accordingly, and fill in the DSA device ID field on transmit
according to which switch chip the packet is heading to.
(net/dsa/tag_{dsa,edsa}.c)
- The concept of "CPU port", which is the switch chip port that the
CPU is connected to (port 10 on switch chip 0 in the example), needs
to be extended with the concept of "upstream port", which is the
port on the switch chip that will bring us one hop closer to the CPU
(port 10 for both switch chips in the example above).
- The dsa platform data needs to specify which ports on which switch
chips are links to other switch chips, so that we can enable DSA
tagging mode on them. (For inter-switch links, we always use
non-EtherType DSA tagging, since it has lower overhead. The CPU
link uses dsa or edsa tagging depending on what the 'root' switch
chip supports.) This is done by specifying "dsa" for the given
port in the port array.
- The dsa platform data needs to be extended with information on via
which port to reach any given switch chip from any given switch chip.
This info is specified via the per-switch chip data struct ->rtable[]
array, which gives the nexthop ports for each of the other switches
in the tree.
For the example topology above, the dsa platform data would look
something like this:
static struct dsa_chip_data sw[2] = {
{
.mii_bus = &foo,
.sw_addr = 1,
.port_names[0] = "p1",
.port_names[1] = "p2",
.port_names[2] = "p3",
.port_names[3] = "p4",
.port_names[4] = "p5",
.port_names[5] = "p6",
.port_names[6] = "p7",
.port_names[7] = "p8",
.port_names[9] = "dsa",
.port_names[10] = "cpu",
.rtable = (s8 []){ -1, 9, },
}, {
.mii_bus = &foo,
.sw_addr = 2,
.port_names[0] = "p9",
.port_names[1] = "p10",
.port_names[2] = "p11",
.port_names[3] = "p12",
.port_names[4] = "p13",
.port_names[5] = "p14",
.port_names[6] = "p15",
.port_names[7] = "p16",
.port_names[10] = "dsa",
.rtable = (s8 []){ 10, -1, },
},
},
static struct dsa_platform_data pd = {
.netdev = &foo,
.nr_switches = 2,
.sw = sw,
};
Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Tested-by: Gary Thomas <gary@mlbassoc.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2009-03-20 09:52:09 +00:00
|
|
|
static struct dsa_platform_data rd88f5181l_fxo_switch_plat_data = {
|
|
|
|
|
.nr_chips = 1,
|
|
|
|
|
.chip = &rd88f5181l_fxo_switch_chip_data,
|
|
|
|
|
};
|
|
|
|
|
|
2008-06-27 22:56:22 +00:00
|
|
|
static void __init rd88f5181l_fxo_init(void)
|
|
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* Setup basic Orion functions. Need to be called early.
|
|
|
|
|
*/
|
|
|
|
|
orion5x_init();
|
|
|
|
|
|
|
|
|
|
orion5x_mpp_conf(rd88f5181l_fxo_mpp_modes);
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Configure peripherals.
|
|
|
|
|
*/
|
|
|
|
|
orion5x_ehci0_init();
|
|
|
|
|
orion5x_eth_init(&rd88f5181l_fxo_eth_data);
|
dsa: add switch chip cascading support
The initial version of the DSA driver only supported a single switch
chip per network interface, while DSA-capable switch chips can be
interconnected to form a tree of switch chips. This patch adds support
for multiple switch chips on a network interface.
An example topology for a 16-port device with an embedded CPU is as
follows:
+-----+ +--------+ +--------+
| |eth0 10| switch |9 10| switch |
| CPU +----------+ +-------+ |
| | | chip 0 | | chip 1 |
+-----+ +---++---+ +---++---+
|| ||
|| ||
||1000baseT ||1000baseT
||ports 1-8 ||ports 9-16
This requires a couple of interdependent changes in the DSA layer:
- The dsa platform driver data needs to be extended: there is still
only one netdevice per DSA driver instance (eth0 in the example
above), but each of the switch chips in the tree needs its own
mii_bus device pointer, MII management bus address, and port name
array. (include/net/dsa.h) The existing in-tree dsa users need
some small changes to deal with this. (arch/arm)
- The DSA and Ethertype DSA tagging modules need to be extended to
use the DSA device ID field on receive and demultiplex the packet
accordingly, and fill in the DSA device ID field on transmit
according to which switch chip the packet is heading to.
(net/dsa/tag_{dsa,edsa}.c)
- The concept of "CPU port", which is the switch chip port that the
CPU is connected to (port 10 on switch chip 0 in the example), needs
to be extended with the concept of "upstream port", which is the
port on the switch chip that will bring us one hop closer to the CPU
(port 10 for both switch chips in the example above).
- The dsa platform data needs to specify which ports on which switch
chips are links to other switch chips, so that we can enable DSA
tagging mode on them. (For inter-switch links, we always use
non-EtherType DSA tagging, since it has lower overhead. The CPU
link uses dsa or edsa tagging depending on what the 'root' switch
chip supports.) This is done by specifying "dsa" for the given
port in the port array.
- The dsa platform data needs to be extended with information on via
which port to reach any given switch chip from any given switch chip.
This info is specified via the per-switch chip data struct ->rtable[]
array, which gives the nexthop ports for each of the other switches
in the tree.
For the example topology above, the dsa platform data would look
something like this:
static struct dsa_chip_data sw[2] = {
{
.mii_bus = &foo,
.sw_addr = 1,
.port_names[0] = "p1",
.port_names[1] = "p2",
.port_names[2] = "p3",
.port_names[3] = "p4",
.port_names[4] = "p5",
.port_names[5] = "p6",
.port_names[6] = "p7",
.port_names[7] = "p8",
.port_names[9] = "dsa",
.port_names[10] = "cpu",
.rtable = (s8 []){ -1, 9, },
}, {
.mii_bus = &foo,
.sw_addr = 2,
.port_names[0] = "p9",
.port_names[1] = "p10",
.port_names[2] = "p11",
.port_names[3] = "p12",
.port_names[4] = "p13",
.port_names[5] = "p14",
.port_names[6] = "p15",
.port_names[7] = "p16",
.port_names[10] = "dsa",
.rtable = (s8 []){ 10, -1, },
},
},
static struct dsa_platform_data pd = {
.netdev = &foo,
.nr_switches = 2,
.sw = sw,
};
Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Tested-by: Gary Thomas <gary@mlbassoc.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2009-03-20 09:52:09 +00:00
|
|
|
orion5x_eth_switch_init(&rd88f5181l_fxo_switch_plat_data, NO_IRQ);
|
2008-06-27 22:56:22 +00:00
|
|
|
orion5x_uart0_init();
|
|
|
|
|
|
|
|
|
|
orion5x_setup_dev_boot_win(RD88F5181L_FXO_NOR_BOOT_BASE,
|
|
|
|
|
RD88F5181L_FXO_NOR_BOOT_SIZE);
|
|
|
|
|
platform_device_register(&rd88f5181l_fxo_nor_boot_flash);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int __init
|
2011-06-10 14:30:21 +00:00
|
|
|
rd88f5181l_fxo_pci_map_irq(const struct pci_dev *dev, u8 slot, u8 pin)
|
2008-06-27 22:56:22 +00:00
|
|
|
{
|
|
|
|
|
int irq;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Check for devices with hard-wired IRQs.
|
|
|
|
|
*/
|
|
|
|
|
irq = orion5x_pci_map_irq(dev, slot, pin);
|
|
|
|
|
if (irq != -1)
|
|
|
|
|
return irq;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Mini-PCI / Cardbus slot.
|
|
|
|
|
*/
|
|
|
|
|
return gpio_to_irq(1);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static struct hw_pci rd88f5181l_fxo_pci __initdata = {
|
|
|
|
|
.nr_controllers = 2,
|
|
|
|
|
.setup = orion5x_pci_sys_setup,
|
|
|
|
|
.scan = orion5x_pci_sys_scan_bus,
|
|
|
|
|
.map_irq = rd88f5181l_fxo_pci_map_irq,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static int __init rd88f5181l_fxo_pci_init(void)
|
|
|
|
|
{
|
|
|
|
|
if (machine_is_rd88f5181l_fxo()) {
|
|
|
|
|
orion5x_pci_set_cardbus_mode();
|
|
|
|
|
pci_common_init(&rd88f5181l_fxo_pci);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
subsys_initcall(rd88f5181l_fxo_pci_init);
|
|
|
|
|
|
|
|
|
|
MACHINE_START(RD88F5181L_FXO, "Marvell Orion-VoIP FXO Reference Design")
|
|
|
|
|
/* Maintainer: Nicolas Pitre <nico@marvell.com> */
|
2011-07-06 02:38:15 +00:00
|
|
|
.atag_offset = 0x100,
|
2008-06-27 22:56:22 +00:00
|
|
|
.init_machine = rd88f5181l_fxo_init,
|
|
|
|
|
.map_io = orion5x_map_io,
|
2010-10-15 14:50:26 +00:00
|
|
|
.init_early = orion5x_init_early,
|
2008-06-27 22:56:22 +00:00
|
|
|
.init_irq = orion5x_init_irq,
|
|
|
|
|
.timer = &orion5x_timer,
|
|
|
|
|
.fixup = tag_fixup_mem32,
|
2011-11-05 10:13:41 +00:00
|
|
|
.restart = orion5x_restart,
|
2008-06-27 22:56:22 +00:00
|
|
|
MACHINE_END
|
