mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-14 08:13:56 +08:00
3272dd9b0f
When the mdio-gpio driver is probed via device trees, the platform device id is set as -1, However the pdev->id is re-used as bus-id for while creating mdio gpio bus. So For device tree case the mdio-gpio bus name appears as "gpio-ffffffff" where as for non-device tree case the bus name appears as "gpio-<bus-num>" Which means the bus_id is fixed in device tree case, so we can't have two mdio gpio buses via device trees. Assigning a logical bus number via device tree solves the problem and the bus name is much consistent with non-device tree bus name. Without this patch 1. we can't support two mdio-gpio buses via device trees. 2. we should always pass gpio-ffffffff as bus name to phy_connect, very different to non-device tree bus name. So, setting up the bus_id via aliases from device tree is the right solution and other drivers do similar thing. Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@st.com> Signed-off-by: David S. Miller <davem@davemloft.net> |
||
---|---|---|
.. | ||
can | ||
broadcom-bcm87xx.txt | ||
calxeda-xgmac.txt | ||
cavium-mdio.txt | ||
cavium-mix.txt | ||
cavium-pip.txt | ||
cpsw.txt | ||
davinci_emac.txt | ||
davinci-mdio.txt | ||
fsl-fec.txt | ||
fsl-tsec-phy.txt | ||
lpc-eth.txt | ||
macb.txt | ||
mdio-gpio.txt | ||
mdio-mux-gpio.txt | ||
mdio-mux-mmioreg.txt | ||
mdio-mux.txt | ||
phy.txt | ||
smsc911x.txt | ||
smsc-lan91c111.txt | ||
stmmac.txt |