diff options
| author |   Marek Behún <marek.behun@nic.cz> | 2019-11-18 19:15:05 +0100 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2019-11-18 17:59:32 -0800 |
| commit | 075e238d12c21c8bde700d21fb48be7a3aa80194 (patch) | |
| tree | ed3abf590650b70be12436995e57c581c8b8f7e8 /drivers/net/ethernet/google | |
| parent | net/ipv4: fix sysctl max for fib_multipath_hash_policy (diff) | |
| download | linux-dev-075e238d12c21c8bde700d21fb48be7a3aa80194.tar.xz linux-dev-075e238d12c21c8bde700d21fb48be7a3aa80194.zip | |
mdio_bus: fix mdio_register_device when RESET_CONTROLLER is disabled
When CONFIG_RESET_CONTROLLER is disabled, the
devm_reset_control_get_exclusive function returns -ENOTSUPP. This is not
handled in subsequent check and then the mdio device fails to probe.
When CONFIG_RESET_CONTROLLER is enabled, its code checks in OF for reset
device, and since it is not present, returns -ENOENT. -ENOENT is handled.
Add -ENOTSUPP also.
This happened to me when upgrading kernel on Turris Omnia. You either
have to enable CONFIG_RESET_CONTROLLER or use this patch.
Signed-off-by: Marek Behún <marek.behun@nic.cz>
Fixes: 71dd6c0dff51b ("net: phy: add support for reset-controller")
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/google')
0 files changed, 0 insertions, 0 deletions