2006-08-25 08:43:25 +00:00
|
|
|
/*
|
|
|
|
|
* MPC7448HPC2 (Taiga) board Device Tree Source
|
|
|
|
|
*
|
2008-04-17 14:40:48 +00:00
|
|
|
* Copyright 2006, 2008 Freescale Semiconductor Inc.
|
2006-08-25 08:43:25 +00:00
|
|
|
* 2006 Roy Zang <Roy Zang at 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.
|
|
|
|
|
*/
|
|
|
|
|
|
2008-04-17 14:40:48 +00:00
|
|
|
/dts-v1/;
|
2006-08-25 08:43:25 +00:00
|
|
|
|
|
|
|
|
/ {
|
|
|
|
|
model = "mpc7448hpc2";
|
|
|
|
|
compatible = "mpc74xx";
|
|
|
|
|
#address-cells = <1>;
|
|
|
|
|
#size-cells = <1>;
|
|
|
|
|
|
2008-07-10 20:21:35 +00:00
|
|
|
aliases {
|
|
|
|
|
ethernet0 = &enet0;
|
|
|
|
|
ethernet1 = &enet1;
|
|
|
|
|
|
|
|
|
|
serial0 = &serial0;
|
|
|
|
|
serial1 = &serial1;
|
|
|
|
|
|
|
|
|
|
pci0 = &pci0;
|
|
|
|
|
};
|
|
|
|
|
|
2006-08-25 08:43:25 +00:00
|
|
|
cpus {
|
|
|
|
|
#address-cells = <1>;
|
|
|
|
|
#size-cells =<0>;
|
|
|
|
|
|
|
|
|
|
PowerPC,7448@0 {
|
|
|
|
|
device_type = "cpu";
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x0>;
|
|
|
|
|
d-cache-line-size = <32>; // 32 bytes
|
|
|
|
|
i-cache-line-size = <32>; // 32 bytes
|
|
|
|
|
d-cache-size = <0x8000>; // L1, 32K bytes
|
|
|
|
|
i-cache-size = <0x8000>; // L1, 32K bytes
|
2006-08-25 08:43:25 +00:00
|
|
|
timebase-frequency = <0>; // 33 MHz, from uboot
|
|
|
|
|
clock-frequency = <0>; // From U-Boot
|
|
|
|
|
bus-frequency = <0>; // From U-Boot
|
|
|
|
|
};
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
memory {
|
|
|
|
|
device_type = "memory";
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x0 0x20000000 // DDR2 512M at 0
|
2006-08-25 08:43:25 +00:00
|
|
|
>;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
tsi108@c0000000 {
|
|
|
|
|
#address-cells = <1>;
|
|
|
|
|
#size-cells = <1>;
|
2007-07-11 06:39:17 +00:00
|
|
|
device_type = "tsi-bridge";
|
2008-04-17 14:40:48 +00:00
|
|
|
ranges = <0x0 0xc0000000 0x10000>;
|
|
|
|
|
reg = <0xc0000000 0x10000>;
|
2006-08-25 08:43:25 +00:00
|
|
|
bus-frequency = <0>;
|
|
|
|
|
|
|
|
|
|
i2c@7000 {
|
2007-05-15 21:12:27 +00:00
|
|
|
interrupt-parent = <&mpic>;
|
2008-04-17 14:40:48 +00:00
|
|
|
interrupts = <14 0>;
|
|
|
|
|
reg = <0x7000 0x400>;
|
2006-08-25 08:43:25 +00:00
|
|
|
device_type = "i2c";
|
[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-13 04:53:00 +00:00
|
|
|
compatible = "tsi108-i2c";
|
2006-08-25 08:43:25 +00: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-13 04:53:00 +00:00
|
|
|
MDIO: mdio@6000 {
|
2006-08-25 08:43:25 +00:00
|
|
|
device_type = "mdio";
|
[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-13 04:53:00 +00:00
|
|
|
compatible = "tsi108-mdio";
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x6000 0x50>;
|
[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-13 04:53:00 +00:00
|
|
|
#address-cells = <1>;
|
|
|
|
|
#size-cells = <0>;
|
2006-08-25 08:43:25 +00: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-13 04:53:00 +00:00
|
|
|
phy8: ethernet-phy@8 {
|
2007-05-15 21:12:27 +00:00
|
|
|
interrupt-parent = <&mpic>;
|
2006-08-25 08:43:25 +00:00
|
|
|
interrupts = <2 1>;
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x8>;
|
2006-08-25 08:43:25 +00: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-13 04:53:00 +00:00
|
|
|
phy9: ethernet-phy@9 {
|
2007-05-15 21:12:27 +00:00
|
|
|
interrupt-parent = <&mpic>;
|
2006-08-25 08:43:25 +00:00
|
|
|
interrupts = <2 1>;
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x9>;
|
2006-08-25 08:43:25 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
};
|
|
|
|
|
|
2008-07-10 20:21:35 +00:00
|
|
|
enet0: ethernet@6200 {
|
2007-09-24 10:31:55 +00:00
|
|
|
linux,network-index = <0>;
|
2006-08-25 08:43:25 +00:00
|
|
|
#size-cells = <0>;
|
|
|
|
|
device_type = "network";
|
[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-13 04:53:00 +00:00
|
|
|
compatible = "tsi108-ethernet";
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x6000 0x200>;
|
2006-08-25 08:43:25 +00:00
|
|
|
address = [ 00 06 D2 00 00 01 ];
|
2008-04-17 14:40:48 +00:00
|
|
|
interrupts = <16 2>;
|
2007-05-15 21:12:27 +00:00
|
|
|
interrupt-parent = <&mpic>;
|
[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-13 04:53:00 +00:00
|
|
|
mdio-handle = <&MDIO>;
|
2007-05-15 21:12:27 +00:00
|
|
|
phy-handle = <&phy8>;
|
2006-08-25 08:43:25 +00:00
|
|
|
};
|
|
|
|
|
|
2008-07-10 20:21:35 +00:00
|
|
|
enet1: ethernet@6600 {
|
2007-09-24 10:31:55 +00:00
|
|
|
linux,network-index = <1>;
|
2006-08-25 08:43:25 +00:00
|
|
|
#address-cells = <1>;
|
|
|
|
|
#size-cells = <0>;
|
|
|
|
|
device_type = "network";
|
[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-13 04:53:00 +00:00
|
|
|
compatible = "tsi108-ethernet";
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x6400 0x200>;
|
2006-08-25 08:43:25 +00:00
|
|
|
address = [ 00 06 D2 00 00 02 ];
|
2008-04-17 14:40:48 +00:00
|
|
|
interrupts = <17 2>;
|
2007-05-15 21:12:27 +00:00
|
|
|
interrupt-parent = <&mpic>;
|
[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-13 04:53:00 +00:00
|
|
|
mdio-handle = <&MDIO>;
|
2007-05-15 21:12:27 +00:00
|
|
|
phy-handle = <&phy9>;
|
2006-08-25 08:43:25 +00:00
|
|
|
};
|
|
|
|
|
|
2008-07-10 20:21:35 +00:00
|
|
|
serial0: serial@7808 {
|
2006-08-25 08:43:25 +00:00
|
|
|
device_type = "serial";
|
|
|
|
|
compatible = "ns16550";
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x7808 0x200>;
|
|
|
|
|
clock-frequency = <1064000000>;
|
|
|
|
|
interrupts = <12 0>;
|
2007-05-15 21:12:27 +00:00
|
|
|
interrupt-parent = <&mpic>;
|
2006-08-25 08:43:25 +00:00
|
|
|
};
|
|
|
|
|
|
2008-07-10 20:21:35 +00:00
|
|
|
serial1: serial@7c08 {
|
2006-08-25 08:43:25 +00:00
|
|
|
device_type = "serial";
|
|
|
|
|
compatible = "ns16550";
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x7c08 0x200>;
|
|
|
|
|
clock-frequency = <1064000000>;
|
|
|
|
|
interrupts = <13 0>;
|
2007-05-15 21:12:27 +00:00
|
|
|
interrupt-parent = <&mpic>;
|
2006-08-25 08:43:25 +00:00
|
|
|
};
|
|
|
|
|
|
2007-05-15 21:12:27 +00:00
|
|
|
mpic: pic@7400 {
|
2006-08-25 08:43:25 +00:00
|
|
|
interrupt-controller;
|
|
|
|
|
#address-cells = <0>;
|
|
|
|
|
#interrupt-cells = <2>;
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x7400 0x400>;
|
2006-08-25 08:43:25 +00:00
|
|
|
compatible = "chrp,open-pic";
|
|
|
|
|
device_type = "open-pic";
|
|
|
|
|
};
|
2008-07-10 20:21:35 +00:00
|
|
|
pci0: pci@1000 {
|
[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-13 04:53:00 +00:00
|
|
|
compatible = "tsi108-pci";
|
2006-08-25 08:43:25 +00:00
|
|
|
device_type = "pci";
|
|
|
|
|
#interrupt-cells = <1>;
|
|
|
|
|
#size-cells = <2>;
|
|
|
|
|
#address-cells = <3>;
|
2008-04-17 14:40:48 +00:00
|
|
|
reg = <0x1000 0x1000>;
|
2006-08-25 08:43:25 +00:00
|
|
|
bus-range = <0 0>;
|
2008-04-17 14:40:48 +00:00
|
|
|
ranges = <0x2000000 0x0 0xe0000000 0xe0000000 0x0 0x1a000000
|
|
|
|
|
0x1000000 0x0 0x0 0xfa000000 0x0 0x10000>;
|
|
|
|
|
clock-frequency = <133333332>;
|
2007-05-15 21:12:27 +00:00
|
|
|
interrupt-parent = <&mpic>;
|
2008-04-17 14:40:48 +00:00
|
|
|
interrupts = <23 2>;
|
|
|
|
|
interrupt-map-mask = <0xf800 0x0 0x0 0x7>;
|
2006-08-25 08:43:25 +00:00
|
|
|
interrupt-map = <
|
|
|
|
|
|
|
|
|
|
/* IDSEL 0x11 */
|
2008-04-17 14:40:48 +00:00
|
|
|
0x800 0x0 0x0 0x1 &RT0 0x24 0x0
|
|
|
|
|
0x800 0x0 0x0 0x2 &RT0 0x25 0x0
|
|
|
|
|
0x800 0x0 0x0 0x3 &RT0 0x26 0x0
|
|
|
|
|
0x800 0x0 0x0 0x4 &RT0 0x27 0x0
|
2006-08-25 08:43:25 +00:00
|
|
|
|
|
|
|
|
/* IDSEL 0x12 */
|
2008-04-17 14:40:48 +00:00
|
|
|
0x1000 0x0 0x0 0x1 &RT0 0x25 0x0
|
|
|
|
|
0x1000 0x0 0x0 0x2 &RT0 0x26 0x0
|
|
|
|
|
0x1000 0x0 0x0 0x3 &RT0 0x27 0x0
|
|
|
|
|
0x1000 0x0 0x0 0x4 &RT0 0x24 0x0
|
2006-08-25 08:43:25 +00:00
|
|
|
|
|
|
|
|
/* IDSEL 0x13 */
|
2008-04-17 14:40:48 +00:00
|
|
|
0x1800 0x0 0x0 0x1 &RT0 0x26 0x0
|
|
|
|
|
0x1800 0x0 0x0 0x2 &RT0 0x27 0x0
|
|
|
|
|
0x1800 0x0 0x0 0x3 &RT0 0x24 0x0
|
|
|
|
|
0x1800 0x0 0x0 0x4 &RT0 0x25 0x0
|
2006-08-25 08:43:25 +00:00
|
|
|
|
|
|
|
|
/* IDSEL 0x14 */
|
2008-04-17 14:40:48 +00:00
|
|
|
0x2000 0x0 0x0 0x1 &RT0 0x27 0x0
|
|
|
|
|
0x2000 0x0 0x0 0x2 &RT0 0x24 0x0
|
|
|
|
|
0x2000 0x0 0x0 0x3 &RT0 0x25 0x0
|
|
|
|
|
0x2000 0x0 0x0 0x4 &RT0 0x26 0x0
|
2006-08-25 08:43:25 +00:00
|
|
|
>;
|
2007-05-15 21:12:27 +00:00
|
|
|
|
|
|
|
|
RT0: router@1180 {
|
2006-11-14 06:31:50 +00:00
|
|
|
clock-frequency = <0>;
|
|
|
|
|
interrupt-controller;
|
|
|
|
|
device_type = "pic-router";
|
|
|
|
|
#address-cells = <0>;
|
|
|
|
|
#interrupt-cells = <2>;
|
|
|
|
|
big-endian;
|
2008-04-17 14:40:48 +00:00
|
|
|
interrupts = <23 2>;
|
2007-05-15 21:12:27 +00:00
|
|
|
interrupt-parent = <&mpic>;
|
2006-11-14 06:31:50 +00:00
|
|
|
};
|
2006-08-25 08:43:25 +00:00
|
|
|
};
|
|
|
|
|
};
|
|
|
|
|
};
|
