On 04/14/2016 01:35 PM, David Lechner wrote:
The "da8xx USB clocks" patch series was growing a bit too big, so on the advice
of Sekhar Nori, I am splitting it into two parts. This part contains everything
in drivers/ and the other part will contain everything in arch/arm/mach-davinci.

This patch series will apply and build on its own. It just won't work at runtime
without the corresponding mach-davinci changes to provide clocks, etc.

This round just contains changes from feedback. See individual patches for
details.

Tested working on LEGO MINDSTORMS EV3 using linux-davinci/master branch.

David Lechner (7):
   mfd: da8xx-cfgchip: New header file for CFGCHIP registers.
   dt-bindings: Add bindings for phy-da8xx-usb
   phy: Add set_mode callback
   phy: da8xx-usb: new driver for DA8xx SoC USB PHY
   usb: ohci-da8xx: Remove code that references mach
   usb: musb: da8xx: Use devm in probe
   usb: musb: da8xx: Remove mach code

  .../devicetree/bindings/phy/phy-da8xx-usb.txt      |  40 ++++
  drivers/phy/Kconfig                                |  10 +
  drivers/phy/Makefile                               |   1 +
  drivers/phy/phy-core.c                             |  15 ++
  drivers/phy/phy-da8xx-usb.c                        | 245 +++++++++++++++++++++
  drivers/usb/host/Kconfig                           |   1 +
  drivers/usb/host/ohci-da8xx.c                      | 102 +++++----
  drivers/usb/musb/Kconfig                           |   2 +-
  drivers/usb/musb/da8xx.c                           | 160 +++++---------
  include/linux/mfd/da8xx-cfgchip.h                  | 153 +++++++++++++
  include/linux/phy/phy.h                            |  15 ++
  include/linux/platform_data/usb-davinci.h          |  22 --
  12 files changed, 594 insertions(+), 172 deletions(-)
  create mode 100644 Documentation/devicetree/bindings/phy/phy-da8xx-usb.txt
  create mode 100644 drivers/phy/phy-da8xx-usb.c
  create mode 100644 include/linux/mfd/da8xx-cfgchip.h


I think all of the maintainers have weighed in now. So, I think I am ready to submit a v5 series to address some small issues to get this to "good enough" status. Which maintainer will take responsibility for including this in his tree?

Reply via email to