summaryrefslogtreecommitdiffstats
path: root/drivers/input/mouse
diff options
context:
space:
mode:
authorGrygorii Strashko <grygorii.strashko@ti.com>2014-04-19 08:51:44 +0530
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-04-24 12:53:38 -0700
commit2b97789fa289d531e767d994a77e34ec58f328c4 (patch)
tree86fed1906885de4609b7b0c7cbbcf45c1cf1816d /drivers/input/mouse
parent743bb387a1edbf1ebbba6cf77c1af3e488886c39 (diff)
downloadop-kernel-dev-2b97789fa289d531e767d994a77e34ec58f328c4.zip
op-kernel-dev-2b97789fa289d531e767d994a77e34ec58f328c4.tar.gz
phy: core: make NULL a valid phy reference if !CONFIG_GENERIC_PHY
This fixes a regression on Keystone 2 platforms caused by patch 57303488cd37da58263e842de134dc65f7c626d5 "usb: dwc3: adapt dwc3 core to use Generic PHY Framework" which adds optional support of generic phy in DWC3 core. On Keystone 2 platforms the USB is not working now because CONFIG_GENERIC_PHY isn't set and, as result, Generic PHY APIs stubs return -ENOSYS always. The log shows: dwc3 2690000.dwc3: failed to initialize core dwc3: probe of 2690000.dwc3 failed with error -38 Hence, fix it by making NULL a valid phy reference in Generic PHY APIs stubs in the same way as it was done by the patch 04c2facad8fee66c981a51852806d8923336f362 "drivers: phy: Make NULL a valid phy reference". Acked-by: Felipe Balbi <balbi@ti.com> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/input/mouse')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud