summaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
diff options
context:
space:
mode:
authorSrinivas Kandagatla <srinivas.kandagatla@st.com>2012-08-30 05:49:58 +0000
committerDavid S. Miller <davem@davemloft.net>2012-08-31 16:11:16 -0400
commita5cf5ce92ecefcbeb3265e6f894905ab3ed5c4c2 (patch)
tree0118e009990a296335492414155b11b736bf9619 /drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
parentfcb118491bc8bc16c4eeb8142366bcbe17fe615d (diff)
downloadop-kernel-dev-a5cf5ce92ecefcbeb3265e6f894905ab3ed5c4c2.zip
op-kernel-dev-a5cf5ce92ecefcbeb3265e6f894905ab3ed5c4c2.tar.gz
net:stmmac: Add check if mdiobus is registered in stmmac_mdio_unregister
This patch adds a basic check in stmmac_mdio_unregister to see if mdio bus registeration for this driver was actually sucessfull or not. Use case here is, if BSP considers using mdio-gpio bus along with stmmac driver by passing mdio_bus_data as NULL in platform data. Call to stmmac_mdio_register with mdio_bus_data as NULL returns 0, which is a considered sucessfull call form stmmac. Then again when we unload the driver we just call stmmac_mdio_unregister, this is were the actual problem is stmmac-mdio code dont really know at this instance of calling that stmmac_mdio_register was actually successful. So Adding a check in stmmac_mdio_unregister is always safe. Without this patch stmmac driver calls stmmac_mdio_register from stmmac_release which Segfaults as mii bus was never registered at the first point. Originally the this bug was found when unloading an stmmac driver instance which uses mdio-gpio for smi access. Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@st.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud