1. 19 8月, 2014 1 次提交
  2. 01 7月, 2014 3 次提交
    • S
      usb: phy: msm: Do not do runtime pm if the phy is not idle · 508ccea1
      Srinivas Kandagatla 提交于
      Use case is when the phy is configured in host mode and a usb device is
      attached to board before bootup. On bootup, with the existing code and
      runtime pm enabled, the driver would decrement the pm usage count
      without checking the current state of the phy. This pm usage count
      decrement would trigger the runtime pm which than would abort the
      usb enumeration which was in progress. In my case a usb stick gets
      detected and then immediatly the driver goes to low power mode which is
      not correct.
      
      log:
      [    1.631412] msm_hsusb_host 12520000.usb: EHCI Host Controller
      [    1.636556] msm_hsusb_host 12520000.usb: new USB bus registered, assigned bus number 1
      [    1.642563] msm_hsusb_host 12520000.usb: irq 220, io mem 0x12520000
      [    1.658197] msm_hsusb_host 12520000.usb: USB 2.0 started, EHCI 1.00
      [    1.659473] hub 1-0:1.0: USB hub found
      [    1.663415] hub 1-0:1.0: 1 port detected
      ...
      [    1.973352] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
      [    2.107707] usb-storage 1-1:1.0: USB Mass Storage device detected
      [    2.108993] scsi0 : usb-storage 1-1:1.0
      [    2.678341] msm_otg 12520000.phy: USB in low power mode
      [    3.168977] usb 1-1: USB disconnect, device number 2
      
      This issue was detected on IFC6410 board.
      
      This patch fixes the intial runtime pm trigger by checking the phy
      state and decrementing the pm use count only when the phy state is IDLE.
      Signed-off-by: NSrinivas Kandagatla <srinivas.kandagatla@linaro.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      508ccea1
    • S
      usb: phy: msm: Make phy_reset clk and reset line optional. · e44f1f4c
      Srinivas Kandagatla 提交于
      This patch makes the phy reset clk and reset line optional as this clk
      is not available on boards like IFC6410 with APQ8064.
      Signed-off-by: NSrinivas Kandagatla <srinivas.kandagatla@linaro.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      e44f1f4c
    • J
      usb: phy: msm: Make of_device_id array const · 492240b0
      Jingoo Han 提交于
      Make of_device_id array const, because all OF functions handle
      it as const.
      Signed-off-by: NJingoo Han <jg1.han@samsung.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      492240b0
  3. 23 5月, 2014 1 次提交
  4. 14 5月, 2014 1 次提交
  5. 13 5月, 2014 2 次提交
  6. 01 5月, 2014 18 次提交
  7. 20 2月, 2014 1 次提交
    • J
      usb: phy: msm: fix compilation errors when !CONFIG_PM_SLEEP · e7d613d1
      Josh Cartwright 提交于
      Both the PM_RUNTIME and PM_SLEEP callbacks call into the common
      msm_otg_{suspend,resume} routines, however these routines are only being
      built when CONFIG_PM_SLEEP.  In addition, msm_otg_{suspend,resume} also
      depends on msm_hsusb_config_vddcx(), which is only built when
      CONFIG_PM_SLEEP.
      
      Fix the CONFIG_PM_RUNTIME, !CONFIG_PM_SLEEP case by changing the
      preprocessor conditional, and moving msm_hsusb_config_vddcx().
      
      While we're here, eliminate the CONFIG_PM conditional for setting
      up the dev_pm_ops.
      
      This address the following errors Russell King has hit doing randconfig
      builds:
      
      drivers/usb/phy/phy-msm-usb.c: In function 'msm_otg_runtime_suspend':
      drivers/usb/phy/phy-msm-usb.c:1691:2: error: implicit declaration of function 'msm_otg_suspend'
      drivers/usb/phy/phy-msm-usb.c: In function 'msm_otg_runtime_resume':
      drivers/usb/phy/phy-msm-usb.c:1699:2: error: implicit declaration of function 'msm_otg_resume'
      
      Cc: Ivan T. Ivanov <iivanov@mm-sol.com>
      Reported-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NJosh Cartwright <joshc@codeaurora.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      e7d613d1
  8. 08 2月, 2014 1 次提交
  9. 09 1月, 2014 1 次提交
  10. 09 12月, 2013 1 次提交
  11. 30 7月, 2013 1 次提交
  12. 25 6月, 2013 1 次提交
  13. 18 3月, 2013 2 次提交
  14. 18 1月, 2013 1 次提交
  15. 22 11月, 2012 2 次提交
  16. 25 6月, 2012 2 次提交
  17. 13 2月, 2012 1 次提交