2006-06-13 01:07:23 -06:00
|
|
|
/*
|
|
|
|
* tsi108/109 device setup code
|
|
|
|
*
|
|
|
|
* Maintained by Roy Zang < tie-fei.zang@freescale.com >
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify it
|
|
|
|
* under the terms of the GNU General Public License as published by the
|
|
|
|
* Free Software Foundation; either version 2 of the License, or (at your
|
|
|
|
* option) any later version.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/stddef.h>
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/errno.h>
|
|
|
|
#include <linux/major.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/irq.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/device.h>
|
|
|
|
#include <linux/platform_device.h>
|
|
|
|
#include <asm/tsi108.h>
|
|
|
|
|
|
|
|
#include <asm/system.h>
|
|
|
|
#include <asm/atomic.h>
|
|
|
|
#include <asm/io.h>
|
|
|
|
#include <asm/irq.h>
|
|
|
|
#include <asm/prom.h>
|
|
|
|
#include <mm/mmu_decl.h>
|
|
|
|
|
|
|
|
#undef DEBUG
|
|
|
|
|
|
|
|
#ifdef DEBUG
|
|
|
|
#define DBG(fmt...) do { printk(fmt); } while(0)
|
|
|
|
#else
|
|
|
|
#define DBG(fmt...) do { } while(0)
|
|
|
|
#endif
|
|
|
|
|
|
|
|
static phys_addr_t tsi108_csr_base = -1;
|
|
|
|
|
|
|
|
phys_addr_t get_csrbase(void)
|
|
|
|
{
|
|
|
|
struct device_node *tsi;
|
|
|
|
|
|
|
|
if (tsi108_csr_base != -1)
|
|
|
|
return tsi108_csr_base;
|
|
|
|
|
|
|
|
tsi = of_find_node_by_type(NULL, "tsi-bridge");
|
|
|
|
if (tsi) {
|
|
|
|
unsigned int size;
|
2007-04-03 06:26:41 -06:00
|
|
|
const void *prop = of_get_property(tsi, "reg", &size);
|
2006-06-13 01:07:23 -06:00
|
|
|
tsi108_csr_base = of_translate_address(tsi, prop);
|
|
|
|
of_node_put(tsi);
|
|
|
|
};
|
|
|
|
return tsi108_csr_base;
|
|
|
|
}
|
|
|
|
|
|
|
|
u32 get_vir_csrbase(void)
|
|
|
|
{
|
|
|
|
return (u32) (ioremap(get_csrbase(), 0x10000));
|
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(get_csrbase);
|
|
|
|
EXPORT_SYMBOL(get_vir_csrbase);
|
|
|
|
|
|
|
|
static int __init tsi108_eth_of_init(void)
|
|
|
|
{
|
|
|
|
struct device_node *np;
|
2007-11-29 12:44:36 -07:00
|
|
|
unsigned int i = 0;
|
2006-06-13 01:07:23 -06:00
|
|
|
struct platform_device *tsi_eth_dev;
|
|
|
|
struct resource res;
|
|
|
|
int ret;
|
|
|
|
|
2007-11-29 12:44:36 -07:00
|
|
|
for_each_compatible_node(np, "network", "tsi108-ethernet") {
|
2006-06-13 01:07:23 -06:00
|
|
|
struct resource r[2];
|
[POWERPC] Fix problems with device tree representation of TSI-1xx bridges
This fixes some problems with the way the some things
represented in the device tree for the Holly and Taiga boards. This
means changes both to the dts files, and to the code which
instantiates the tsi108 ethernet platform devices based on the device
tree.
- First, and most importantly, the ethernet PHYs are given
with an identical 'reg' property. This reg currently encodes the
accessible register used to initiate mdio interaction with the PHYs,
rather than a meaningful address on the parent bus (mdio in this
case), which is incorrect. Instead we give the address of these
registers as 'reg' in the mdio node itself, and encode the ID of each
phy in their 'reg' propertyies.
- Currently the platform device constructor enables a
workaround in the tsi108 ethernet driver based on the compatible
property of the PHY. This is incorrect, because the workaround in
question is necessary due to the board's wiring of the PHY, not the
model of PHY itself. This patch alters the constructor to instead
enable the workaround based on a new special property in the PHY node.
- The compatible properties on a number of nodes in the device
tree are insufficiently precise. In particular the PHYs give only
"bcm54xx", which is broken, since there are many bcm54xx PHY models,
and they have differences which matter. The mdio had a compatible
property of "tsi-ethernet" identical to the ethernet MAC nodes, which
doesn't make sense. The ethernet, i2c, bridge and PCI nodes were
given only as "tsi-*" which is somewhat inprecise, we replace with
"tsi108-*" in the case of Taiga (which has a TSI108 bridge), and
"tsi109-*", "tsi108-*" in the case of Holly (which has a TSI109
bridge).
- We remove some "model" properties from the ethernets on
Taiga board which were neither useful nor adequately precise.
- On Holly we change to using a dtc label instead of a full
path to reference the MPIC node, which makes the dts a little more
readable.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-06-12 22:53:00 -06:00
|
|
|
struct device_node *phy, *mdio;
|
2006-06-13 01:07:23 -06:00
|
|
|
hw_info tsi_eth_data;
|
2007-04-03 06:26:41 -06:00
|
|
|
const unsigned int *phy_id;
|
2006-10-17 21:18:58 -06:00
|
|
|
const void *mac_addr;
|
2007-04-03 06:26:41 -06:00
|
|
|
const phandle *ph;
|
2006-06-13 01:07:23 -06:00
|
|
|
|
|
|
|
memset(r, 0, sizeof(r));
|
|
|
|
memset(&tsi_eth_data, 0, sizeof(tsi_eth_data));
|
|
|
|
|
|
|
|
ret = of_address_to_resource(np, 0, &r[0]);
|
|
|
|
DBG("%s: name:start->end = %s:0x%lx-> 0x%lx\n",
|
|
|
|
__FUNCTION__,r[0].name, r[0].start, r[0].end);
|
|
|
|
if (ret)
|
|
|
|
goto err;
|
|
|
|
|
|
|
|
r[1].name = "tx";
|
2006-08-22 20:19:50 -06:00
|
|
|
r[1].start = irq_of_parse_and_map(np, 0);
|
|
|
|
r[1].end = irq_of_parse_and_map(np, 0);
|
2006-06-13 01:07:23 -06:00
|
|
|
r[1].flags = IORESOURCE_IRQ;
|
2006-08-22 20:19:50 -06:00
|
|
|
DBG("%s: name:start->end = %s:0x%lx-> 0x%lx\n",
|
|
|
|
__FUNCTION__,r[1].name, r[1].start, r[1].end);
|
2006-06-13 01:07:23 -06:00
|
|
|
|
|
|
|
tsi_eth_dev =
|
2007-11-29 12:44:36 -07:00
|
|
|
platform_device_register_simple("tsi-ethernet", i++, &r[0],
|
2006-08-22 20:19:50 -06:00
|
|
|
1);
|
2006-06-13 01:07:23 -06:00
|
|
|
|
|
|
|
if (IS_ERR(tsi_eth_dev)) {
|
|
|
|
ret = PTR_ERR(tsi_eth_dev);
|
|
|
|
goto err;
|
|
|
|
}
|
|
|
|
|
2007-05-07 15:26:22 -06:00
|
|
|
mac_addr = of_get_mac_address(np);
|
|
|
|
if (mac_addr)
|
|
|
|
memcpy(tsi_eth_data.mac_addr, mac_addr, 6);
|
2006-06-13 01:07:23 -06:00
|
|
|
|
[POWERPC] Fix problems with device tree representation of TSI-1xx bridges
This fixes some problems with the way the some things
represented in the device tree for the Holly and Taiga boards. This
means changes both to the dts files, and to the code which
instantiates the tsi108 ethernet platform devices based on the device
tree.
- First, and most importantly, the ethernet PHYs are given
with an identical 'reg' property. This reg currently encodes the
accessible register used to initiate mdio interaction with the PHYs,
rather than a meaningful address on the parent bus (mdio in this
case), which is incorrect. Instead we give the address of these
registers as 'reg' in the mdio node itself, and encode the ID of each
phy in their 'reg' propertyies.
- Currently the platform device constructor enables a
workaround in the tsi108 ethernet driver based on the compatible
property of the PHY. This is incorrect, because the workaround in
question is necessary due to the board's wiring of the PHY, not the
model of PHY itself. This patch alters the constructor to instead
enable the workaround based on a new special property in the PHY node.
- The compatible properties on a number of nodes in the device
tree are insufficiently precise. In particular the PHYs give only
"bcm54xx", which is broken, since there are many bcm54xx PHY models,
and they have differences which matter. The mdio had a compatible
property of "tsi-ethernet" identical to the ethernet MAC nodes, which
doesn't make sense. The ethernet, i2c, bridge and PCI nodes were
given only as "tsi-*" which is somewhat inprecise, we replace with
"tsi108-*" in the case of Taiga (which has a TSI108 bridge), and
"tsi109-*", "tsi108-*" in the case of Holly (which has a TSI109
bridge).
- We remove some "model" properties from the ethernets on
Taiga board which were neither useful nor adequately precise.
- On Holly we change to using a dtc label instead of a full
path to reference the MPIC node, which makes the dts a little more
readable.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-06-12 22:53:00 -06:00
|
|
|
ph = of_get_property(np, "mdio-handle", NULL);
|
|
|
|
mdio = of_find_node_by_phandle(*ph);
|
|
|
|
ret = of_address_to_resource(mdio, 0, &res);
|
|
|
|
of_node_put(mdio);
|
|
|
|
if (ret)
|
|
|
|
goto unreg;
|
|
|
|
|
2007-04-03 06:26:41 -06:00
|
|
|
ph = of_get_property(np, "phy-handle", NULL);
|
2006-06-13 01:07:23 -06:00
|
|
|
phy = of_find_node_by_phandle(*ph);
|
|
|
|
|
|
|
|
if (phy == NULL) {
|
|
|
|
ret = -ENODEV;
|
|
|
|
goto unreg;
|
|
|
|
}
|
|
|
|
|
[POWERPC] Fix problems with device tree representation of TSI-1xx bridges
This fixes some problems with the way the some things
represented in the device tree for the Holly and Taiga boards. This
means changes both to the dts files, and to the code which
instantiates the tsi108 ethernet platform devices based on the device
tree.
- First, and most importantly, the ethernet PHYs are given
with an identical 'reg' property. This reg currently encodes the
accessible register used to initiate mdio interaction with the PHYs,
rather than a meaningful address on the parent bus (mdio in this
case), which is incorrect. Instead we give the address of these
registers as 'reg' in the mdio node itself, and encode the ID of each
phy in their 'reg' propertyies.
- Currently the platform device constructor enables a
workaround in the tsi108 ethernet driver based on the compatible
property of the PHY. This is incorrect, because the workaround in
question is necessary due to the board's wiring of the PHY, not the
model of PHY itself. This patch alters the constructor to instead
enable the workaround based on a new special property in the PHY node.
- The compatible properties on a number of nodes in the device
tree are insufficiently precise. In particular the PHYs give only
"bcm54xx", which is broken, since there are many bcm54xx PHY models,
and they have differences which matter. The mdio had a compatible
property of "tsi-ethernet" identical to the ethernet MAC nodes, which
doesn't make sense. The ethernet, i2c, bridge and PCI nodes were
given only as "tsi-*" which is somewhat inprecise, we replace with
"tsi108-*" in the case of Taiga (which has a TSI108 bridge), and
"tsi109-*", "tsi108-*" in the case of Holly (which has a TSI109
bridge).
- We remove some "model" properties from the ethernets on
Taiga board which were neither useful nor adequately precise.
- On Holly we change to using a dtc label instead of a full
path to reference the MPIC node, which makes the dts a little more
readable.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-06-12 22:53:00 -06:00
|
|
|
phy_id = of_get_property(phy, "reg", NULL);
|
|
|
|
|
2006-06-13 01:07:23 -06:00
|
|
|
tsi_eth_data.regs = r[0].start;
|
|
|
|
tsi_eth_data.phyregs = res.start;
|
|
|
|
tsi_eth_data.phy = *phy_id;
|
2006-08-22 20:19:50 -06:00
|
|
|
tsi_eth_data.irq_num = irq_of_parse_and_map(np, 0);
|
[POWERPC] Fix problems with device tree representation of TSI-1xx bridges
This fixes some problems with the way the some things
represented in the device tree for the Holly and Taiga boards. This
means changes both to the dts files, and to the code which
instantiates the tsi108 ethernet platform devices based on the device
tree.
- First, and most importantly, the ethernet PHYs are given
with an identical 'reg' property. This reg currently encodes the
accessible register used to initiate mdio interaction with the PHYs,
rather than a meaningful address on the parent bus (mdio in this
case), which is incorrect. Instead we give the address of these
registers as 'reg' in the mdio node itself, and encode the ID of each
phy in their 'reg' propertyies.
- Currently the platform device constructor enables a
workaround in the tsi108 ethernet driver based on the compatible
property of the PHY. This is incorrect, because the workaround in
question is necessary due to the board's wiring of the PHY, not the
model of PHY itself. This patch alters the constructor to instead
enable the workaround based on a new special property in the PHY node.
- The compatible properties on a number of nodes in the device
tree are insufficiently precise. In particular the PHYs give only
"bcm54xx", which is broken, since there are many bcm54xx PHY models,
and they have differences which matter. The mdio had a compatible
property of "tsi-ethernet" identical to the ethernet MAC nodes, which
doesn't make sense. The ethernet, i2c, bridge and PCI nodes were
given only as "tsi-*" which is somewhat inprecise, we replace with
"tsi108-*" in the case of Taiga (which has a TSI108 bridge), and
"tsi109-*", "tsi108-*" in the case of Holly (which has a TSI109
bridge).
- We remove some "model" properties from the ethernets on
Taiga board which were neither useful nor adequately precise.
- On Holly we change to using a dtc label instead of a full
path to reference the MPIC node, which makes the dts a little more
readable.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-06-12 22:53:00 -06:00
|
|
|
|
|
|
|
/* Some boards with the TSI108 bridge (e.g. Holly)
|
|
|
|
* have a miswiring of the ethernet PHYs which
|
|
|
|
* requires a workaround. The special
|
|
|
|
* "txc-rxc-delay-disable" property enables this
|
|
|
|
* workaround. FIXME: Need to port the tsi108_eth
|
|
|
|
* driver itself to phylib and use a non-misleading
|
|
|
|
* name for the workaround flag - it's not actually to
|
|
|
|
* do with the model of PHY in use */
|
|
|
|
if (of_get_property(phy, "txc-rxc-delay-disable", NULL))
|
2007-05-07 15:26:22 -06:00
|
|
|
tsi_eth_data.phy_type = TSI108_PHY_BCM54XX;
|
2006-06-13 01:07:23 -06:00
|
|
|
of_node_put(phy);
|
[POWERPC] Fix problems with device tree representation of TSI-1xx bridges
This fixes some problems with the way the some things
represented in the device tree for the Holly and Taiga boards. This
means changes both to the dts files, and to the code which
instantiates the tsi108 ethernet platform devices based on the device
tree.
- First, and most importantly, the ethernet PHYs are given
with an identical 'reg' property. This reg currently encodes the
accessible register used to initiate mdio interaction with the PHYs,
rather than a meaningful address on the parent bus (mdio in this
case), which is incorrect. Instead we give the address of these
registers as 'reg' in the mdio node itself, and encode the ID of each
phy in their 'reg' propertyies.
- Currently the platform device constructor enables a
workaround in the tsi108 ethernet driver based on the compatible
property of the PHY. This is incorrect, because the workaround in
question is necessary due to the board's wiring of the PHY, not the
model of PHY itself. This patch alters the constructor to instead
enable the workaround based on a new special property in the PHY node.
- The compatible properties on a number of nodes in the device
tree are insufficiently precise. In particular the PHYs give only
"bcm54xx", which is broken, since there are many bcm54xx PHY models,
and they have differences which matter. The mdio had a compatible
property of "tsi-ethernet" identical to the ethernet MAC nodes, which
doesn't make sense. The ethernet, i2c, bridge and PCI nodes were
given only as "tsi-*" which is somewhat inprecise, we replace with
"tsi108-*" in the case of Taiga (which has a TSI108 bridge), and
"tsi109-*", "tsi108-*" in the case of Holly (which has a TSI109
bridge).
- We remove some "model" properties from the ethernets on
Taiga board which were neither useful nor adequately precise.
- On Holly we change to using a dtc label instead of a full
path to reference the MPIC node, which makes the dts a little more
readable.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2007-06-12 22:53:00 -06:00
|
|
|
|
2006-06-13 01:07:23 -06:00
|
|
|
ret =
|
|
|
|
platform_device_add_data(tsi_eth_dev, &tsi_eth_data,
|
|
|
|
sizeof(hw_info));
|
|
|
|
if (ret)
|
|
|
|
goto unreg;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
unreg:
|
|
|
|
platform_device_unregister(tsi_eth_dev);
|
|
|
|
err:
|
2007-11-29 12:44:36 -07:00
|
|
|
of_node_put(np);
|
2006-06-13 01:07:23 -06:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
arch_initcall(tsi108_eth_of_init);
|