1. 02 5月, 2012 1 次提交
    • R
      USB: Add driver for NXP ISP1301 USB transceiver · 8b7c3b68
      Roland Stigge 提交于
      This new driver registers the NXP ISP1301 chip via the I2C subsystem.  The chip
      is the USB transceiver shared by ohci-nxp, lpc32xx_udc (gadget) and
      isp1301_omap.
      
      ISP1301 is a very low-level driver that primarily separates out the I2C client
      registration of the ISP1301 chip (including instantiation via DT), used by
      other drivers, and declares the chip's registers. It's only a helper driver for
      some OHCI and USB device drivers.  The driver can be considered as a register
      set extension of ohci-nxp, lpc32xx-udc and isp1301_omap, which in turn know
      best what to do with the low level functionality (individual ISP1301 registers
      and timing, see the different initialization strategies in those drivers).
      Those drivers previously internally duplicated ISP1301 register definitions
      which is solved by this new isp1301 driver. The ISP1301 registers exposed via
      isp1301.h can be accessed by other drivers using it with standard i2c_smbus_*()
      accesses.
      
      Following patches let the respective USB host and gadget drivers use this
      driver, instead of duplicating ISP1301 handling.
      Signed-off-by: NRoland Stigge <stigge@antcom.de>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      8b7c3b68
  2. 07 4月, 2012 1 次提交
  3. 16 3月, 2012 1 次提交
  4. 14 3月, 2012 1 次提交
  5. 03 3月, 2012 1 次提交
    • K
      ARM: S3C24XX: change the ARCH_S3C2410 to ARCH_S3C24XX · b130d5c2
      Kukjin Kim 提交于
      This patch changes the ARCH name to "ARCH_S3C24XX" for Samsung
      S3C2410, S3C2412, S3C2413, S3C2416, S3C2440, S3C2442, S3C2443,
      and S3C2450 SoCs so that we can merge the mach-xxx directories
      and plat-s3c24xx dir. to just one mach-s3c24xx for them.
      
      I think this should be sent to upstream via samsung tree because
      this touches many samsung stuff.
      
      Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Cc: Chris Ball <cjb@laptop.org>
      Cc: David Woodhouse <dwmw2@infradead.org>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Greg Kroah-Hartman <gregkh@suse.de>
      [for the gadget part:]
      Acked-by: NFelipe Balbi <balbi@ti.com>
      [for the framebuffer (video) part:]
      Acked-by: NFlorian Tobias Schandinat <FlorianSchandinat@gmx.de>
      [For the watchdog-part:]
      Acked-by: NWim Van Sebroeck <wim@iguana.be>
      Cc: Sangbeom Kim <sbkim73@samsung.com>
      Cc: Liam Girdwood <lrg@ti.com>
      Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
      Cc: Russell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      b130d5c2
  6. 25 1月, 2012 1 次提交
  7. 23 12月, 2011 1 次提交
  8. 25 10月, 2011 1 次提交
  9. 19 10月, 2011 1 次提交
  10. 27 9月, 2011 1 次提交
  11. 18 9月, 2011 1 次提交
    • M
      usb: Provide usb_speed_string() function · e538dfda
      Michal Nazarewicz 提交于
      In a few places in the kernel, the code prints
      a human-readable USB device speed (eg. "high speed").
      This involves a switch statement sometimes wrapped
      around in ({ ... }) block leading to code repetition.
      
      To mitigate this issue, this commit introduces
      usb_speed_string() function, which returns
      a human-readable name of provided speed.
      
      It also changes a few places switch was used to use
      this new function.  This changes a bit the way the
      speed is printed in few instances at the same time
      standardising it.
      Signed-off-by: NMichal Nazarewicz <mina86@mina86.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      e538dfda
  12. 23 8月, 2011 2 次提交
    • F
      usb: Introduce DesignWare USB3 DRD Driver · 72246da4
      Felipe Balbi 提交于
      The DesignWare USB3 is a highly
      configurable IP Core which can be
      instantiated as Dual-Role Device (DRD),
      Peripheral Only and Host Only (XHCI)
      configurations.
      
      Several other parameters can be configured
      like amount of FIFO space, amount of TX and
      RX endpoints, amount of Host Interrupters,
      etc.
      
      The current driver has been validated with
      a virtual model of version 1.73a of that core
      and with an FPGA burned with version 1.83a
      of the DRD core. We have support for PCIe
      bus, which is used on FPGA prototyping, and
      for the OMAP5, more adaptation (or glue)
      layers can be easily added and the driver
      is half prepared to handle any possible
      configuration the HW engineer has chosen
      considering we have the information on
      one of the GHWPARAMS registers to do
      runtime checking of certain features.
      
      More runtime checks can, and should, be added
      in order to make this driver even more flexible
      with regards to number of endpoints, FIFO sizes,
      transfer types, etc.
      
      While this supports only the device side, for
      now, we will add support for Host side (xHCI -
      see the updated series Sebastian has sent [1])
      and OTG after we have it all stabilized.
      
      [1] http://marc.info/?l=linux-usb&m=131341992020339&w=2Signed-off-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      72246da4
    • T
      USB: pxa168: Add onchip USB host controller support · 3abd7f68
      Tanmay Upadhyay 提交于
      - Add EHCI Host controller driver
      - Add wrapper that creates resources for host controller driver
      
      v2 - Call clk_put() after clk_disable() in probe function
      Signed-off-by: NTanmay Upadhyay <tanmay.upadhyay@einfochips.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      3abd7f68
  13. 09 7月, 2011 1 次提交
  14. 02 7月, 2011 1 次提交
    • F
      usb: gadget: allow multiple gadgets to be built · 193ab2a6
      Felipe Balbi 提交于
      now that we have the udc class, we can allow
      multiple gadget controller drivers to be
      compiled as modules. This will allow for
      distro-like kernels for embedded devices.
      
      With this patch, I managed to build an x86
      kernel with support for many of the controllers
      enabled:
      
      CONFIG_USB_FUSB300=m
      CONFIG_USB_R8A66597=m
      CONFIG_USB_M66592=m
      CONFIG_USB_AMD5536UDC=m
      CONFIG_USB_CI13XXX_PCI=m
      CONFIG_USB_NET2272=m
      CONFIG_USB_NET2280=m
      CONFIG_USB_GOKU=m
      CONFIG_USB_LANGWELL=m
      CONFIG_USB_EG20T=m
      
      Also an ARM kernel with support for many controllers:
      
      CONFIG_USB_FUSB300=m
      CONFIG_USB_OMAP=m
      CONFIG_USB_R8A66597=m
      CONFIG_USB_GADGET_MUSB_HDRC=m
      CONFIG_USB_M66592=m
      CONFIG_USB_NET2272=m
      CONFIG_USB_DUMMY_HCD=m
      
      The next step would be to get rid of the
      direct access to arch/ and mach/ directories
      on some gadget controllers so that we can
      build all of them without depending on their
      respective ARCH_* symbols.
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      193ab2a6
  15. 04 5月, 2011 1 次提交
  16. 14 4月, 2011 3 次提交
  17. 25 1月, 2011 1 次提交
  18. 11 12月, 2010 1 次提交
  19. 01 12月, 2010 1 次提交
  20. 29 11月, 2010 1 次提交
  21. 17 11月, 2010 1 次提交
  22. 11 11月, 2010 1 次提交
  23. 02 11月, 2010 1 次提交
  24. 23 10月, 2010 1 次提交
    • A
      USB: add USB EHCI support for MPC5121 SoC · 230f7ede
      Anatolij Gustschin 提交于
      Extends FSL EHCI platform driver glue layer to support
      MPC5121 USB controllers. MPC5121 Rev 2.0 silicon EHCI
      registers are in big endian format. The appropriate flags
      are set using the information in the platform data structure.
      MPC83xx system interface registers are not available on
      MPC512x, so the access to these registers is isolated in
      MPC512x case. Furthermore the USB controller clocks
      must be enabled before 512x register accesses which is
      done by providing platform specific init callback.
      
      The MPC512x internal USB PHY doesn't provide supply voltage.
      For boards using different power switches allow specifying
      DRVVBUS and PWR_FAULT signal polarity of the MPC5121 internal
      PHY using "fsl,invert-drvvbus" and "fsl,invert-pwr-fault"
      properties in the device tree USB nodes. Adds documentation
      for this new device tree bindings.
      Signed-off-by: NAnatolij Gustschin <agust@denx.de>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      230f7ede
  25. 05 8月, 2010 2 次提交
  26. 03 3月, 2010 2 次提交
  27. 16 2月, 2010 1 次提交
  28. 12 12月, 2009 2 次提交
  29. 23 9月, 2009 2 次提交
  30. 22 9月, 2009 1 次提交
  31. 16 6月, 2009 1 次提交
  32. 21 5月, 2009 1 次提交
  33. 16 3月, 2009 1 次提交