On 3/9/24 6:53 PM, Niklas Söderlund wrote: > The driver used the OF node of the device itself when registering the s/OF/DT/, perhaps? > MDIO bus. While this works it creates a problem, it forces any MDIO bus While this works, it creates a problem: it forces any MDIO bus... > properties to also be set on the devices OF node. This mixes the Again, DT node? > properties of two distinctly different things and is confusing. > > This change adds support for an optional mdio node to be defined as a > child to the device OF node. The child node can then be used to describe > MDIO bus properties that the MDIO core can act on when registering the > bus. > > If no mdio child node is found the driver fallback to the old behavior > and register the MDIO bus using the device OF node. This change is > backward compatible with old bindings in use. > > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@xxxxxxxxxxxx> Reviewed-by: Sergey Shtylyov <s.shtylyov@xxxxxx> [...] MBR, Sergey
