>>>>+- reg : Offset and length of the register regions for the device>>
>>>+- reg-names : Register region names referenced in 'reg' above.
>>>+ Required register resource entries are:
>>>+ "base" : EMAC controller base register block.
>>>+ "csr" : EMAC wrapper register block.
>>>+ Optional register resource entries are:
>>>+ "ptp" : EMAC PTP (1588) register block.
>>>+ Required if 'qcom,emac-tstamp-en' is present.
>>>+ "sgmii" : EMAC SGMII PHY register block.
>>>+- interrupts : Interrupt numbers used by this controller
>>>+- interrupt-names : Interrupt resource names referenced in 'interrupts'
>>>above.
>>>+ Required interrupt resource entries are:
>>>+ "emac_core0" : EMAC core0 interrupt.
>>>+ "sgmii_irq" : EMAC SGMII interrupt.
>>>+- qcom,emac-gpio-mdc : GPIO pin number of the MDC line of MDIO bus.
>>>+- qcom,emac-gpio-mdio : GPIO pin number of the MDIO line of MDIO bus.
>>
>>Use the standard binding for GPIO controlled MDIO bus.
>
>I'm not familiar with that one. Are you talking about
>bindings/net/mdio-gpio.txt?
Yes.
>>>>+- phy-addr : Specifies phy address on MDIO bus.>>
>>>+ Required if the optional property
>>>"qcom,no-external-phy"
>>>+ is not specified.
>>
>>Don't you think you will need to know the specific phy device or other
>>properties of the phy?
>
>That, I can't answer. Aren't all MDIO devices basically the same? It's
>been a while since I've worked on them.
No. There was some discussion just this week about needing to require
phy devices to have compatible strings.