1. 29 6月, 2020 2 次提交
  2. 25 6月, 2020 2 次提交
  3. 19 5月, 2020 1 次提交
  4. 18 5月, 2020 1 次提交
  5. 05 5月, 2020 4 次提交
  6. 04 5月, 2020 1 次提交
  7. 30 4月, 2020 1 次提交
  8. 28 4月, 2020 1 次提交
  9. 27 4月, 2020 1 次提交
  10. 20 3月, 2020 7 次提交
  11. 21 2月, 2020 2 次提交
  12. 08 1月, 2020 5 次提交
  13. 20 12月, 2019 2 次提交
  14. 31 10月, 2019 1 次提交
    • S
      phy: qcom-usb-hs: Fix extcon double register after power cycle · 64f86b99
      Stephan Gerhold 提交于
      Commit f0b5c2c9 ("phy: qcom-usb-hs: Replace the extcon API")
      switched from extcon_register_notifier() to the resource-managed
      API, i.e. devm_extcon_register_notifier().
      
      This is problematic in this case, because the extcon notifier
      is dynamically registered/unregistered whenever the PHY is powered
      on/off. The resource-managed API does not unregister the notifier
      until the driver is removed, so as soon as the PHY is power cycled,
      attempting to register the notifier again results in:
      
      	double register detected
      	WARNING: CPU: 1 PID: 182 at kernel/notifier.c:26 notifier_chain_register+0x74/0xa0
      	Call trace:
      	 ...
      	 extcon_register_notifier+0x74/0xb8
      	 devm_extcon_register_notifier+0x54/0xb8
      	 qcom_usb_hs_phy_power_on+0x1fc/0x208
      	 ...
      
      ... and USB stops working after plugging the cable out and in
      another time.
      
      The easiest way to fix this is to make a partial revert of
      commit f0b5c2c9 ("phy: qcom-usb-hs: Replace the extcon API")
      and avoid using the resource-managed API in this case.
      
      Fixes: f0b5c2c9 ("phy: qcom-usb-hs: Replace the extcon API")
      Signed-off-by: NStephan Gerhold <stephan@gerhold.net>
      Signed-off-by: NKishon Vijay Abraham I <kishon@ti.com>
      64f86b99
  15. 25 10月, 2019 1 次提交
  16. 26 8月, 2019 2 次提交
  17. 25 6月, 2019 1 次提交
  18. 21 6月, 2019 2 次提交
  19. 19 6月, 2019 1 次提交
  20. 05 6月, 2019 1 次提交
  21. 03 6月, 2019 1 次提交