1. 28 8月, 2013 2 次提交
  2. 09 8月, 2013 3 次提交
    • S
      usb: musb: dsps: use proper child nodes · 97238b35
      Sebastian Andrzej Siewior 提交于
      This moves the two instances from the big node into two child nodes. The
      glue layer ontop does almost nothing.
      
      There is one devices containing the control module for USB (2) phy,
      (2) usb and later the dma engine. The usb device is the "glue device"
      which contains the musb device as a child. This is what we do ever since.
      
      The new file musb_am335x is just here to prob the new bus and populate
      child devices.
      
      There are a lot of changes to the dsps file as a result of the changes:
      
      - musb_core_offset
        This is gone. The device tree provides memory ressources information
        for the device there is no need to "fix" things
      
      - instances
        This is gone as well. If we have two instances then we have have two
        child enabled nodes in the device tree. For instance the SoC in beagle
        bone has two USB instances but only one has been wired up so there is
        no need to load and init the second instance since it won't be used.
      
      - dsps_glue is now per glue device
        In the past there was one of this structs but with an array of two and
        each instance accessed its variable depending on the platform device
        id.
      
      - no unneeded copy of structs
        I do not know why struct dsps_musb_wrapper is copied but it is not
        necessary. The same goes for musb_hdrc_platform_data which allocated
        on demand and then again by platform_device_add_data(). One copy is
        enough.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      97238b35
    • S
      usb: musb: dsps: remove the hardcoded phy pieces · e96bdc3d
      Sebastian Andrzej Siewior 提交于
      dsps uses a nop driver which is added in dsps itself and does the PHY
      on/off calls within dsps. Since those calls are now moved the nop driver
      itself, we can now request the phy proper phy and remove those calls.
      Currently only the first musb interface is used so we only add one phy
      node for now.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      e96bdc3d
    • S
      usb: phy: rename nop_usb_xceiv => usb_phy_gen_xceiv · 3fa4d734
      Sebastian Andrzej Siewior 提交于
      The "nop" driver isn't a do-nothing-stub but supports a couple functions
      like clock on/off or is able to use a voltage regulator. This patch
      simply renames the driver to "generic" since it is easy possible to
      extend it by a simple function istead of writing a complete driver.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      3fa4d734
  3. 30 7月, 2013 1 次提交
  4. 29 7月, 2013 4 次提交
  5. 28 5月, 2013 1 次提交
  6. 15 5月, 2013 1 次提交
  7. 02 4月, 2013 1 次提交
  8. 18 3月, 2013 3 次提交
  9. 23 1月, 2013 1 次提交
  10. 17 1月, 2013 1 次提交
    • M
      usb: musb: fix dependency on transceiver driver · 25736e0c
      Ming Lei 提交于
      This patch let glue driver return -EPROBE_DEFER if the transceiver
      is not readly, so we can support defer probe on musb to fix the
      below error on 3.7-rc5 if transceiver drivers are built as module:
      
      [   19.052490] unable to find transceiver of type USB2 PHY
      [   19.072052] HS USB OTG: no transceiver configured
      [   19.076995] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -19
      [   19.089355] musb-hdrc: probe of musb-hdrc.0.auto rejects match -19
      [   19.096771] driver: 'musb-omap2430': driver_bound: bound to device 'musb-omap2430'
      [   19.105194] bus: 'platform': really_probe: bound device musb-omap2430 to driver musb-omap2430
      [   19.174407] bus: 'platform': add driver twl4030_usb
      [   19.179656] bus: 'platform': driver_probe_device: matched device twl4030_usb with driver twl4030_usb
      [   19.202270] bus: 'platform': really_probe: probing driver twl4030_usb with device twl4030_usb
      [   19.214172] twl4030_usb twl4030_usb: HW_CONDITIONS 0xc0/192; link 3
      [   19.239624] musb-omap2430 musb-omap2430: musb core is not yet ready
      [   19.246765] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
      [   19.254516] driver: 'twl4030_usb': driver_bound: bound to device 'twl4030_usb'
      [   19.263580] bus: 'platform': really_probe: bound device twl4030_usb to driver twl4030_usb
      
      Cc: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
      Cc: <stable@vger.kernel.org> v3.8
      Signed-off-by: NMing Lei <ming.lei@canonical.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      25736e0c
  11. 10 1月, 2013 1 次提交
  12. 13 12月, 2012 1 次提交
    • A
      usb: musb: dsps: header movement build error fix · deeeb9ee
      Afzal Mohammed 提交于
      "54db6eee ARM: OMAP2+: Introduce local usb.h" moved control module bit
      definitions from plat/usb.h (which dsps glue was using) to a local
      header in mach-omap2. And in parallel,
      "c68bb4c6 usb: musb: dsps: control module handling (quirk)" added
      control module handling capability to dsps glue driver that used
      those control module bit definitions.
      
      Integration of above two changes would cause build error in musb dsps
      glue driver (they go through different trees upstream) as is seen now
      in linux-next. Fix it by adding necessary definitions in dsps glue
      driver.
      Signed-off-by: NAfzal Mohammed <afzal@ti.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      deeeb9ee
  13. 22 11月, 2012 4 次提交
  14. 09 11月, 2012 1 次提交
  15. 06 11月, 2012 5 次提交
  16. 01 11月, 2012 1 次提交
    • S
      usb: musb: remove hand-crafted id handling · 2f771164
      Sebastian Andrzej Siewior 提交于
      This replaced the handcrafted id handling by the PLATFORM_DEVID_AUTO
      value which should do the same thing.
      
      This patch probably also fixes ux500 because I did not find the "musbid"
      variable to remove. And we close a tiny-unlikely race window becuase the
      old code gave the id back before device was destroyed in the remove
      case.
      
      [ balbi@ti.com : fixed up two failed hunks when applying patch ]
      
      Cc: B, Ravi <ravibabu@ti.com>
      Cc: Santhapuri, Damodar <damodar.santhapuri@ti.com>
      Cc: Mian Yousaf Kaukab <mian.yousaf.kaukab@stericsson.com>
      Cc: Bob Liu <lliubbo@gmail.com>
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      2f771164
  17. 26 10月, 2012 1 次提交
  18. 25 10月, 2012 1 次提交
    • F
      ARM: OMAP: move OMAP USB platform data to <linux/platform_data/omap-usb.h> · e8c4a7ac
      Felipe Balbi 提交于
      In order to make single zImage work for ARM architecture,
      we need to make sure we don't depend on private headers.
      
      Move USB platform_data to <linux/platform_data/omap-usb.h>
      and add a minimal drivers/mfd/usb-omap.h.
      
      Cc: Samuel Ortiz <sameo@linux.intel.com>
      Cc: Alan Stern <stern@rowland.harvard.edu>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Partha Basak <parthab@india.ti.com>
      Cc: Keshava Munegowda <keshava_mgowda@ti.com>
      Cc: linux-usb@vger.kernel.org
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      [tony@atomide.com: updated for local mfd/usb-omap.h]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      e8c4a7ac
  19. 23 10月, 2012 1 次提交
  20. 11 9月, 2012 4 次提交
  21. 09 8月, 2012 1 次提交
  22. 03 8月, 2012 1 次提交