1. 12 8月, 2011 1 次提交
  2. 02 7月, 2011 1 次提交
  3. 18 5月, 2011 1 次提交
  4. 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
  5. 07 5月, 2011 1 次提交
  6. 29 3月, 2011 1 次提交
  7. 10 12月, 2010 4 次提交
  8. 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
  9. 01 12月, 2010 1 次提交
  10. 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
  11. 27 7月, 2010 1 次提交
  12. 21 5月, 2010 1 次提交
  13. 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
  14. 03 3月, 2010 1 次提交
  15. 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
  16. 24 4月, 2009 1 次提交
  17. 08 1月, 2009 1 次提交
  18. 14 11月, 2008 1 次提交
  19. 14 8月, 2008 1 次提交