> > I still think the switch@1b000000 needs to be "syscon", "simple-mfd" as > that's how the reset and i2c blocks work and they're pretty independent > of everything else. > > I've currently described the mdio interface as a device on a simple bus > although it could just be handled as a descendant of the switch block > that a driver looks up as a child node (I've tried to keep the mdio > driver independent for now but that's an implementation detail). It does > need to reach out to the ethernet-ports to figure out the mapping of > port to phy so it isn't independent. > > I see a couple of paths forward > - keep adding the switch stuff to the mfd/realtek,rtl9301-switch.yaml I think that's the way to go. > - move mfd/realtek,rtl9301-switch.yaml to net/realtek,rtl9301-switch.yaml This you can do anyway. MFD in bindings is rather placeholder for complex devices where we cannot assign one, common function. In your case you call it switch, so it could be placed in net in the first place. > - keep mfd/realtek,rtl9301-switch.yaml with the i2c and reboot but have > a $ref to a new binding under net/ (not sure what that'd look like). > > There's only one in-tree user of this so I don't think we need to be too > concerned about backwards compatibility. Downstream openwrt handles > these devices way differently already. Best regards, Krzysztof
