1. 12 11月, 2012 3 次提交
    • G
      Merge tag 'dwc3-for-v3.8' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-next · 0f89fc3f
      Greg Kroah-Hartman 提交于
      USB dwc3 patches from Felipe:
      
      "usb: dwc3: patches for v3.8
      
      We can finaly drop HAVE_CLK dependency from exynos glue layer
      now that clk API provides no-op stubs when it's not linked
      into the kernel.
      
      We're also switching over event buffer allocation to devm_kzalloc()
      and moving the allocation out of dwc3_core_init() so that can be
      re-used when implementing PM support for v3.9.
      
      After the introduction of PLATFORM_DEVID_AUTO, we can also drop the
      homebrew platform device ID handling we had on dwc3 core and let
      driver core take care of that for us.
      
      Exynos glue layer learns about DeviceTree and drops platform_data
      support completely."
      0f89fc3f
    • G
      Merge tag 'musb-for-v3.8' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-next · 3a3f2e50
      Greg Kroah-Hartman 提交于
      USB musb merge from Felipe:
      
      "usb: musb: patches for v3.8 merge window
      
      We have here the usual set of cleanups for the MUSB driver; a
      big set of patches converting platform_device_del() and
      platform_device_put() into platform_device_unregister().
      
      Another big set was applied converting to module_platform_driver()
      macro in order to reduce some boilerplate code from all glue
      layers.
      
      Other than that, we had a series fixing one known silicon errata
      where we couldn't read a few registers. In order to fix that
      we're now using shadow variables for reads and only writing
      to the registers which are known to break functionality when
      read."
      3a3f2e50
    • G
      Merge tag 'xceiv-for-v3.8' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into USB-next · 8e06c6a7
      Greg Kroah-Hartman 提交于
      Pull USB phy patches from Felipe:
      
      "usb: phy: patches for v3.8 merge window
      
      Not too many patches this time. First two patches are only
      cleanups where one of them switches over to module_platform_driver
      macro and the second removes inclusion of <mach/iomap.h> and is
      part of a bigger set of include cleanups from the Tegra folks.
      
      The only substantial change here is the addition of a driver
      for Renesas' R-Car USB Phy controller."
      8e06c6a7
  2. 09 11月, 2012 2 次提交
  3. 08 11月, 2012 1 次提交
  4. 06 11月, 2012 8 次提交
  5. 04 11月, 2012 1 次提交
  6. 03 11月, 2012 4 次提交
  7. 01 11月, 2012 13 次提交
  8. 31 10月, 2012 8 次提交
    • S
      usb: musb: Perform only write access on MUSB_INTRTXE · b18d26f6
      Sebastian Andrzej Siewior 提交于
      This is part of the workaround for AM35x advisory Advisory 1.1.20.
      The advisory says that the IPSS bridge can't handle 8 & 16 bit read
      access. An 16bit read access to MUSB_INTRTXE results in an 32bit read
      access which also reads INTRRX and therefore may lose interrupts.
      This patch uses a shadow register of MUSB_INTRTXE so we only perform
      write access to it.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      b18d26f6
    • S
      usb: musb: Perform only write access on MUSB_INTRRXE · af5ec14d
      Sebastian Andrzej Siewior 提交于
      This is part of the workaround for AM35x advisory Advisory 1.1.20.
      The advisory says that the IPSS bridge can't handle 8 & 16 bit read
      access. An 16bit read access to MUSB_INTRRXE results in an 32bit read
      access which also reads INTRUSB and therefore may lose interrupts.
      This patch uses a shadow register of MUSB_INTRRXE so we only perform
      write access to it.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      af5ec14d
    • S
      usb: musb: avoid FADDR read access · 515ba29c
      Sebastian Andrzej Siewior 提交于
      This is part of the workaround for AM35x advisory Advisory 1.1.20.
      The advisory says that the IPSS bridge can't handle 8 & 16 bit read
      access. An 8bit read access to FADDR results in an 32bit read
      access which also reads INTRTX and therefore may lose interrupts.
      This patch removes any reads to FADDR as they are not really required.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      515ba29c
    • S
      usb: musb: read MUSB_POWER register only when required. · b11e94d0
      Sebastian Andrzej Siewior 提交于
      This is part of the workaround for AM35x advisory Advisory 1.1.20.
      The advisory says that the IPSS bridge can't handle 8 & 16 bit read
      access. An 8bit read access to MUSB_POWER results in an 32bit read
      access which also reads INTRTX and therefore may lose interrupts.
      This patch tries to minimize reads to MUSB_POWER and perform them only
      when required.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      b11e94d0
    • S
      usb: dwc3: remove custom unique id handling · 124dafde
      Sebastian Andrzej Siewior 提交于
      The lockless implementation of the unique id is quite impressive (:P)
      but dirver's core can handle it, we can remove it and make our code a
      little smaller.
      
      Cc: Anton Tikhomirov <av.tikhomirov@samsung.com>
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      124dafde
    • J
      USB: ums_realtek: fix build warning · 806df3ac
      Jingoo Han 提交于
      When rts51x_read_status() returns USB_STOR_TRANSPORT_ERROR,
      an error happens. This patch fixes build warning as below:
      
      drivers/usb/storage/realtek_cr.c: In function 'init_realtek_cr':
      drivers/usb/storage/realtek_cr.c:476:33: warning: 'buf[15]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[15]' was declared here
      drivers/usb/storage/realtek_cr.c:475:33: warning: 'buf[14]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[14]' was declared here
      drivers/usb/storage/realtek_cr.c:474:50: warning: 'buf[13]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[13]' was declared here
      drivers/usb/storage/realtek_cr.c:472:30: warning: 'buf[12]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[12]' was declared here
      drivers/usb/storage/realtek_cr.c:471:31: warning: 'buf[11]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[11]' was declared here
      drivers/usb/storage/realtek_cr.c:470:31: warning: 'buf[10]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[10]' was declared here
      drivers/usb/storage/realtek_cr.c:469:30: warning: 'buf[9]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[9]' was declared here
      drivers/usb/storage/realtek_cr.c:468:27: warning: 'buf[8]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[8]' was declared here
      drivers/usb/storage/realtek_cr.c:468:43: warning: 'buf[7]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[7]' was declared here
      drivers/usb/storage/realtek_cr.c:467:30: warning: 'buf[6]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[6]' was declared here
      drivers/usb/storage/realtek_cr.c:466:30: warning: 'buf[5]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[5]' was declared here
      drivers/usb/storage/realtek_cr.c:465:28: warning: 'buf[4]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[4]' was declared here
      drivers/usb/storage/realtek_cr.c:464:24: warning: 'buf[3]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[3]' was declared here
      drivers/usb/storage/realtek_cr.c:464:40: warning: 'buf[2]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[2]' was declared here
      drivers/usb/storage/realtek_cr.c:463:24: warning: 'buf[1]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[1]' was declared here
      drivers/usb/storage/realtek_cr.c:463:40: warning: 'buf[0]' may be used uninitialized in this function [-Wuninitialized]
      drivers/usb/storage/realtek_cr.c:455:5: note: 'buf[0]' was declared here
      Signed-off-by: NJingoo Han <jg1.han@samsung.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      806df3ac
    • J
      USB: ftdi_sio: use ftdi_get_modem_status in chars_in_buffer · 5fb0432e
      Johan Hovold 提交于
      Use ftdi_get_modem_status to check hardware buffers in chars_in_buffer.
      Signed-off-by: NJohan Hovold <jhovold@gmail.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      5fb0432e
    • J
      USB: ftdi_sio: optimise chars_in_buffer · 8da636d9
      Johan Hovold 提交于
      No need to check hardware buffers when we know that the software
      buffers are non-empty.
      Signed-off-by: NJohan Hovold <jhovold@gmail.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      8da636d9