1. 18 3月, 2013 1 次提交
  2. 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
  3. 18 12月, 2012 1 次提交
  4. 22 11月, 2012 3 次提交
  5. 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
  6. 26 10月, 2012 1 次提交
  7. 15 10月, 2012 1 次提交
  8. 11 9月, 2012 1 次提交
  9. 07 9月, 2012 1 次提交
  10. 09 8月, 2012 1 次提交
  11. 07 8月, 2012 1 次提交
    • F
      usb: musb: fix sparse warnings · a156544b
      Felipe Balbi 提交于
      The following warnings are fixed:
      
      drivers/usb/musb/musb_core.c:357:6: warning: symbol 'musb_otg_timer_func' was not declared. Should it be static?
      drivers/usb/musb/musb_core.c:1339:27: warning: incorrect type in initializer (different address spaces)
      drivers/usb/musb/musb_core.c:1339:27:    expected void *mbase
      drivers/usb/musb/musb_core.c:1339:27:    got void [noderef] <asn:2>*mregs
      drivers/usb/musb/musb_core.c:1347:17: warning: incorrect type in argument 1 (different address spaces)
      drivers/usb/musb/musb_core.c:1347:17:    expected void [noderef] <asn:2>*addr
      drivers/usb/musb/musb_core.c:1347:17:    got void *mbase
      drivers/usb/musb/musb_core.h:487:27: warning: incorrect type in initializer (different address spaces)
      drivers/usb/musb/musb_core.h:487:27:    expected void *mbase
      drivers/usb/musb/musb_core.h:487:27:    got void [noderef] <asn:2>*mregs
      drivers/usb/musb/musb_core.h:491:26: warning: incorrect type in argument 1 (different address spaces)
      drivers/usb/musb/musb_core.h:491:26:    expected void const [noderef] <asn:2>*addr
      drivers/usb/musb/musb_core.h:491:26:    got void *mbase
      drivers/usb/musb/tusb6010.c:270:48: warning: incorrect type in argument 2 (different address spaces)
      drivers/usb/musb/tusb6010.c:270:48:    expected void [noderef] <asn:2>*buf
      drivers/usb/musb/tusb6010.c:270:48:    got unsigned char [usertype] *[assigned] buf
      drivers/usb/musb/tusb6010.c:164:32: warning: incorrect type in argument 1 (different address spaces)
      drivers/usb/musb/tusb6010.c:164:32:    expected void *to
      drivers/usb/musb/tusb6010.c:164:32:    got void [noderef] <asn:2>*buf
      drivers/usb/musb/tusb6010.c:172:24: warning: incorrect type in argument 1 (different address spaces)
      drivers/usb/musb/tusb6010.c:172:24:    expected void *to
      drivers/usb/musb/tusb6010.c:172:24:    got void [noderef] <asn:2>*[assigned] buf
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      a156544b
  12. 03 8月, 2012 1 次提交
  13. 02 7月, 2012 1 次提交
  14. 25 6月, 2012 2 次提交
  15. 27 2月, 2012 1 次提交
  16. 13 2月, 2012 2 次提交
  17. 31 1月, 2012 1 次提交
  18. 12 12月, 2011 1 次提交
  19. 12 8月, 2011 1 次提交
  20. 02 7月, 2011 1 次提交
  21. 18 5月, 2011 1 次提交
  22. 13 5月, 2011 1 次提交
    • F
      usb: musb: drop unneeded musb_debug trickery · 5c8a86e1
      Felipe Balbi 提交于
      We have a generic way of enabling/disabling
      different debug messages on a driver called
      DYNAMIC_PRINTK. Anyone interested in enabling
      just part of the debug messages, please read
      the documentation under:
      
      Documentation/dynamic-debug-howto.txt
      
      for information on how to use that great
      infrastructure.
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      5c8a86e1
  23. 07 5月, 2011 1 次提交
  24. 29 3月, 2011 1 次提交
  25. 10 12月, 2010 4 次提交
  26. 07 12月, 2010 1 次提交
    • F
      usb: musb: make all glue layer export struct musb_platform_ops · 743411b3
      Felipe Balbi 提交于
      preparing to a big refactor on musb code. We need
      to be able to compile in all glue layers (or at
      least all ARM-based ones) together and have a
      working binary.
      
      While preparing for that, we move every glue
      layer to export only one symbol, which is
      a struct musb_platform_ops, and make all
      other functions static.
      
      Later patches will come to allow for compiling
      all glue layers together and have a working
      binary.
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      743411b3
  27. 01 12月, 2010 1 次提交
  28. 23 10月, 2010 1 次提交
    • S
      USB: MUSB: fix kernel WARNING/oops when unloading module in OTG mode · f4053874
      Sergei Shtylyov 提交于
      Since commit 461972d8 (musb_core: don't call
      musb_platform_exit() twice), unloading the driver module results in a WARNING
      "kobject: '(null)' (c73de788): is not initialized, yet kobject_put() is being
      called." (or even kernel oops) on e.g. DaVincis, though only in the OTG mode.
      There exists dubious and unbalanced put_device() call in musb_free() which
      takes place only in the OTG mode.  As this commit caused musb_platform_exit()
      to be called (and so unregister the NOP transceiver) before this put_device()
      call, this function references already freed memory.
      
      On the other hand, all the glue layers miss the otg_put_transceiver() call,
      complementary to the otg_get_transceiver() call that they do.  So, I think
      the solution is to get rid of the strange put_device() call, and instead
      call otg_put_transceiver() in the glue layers...
      Signed-off-by: NSergei Shtylyov <sshtylyov@ru.mvista.com>
      Cc: stable <stable@kernel.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      f4053874
  29. 27 7月, 2010 1 次提交
  30. 21 5月, 2010 1 次提交
  31. 01 5月, 2010 1 次提交
    • T
      usb: Fix tusb6010 for DMA API · 1d0f11b3
      Tony Lindgren 提交于
      Commit 18eabe23 introduced
      DMA buffer ownership. Fix tusb6010 accordingly. To compile,
      also dummy musb_platform_save and restore functions need to
      be added.
      
      Also change the order of musb_read_fifo() to happen after
      dma_cache_maint to have the DMA operations completed before
      moving the remaining unaligned bytes with PIO. The DMA
      access and PIO touch different areas of the FIFO, so this
      change only makes the code a bit easier to follow.
      
      Tested on n810 and g_ether with variable size ping test.
      The test seems to fail for some ping sizes, but that seems to
      be a different problem.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Acked-by: NFelipe Balbi <felipe.balbi@nokia.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      1d0f11b3
  32. 03 3月, 2010 1 次提交
  33. 16 6月, 2009 1 次提交
    • D
      musb: proper hookup to transceiver drivers · 84e250ff
      David Brownell 提交于
      Let the otg_transceiver in MUSB be managed by an external driver;
      don't assume it's integrated.  OMAP3 chips need it to be external,
      and there may be ways to interact with the transceiver which add
      functionality to the system.
      
      Platform init code is responsible for setting up the transeciver,
      probably using the NOP transceiver for integrated transceivers.
      External ones will use whatever the board init code provided,
      such as twl4030 or something more hands-off.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      84e250ff