mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-30 00:21:06 +00:00
1c8ad08674
In the case of the tsec network driver, so far there has been no
mainline user of DM_ETH where the DT bindings get used.
In the case of the mdio bus, it looks like the "fsl,tsec-mdio" string
was made up for the documentation, but there is no mainline code that
parses the "compatible" property anyway.
In both cases, there are no DT blobs that contain the old strings.
So change the documentation to "fsl,etsec2" for the Ethernet ports and
"fsl,etsec2-mdio" for the MDIO buses, which are strings that Linux also
uses, at least for LS1021A. More compatible strings can be added once
other (PowerPC) SoCs are migrated to DM_ETH.
The current ls1021a.dtsi doesn't match what was documented for the MDIO
buses anyway (the "compatible" is "gianfar" currently). This will be
fixed in the next patch.
Fixes: 69a00875e3 ("doc: dt-bindings: Describe Freescale TSEC ethernet controller")
Signed-off-by: Vladimir Oltean <olteanv@gmail.com>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Joe Hershberger <joe.hershberger@ni.com>
64 lines
1.9 KiB
Text
64 lines
1.9 KiB
Text
* TSEC-compatible ethernet nodes
|
|
|
|
Properties:
|
|
|
|
- compatible : Should be "fsl,tsec"
|
|
- reg : Offset and length of the register set for the device
|
|
- phy-handle : See ethernet.txt file in the same directory.
|
|
- phy-connection-type : See ethernet.txt file in the same directory. This
|
|
property is only really needed if the connection is of type "rgmii-id",
|
|
"rgmii-rxid" and "rgmii-txid" as all other connection types are detected
|
|
by hardware.
|
|
|
|
Example:
|
|
ethernet@24000 {
|
|
compatible = "fsl,tsec";
|
|
reg = <0x24000 0x1000>;
|
|
phy-handle = <&phy0>;
|
|
phy-connection-type = "sgmii";
|
|
};
|
|
|
|
Child nodes of the TSEC controller are typically the individual PHY devices
|
|
connected via the MDIO bus (sometimes the MDIO bus controller is separate).
|
|
|
|
* MDIO IO device
|
|
|
|
The MDIO is a bus to which the PHY devices are connected. For each
|
|
device that exists on this bus, a PHY node should be created.
|
|
|
|
Required properties:
|
|
- compatible : Should define the compatible device type for the
|
|
mdio. Currently supported string/device is "fsl,etsec2-mdio".
|
|
- reg : Offset and length of the register set for the device
|
|
|
|
Example:
|
|
|
|
mdio@24520 {
|
|
compatible = "fsl,etsec2-mdio";
|
|
reg = <0x24520 0x20>;
|
|
|
|
ethernet-phy@0 {
|
|
reg = <0>;
|
|
};
|
|
};
|
|
|
|
* TBI Internal MDIO bus
|
|
|
|
As of this writing, every tsec is associated with an internal TBI PHY.
|
|
This PHY is accessed through the local MDIO bus. These buses are defined
|
|
similarly to the mdio buses. The TBI PHYs underneath them are similar to
|
|
normal PHYs, but the reg property is considered instructive, rather than
|
|
descriptive. The reg property should be chosen so it doesn't interfere
|
|
with other PHYs on the bus. The TBI PHYs are referred to by a "tbi-handle"
|
|
property under the tsec node, which has a similar meaning of "phy-handle".
|
|
|
|
Example:
|
|
ethernet@24000 {
|
|
phy-handle = <&tbi1>;
|
|
};
|
|
|
|
mdio@24520 {
|
|
tbi1: tbi-phy@1f {
|
|
reg = <0x1f>;
|
|
};
|
|
};
|