1. 03 2月, 2015 1 次提交
  2. 23 12月, 2014 1 次提交
  3. 25 11月, 2014 3 次提交
  4. 04 11月, 2014 2 次提交
  5. 01 7月, 2014 1 次提交
    • H
      usb: musb: backfin: Introduce the use of the managed version of kzalloc · f875bf35
      Himangi Saraogi 提交于
      This patch moves data allocated using kzalloc to managed data allocated
      using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
      functions. Also, a label is done away with and err2 and err3 renamed.
      
      The following Coccinelle semantic patch was used for making the change:
      
      @platform@
      identifier p, probefn, removefn;
      @@
      struct platform_driver p = {
        .probe = probefn,
        .remove = removefn,
      };
      
      @prb@
      identifier platform.probefn, pdev;
      expression e, e1, e2;
      @@
      probefn(struct platform_device *pdev, ...) {
        <+...
      - e = kzalloc(e1, e2)
      + e = devm_kzalloc(&pdev->dev, e1, e2)
        ...
      ?-kfree(e);
        ...+>
      }
      
      @rem depends on prb@
      identifier platform.removefn;
      expression e;
      @@
      removefn(...) {
        <...
      - kfree(e);
        ...>
      }
      Signed-off-by: NHimangi Saraogi <himangi774@gmail.com>
      Acked-by: NJulia Lawall <julia.lawall@lip6.fr>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      f875bf35
  6. 22 4月, 2014 4 次提交
  7. 09 1月, 2014 1 次提交
  8. 04 1月, 2014 1 次提交
  9. 02 10月, 2013 1 次提交
  10. 09 8月, 2013 1 次提交
  11. 30 7月, 2013 1 次提交
  12. 29 5月, 2013 1 次提交
  13. 18 3月, 2013 1 次提交
  14. 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
  15. 22 11月, 2012 2 次提交
  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. 15 10月, 2012 1 次提交
  19. 11 9月, 2012 1 次提交
  20. 09 8月, 2012 1 次提交
  21. 03 8月, 2012 1 次提交
  22. 02 7月, 2012 1 次提交
  23. 25 6月, 2012 2 次提交
  24. 27 2月, 2012 1 次提交
  25. 13 2月, 2012 1 次提交
  26. 31 1月, 2012 1 次提交
  27. 12 8月, 2011 1 次提交
  28. 18 5月, 2011 1 次提交
  29. 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
  30. 07 5月, 2011 1 次提交
  31. 13 4月, 2011 1 次提交
    • M
      USB: musb: blackfin: work around anomaly 05000450 · 13254307
      Mike Frysinger 提交于
      DMA mode 1 data corruption anomaly on Blackfin systems.  This issue is
      specific to the Blackfin silicon as the bug appears to be related to the
      connection of the musb ip to the bus/dma fabric.
      
      Data corruption when using USB DMA mode 1. (Issue manager 17-01-0105)
      DMA mode 1 allows large size transfers to generate a single interrupt
      at the end of the entire transfer.  The transfer is split up in packets
      of length specified in the Maximum Packet Size field for that endpoint.
      If the transfer size is not an integer multiple of the Maximum Packet
      Size, a short packet will be present at the end of the transfer.
      
      Under certain conditions this packet may be corrupted in the USB FIFO.
      
      Workaround:
      Use DMA mode 1 to transfer (n* Maximum Packet Size) and schedule DMA
      mode 0 to transfer the short packet.
      
      As an example if your transfer size is 33168 bytes and Maximum Packet
      Size equals 512, schedule [33168 - (33168 mod 512)] in DMA mode 1 and
      the remainder (33168 mod 512) in DMA mode 0.
      Signed-off-by: NMike Frysinger <vapier@gentoo.org>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      13254307
  32. 24 3月, 2011 1 次提交