> Right. So if you need to have some additional "parameters" with the
> connection, then I suppose you may want to go with the GenericSerialBus
> route. However, looking at the sample device tree description:
>
> davinci_mdio: ethernet@5c030000 {
> compatible = "ti,davinci_mdio";
> reg = <0x5c030000 0x1000>;
> #address-cells = <1>;
> #size-cells = <0>;
>
> reset-gpios = <&gpio2 5 GPIO_ACTIVE_LOW>;
> reset-delay-us = <2>;
>
> ethphy0: ethernet-phy@1 {
> reg = <1>;
> };
>
> ethphy1: ethernet-phy@3 {
> reg = <3>;
> };
> };
>
> would pretty much translate directly to this in ACPI if you don't need
> any additional attributes:
>
> Device (ETH0) {
> Name (_ADR, /* PCI address of the NIC */)
>
> Device (PHY0) {
> Name (_ADR, 1)
> ...
> }
>
> Device (PHY1) {
> Name (_ADR, 3)
> ...
> }
> }
>
> which looks pretty simple to me. You can also use _DSM and _DSD here to
> pass information (like the protocol number) for the PHY devices to Linux.
I'm not particularly worried about that simple case. Other than, i
don't want people to think that is all that is required.
For a more full example, take a look at vf610-zii-dev-rev-b.dts. The
Freescale FEC Ethernet controller provides the base MDIO device,
mdio1. On top of this is an MDIO mux, using a few GPIO lines to
enable/disable 3 child MDIO busses. Each of these busses has an
Ethernet Switch. The Ethernet switch exports up to two MDIO busses,
and on these busses are Ethernet PHYs which are embedded inside the
switch. The Ethernet switches are also interrupt controllers, with the
PHYs having interrupt properties which point back to the interrupt
controller in the switch.
So i'm interested in an ACPI proposal which supports this board.
Andrew
