From: "Ivan T. Ivanov" <iiva...@mm-sol.com>

Hi,

This is a fifth version of patches posted earlier here [1].

They have been tested on AP8074 DragonBoard. Only gadget
mode utilized for now.

CV Test Suite engine "Chapter 9 tests" are passing except
"Halt Endpoint Test".

usbtest driver report following failure:
test 13 --> 32 (Broken pipe)    ep 81 couldn't set halt, -32

Changes since v4:
 - Drop patch [1/15] usb: phy: msm: Move mach dependent code to platform data
   it is already merged.
 - Address comments regarding devicetree bindings.

[1] https://lkml.org/lkml/2013/11/12/298

Ivan T. Ivanov (14):
  usb: phy: msm: Move global regulators variables to driver state
  usb: phy: msm: Migrate to Managed Device Resource allocation
  usb: phy: msm: Remove unnecessarily check for valid regulators.
  usb: phy: msm: Fix checkpatch.pl warnings
  usb: phy: msm: Replace custom enum usb_mode_type with enum
    usb_dr_mode
  usb: phy: msm: Remove unused pclk_src_name
  usb: phy: msm: Remove HSUSB prefix from regulator names
  usb: phy: msm: Properly check result from platform_get_irq()
  usb: phy: msm: Add device tree support and binding information
  usb: phy: msm: Use reset framework for LINK and PHY resets
  usb: phy: msm: Add support for secondary PHY control
  usb: phy: msm: Correct USB PHY Reset sequence for newer platform
  usb: phy: msm: Handle disconnect events
  usb: phy: msm: Vote for corner of VDD CX instead of voltage of VDD CX

 .../devicetree/bindings/usb/msm-hsusb.txt          |   78 +++
 arch/arm/mach-msm/board-msm7x30.c                  |    2 +-
 arch/arm/mach-msm/board-qsd8x50.c                  |    2 +-
 drivers/usb/phy/phy-msm-usb.c                      |  674 +++++++++++---------
 include/linux/usb/msm_hsusb.h                      |   39 +-
 include/linux/usb/msm_hsusb_hw.h                   |    6 +
 6 files changed, 474 insertions(+), 327 deletions(-)

--
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to