1. 09 3月, 2014 1 次提交
  2. 06 3月, 2014 1 次提交
  3. 24 12月, 2013 1 次提交
  4. 17 12月, 2013 1 次提交
  5. 13 12月, 2013 1 次提交
  6. 07 12月, 2013 2 次提交
  7. 27 11月, 2013 1 次提交
  8. 11 10月, 2013 1 次提交
  9. 28 9月, 2013 2 次提交
  10. 27 9月, 2013 1 次提交
  11. 09 8月, 2013 1 次提交
    • S
      usb: phy: Add AM335x PHY driver · 3bb869c8
      Sebastian Andrzej Siewior 提交于
      This driver is a redo of my earlier attempt. It uses parts of the
      generic PHY driver and uses the new control driver for the register
      the phy needs to power on/off the phy. It also enables easy access for
      the wakeup register which is not yet implemented.
      The difference between the omap attempt is:
      - no static holding variable
      - one global visible function which exports a struct with callbacks to
        access the "control" registers.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      3bb869c8
  12. 29 7月, 2013 1 次提交
    • R
      usb: phy: make PHY driver selection possible by controller drivers · 052a11d1
      Roger Quadros 提交于
      Convert PHY Drivers from menuconfig to menu so that the PHY drivers
      can be explicitely selected by the controller drivers.
      
      USB_PHY is no longer a user visible option. It is upto to the PHY
      drivers to select it if needed. This patch does so for the existing
      PHY drivers that use the USB_PHY library.
      
      Doing so moves the USB_PHY and PHY driver selection problem from the
      end user to the PHY and controller driver developer.
      
      e.g.
      
      Earlier, a controller driver (e.g. EHCI_OMAP) that needs to select
      a PHY driver (e.g. NOP_PHY) couldn't do so because the PHY driver
      depended on USB_PHY. Making the controller driver depend on USB_PHY
      has a negative effect i.e. it becomes invisible to the user till
      USB_PHY is enabled. Most end users will not familiar with this.
      
      With this patch, the end user just needs to select the controller driver
      needed for his/her platform without worrying about which PHY driver to
      select.
      
      Also update USB_EHCI_MSM, USB_LPC32XX and USB_OMAP to not depend
      on USB_PHY any more. They can safely select the necessary PHY drivers.
      
      [ balbi@ti.com : refreshed on top of my next branch. Changed bool
      	followed by default n into def_bool n ]
      
      CC: Pavankumar Kondeti <pkondeti@codeaurora.org>
      Acked-by: NRoland Stigge <stigge@antcom.de>
      Signed-off-by: NRoger Quadros <rogerq@ti.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      052a11d1
  13. 27 7月, 2013 1 次提交
    • P
      usb: limit OMAP related USB options to OMAP2PLUS platforms · 4e682bbd
      Paul Gortmaker 提交于
      commit 57f6ce07 ("usb: phy:
      add a new driver for usb3 phy") added the new Kconfig option
      OMAP_USB3, but it had no dependencies whatsoever, and hence
      became available across all arch/platforms.
      
      Which presumably caused this to show up in x86 randconfig:
      
          warning: (USB_MUSB_HDRC && OMAP_USB3) selects \
              OMAP_CONTROL_USB which has unmet direct \
              dependencies (USB_SUPPORT && ARCH_OMAP2PLUS)
      
      Then commit 6992819f ("usb: phy:
      fix Kconfig warning") was added.  However, this just deleted the
      ARCH_OMAP2PLUS dependency from OMAP_CONTROL_USB, further
      compounding the problem by opening up OMAP_CONTROL_USB to
      all arch/platforms as well.
      
      Earlier it was suggested[1] that we revert the change of 6992819f
      to restore the dependency, and add a same ARCH_OMAP2PLUS dependency
      to the new OMAP_USB3 entry.  However that was discouraged on the
      grounds of people wanting the extra sanity compile testing on x86,
      even though the driver could probably never be used there.
      
      Now we have CONFIG_COMPILE_TEST, so developers who value the ability
      to compile drivers on an architecture that it never can be used for
      can have that, and people who want dependencies to shield them from
      seeing options that aren't relevant to their platform get what they
      want too.
      
      Here we restore the dependency but couple it with COMPILE_TEST, in
      order to achieve both of the above goals.
      
      [1] https://patchwork.kernel.org/patch/2194511/Acked-by: NFelipe Balbi <balbi@ti.com>
      Cc: Kishon Vijay Abraham I <kishon@ti.com>
      Cc: Moiz Sonasath <m-sonasath@ti.com>
      Cc: Jiri Slaby <jslaby@suse.cz>
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4e682bbd
  14. 19 6月, 2013 1 次提交
  15. 11 6月, 2013 1 次提交
    • S
      phy-rcar-usb: add R8A7778 support · 54407f19
      Sergei Shtylyov 提交于
      The driver currently only supports R8A7779 SoC. Compared to it, R8A7778 USB-PHY
      has extra register range containing two high-speed signal quality characteristic
      control registers which should be set up  during USB-PHY  startup depending on
      whether a ferrite bead is in use or not.  So, we now handle an optional second
      memory range in the driver's probe method, add the 'ferrite_bead' field to the
      driver's platform data, and add an extra (optional) step to the USB-PHY startup
      routine which sets up the extended registers.
      
      Also mark in the driver's Kconfig section  that R8A7778 is now supported and
      generally clarify that section, uppercasing the word "phy" and also changing
      the module name that got lost in the big driver rename, while at it...
      
      The patch has been tested on the Marzen and BOCK-W boards.
      Signed-off-by: NSergei Shtylyov <sergei.shtylyov@cogentembedded.com>
      Acked-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      54407f19
  16. 29 5月, 2013 1 次提交
  17. 16 5月, 2013 1 次提交
  18. 15 5月, 2013 1 次提交
  19. 24 4月, 2013 1 次提交
    • A
      usb: phy: phy core cannot yet be a module · 4623245c
      Arnd Bergmann 提交于
      A lot of platform code calls into the usb phy core at the moment, which
      does not work if it is built as a loadable module. This will hopefully
      change when those platforms are all converted to DT based probing,
      but for now, the easiest solution is to change it from "tristate"
      to "bool".
      
      This solves at least these ARM allmodconfig build errors:
      
      arch/arm/mach-imx/built-in.o: In function `imx_otg_ulpi_create':
      arch/arm/mach-imx/ulpi.c:117: undefined reference to `otg_ulpi_create'
      arch/arm/mach-omap2/built-in.o: In function `usbhs_init_phys':
      arch/arm/mach-omap2/usb-host.c:652: undefined reference to `usb_bind_phy'
      arch/arm/mach-omap2/built-in.o: In function `omap_2430sdp_init':
      arch/arm/mach-omap2/board-2430sdp.c:236: undefined reference to `usb_bind_phy'
      arch/arm/mach-omap2/built-in.o: In function `omap3_beagle_init':
      arch/arm/mach-omap2/board-omap3beagle.c:554: undefined reference to `usb_bind_phy'
      arch/arm/mach-omap2/built-in.o: In function `devkit8000_init':
      arch/arm/mach-omap2/board-devkit8000.c:596: undefined reference to `usb_bind_phy'
      arch/arm/mach-omap2/built-in.o: In function `omap_ldp_init':
      arch/arm/mach-omap2/board-ldp.c:379: undefined reference to `usb_bind_phy'
      drivers/built-in.o: In function `ab8500_charger_probe':
      drivers/power/ab8500_charger.c:3629: undefined reference to `usb_get_phy'
      drivers/power/ab8500_charger.c:3706: undefined reference to `usb_put_phy'
      drivers/built-in.o: In function `ab8500_charger_remove':
      drivers/power/ab8500_charger.c:3411: undefined reference to `usb_put_phy'
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4623245c
  20. 27 3月, 2013 2 次提交
    • R
      usb: Fix compile error by selecting USB_OTG_UTILS · c8fa48d3
      Roland Stigge 提交于
      The current lpc32xx_defconfig breaks like this, caused by recent phy
      restructuring:
      
        LD      init/built-in.o
      drivers/built-in.o: In function `usb_hcd_nxp_probe':
      drivers/usb/host/ohci-nxp.c:224: undefined reference to `isp1301_get_client'
      drivers/built-in.o: In function `lpc32xx_udc_probe':
      drivers/usb/gadget/lpc32xx_udc.c:3104: undefined reference to
      `isp1301_get_client' distcc[27867] ERROR: compile (null) on localhost failed
      make: *** [vmlinux] Error 1
      
      Caused by 1c208881 (usb: Makefile: fix
      drivers/usb/phy/ Makefile entry)
      
      This patch fixes this by selecting USB_OTG_UTILS in Kconfig which
      causes the phy driver to be built again.
      Signed-off-by: NRoland Stigge <stigge@antcom.de>
      Acked-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c8fa48d3
    • F
      usb: gadget: mv_u3d: drop ARCH dependency · 60630c2e
      Felipe Balbi 提交于
      this driver compiles fine everywhere which
      means we can use linux-next to compile it
      for us frequently.
      
      By dropping the arch dependency, we also
      ensure driver writers don't add virtual
      arch-depdencies to the driver by e.g. using
      the wrong headers.
      
      While at that, fix Marvell's USB3 PHY dependency,
      that's the driver which depends on CPU_MM3, not
      mv_u3d_core.
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      60630c2e
  21. 18 3月, 2013 5 次提交
  22. 29 1月, 2013 1 次提交
  23. 25 1月, 2013 3 次提交
  24. 23 1月, 2013 1 次提交
  25. 18 1月, 2013 1 次提交
  26. 17 12月, 2012 1 次提交
  27. 01 11月, 2012 1 次提交
  28. 07 9月, 2012 1 次提交
    • K
      usb: phy: add a new driver for omap usb2 phy · 657b306a
      Kishon Vijay Abraham I 提交于
      All phy related programming like enabling/disabling the clocks, powering
      on/off the phy is taken care of by this driver. It is also used for OTG
      related functionality like srp.
      
      This also includes device tree support for usb2 phy driver and
      the documentation with device tree binding information is updated.
      
      Currently writing to control module register is taken care in this
      driver which will be removed once the control module driver is in place.
      
      Cc: Felipe Balbi <balbi@ti.com>
      Signed-off-by: NKishon Vijay Abraham I <kishon@ti.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      657b306a
  29. 09 8月, 2012 1 次提交
  30. 27 6月, 2012 1 次提交
  31. 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