04 Oct, 2014
2 commits
-
Instead of calling xhci_compliance_mode_recovery_timer_quirk_check() again
in the PCI suspend path, just check for XHCI_COMP_MODE_QUIRK which will
have been set based on xhci_compliance_mode_recovery_timer_quirk_check()
in xhci_init().Signed-off-by: Andrew Bresticker
Signed-off-by: Mathias Nyman
Signed-off-by: Greg Kroah-Hartman -
Since the struct hc_driver is mostly the same across the xhci-pci,
xhci-plat, and the upcoming xhci-tegra driver, introduce the function
xhci_init_driver() which will populate the hc_driver with the default
xHCI operations. The caller must supply a setup function which will
be used as the hc_driver's reset callback.Note that xhci-plat also overrides the default ->start() callback so
that it can do rcar-specific initialization.Signed-off-by: Andrew Bresticker
Signed-off-by: Mathias Nyman
Signed-off-by: Greg Kroah-Hartman
29 Sep, 2014
8 commits
-
Add the generic PHY support, analogous to the USB PHY support. Intended it to be
used with the PCI EHCI/OHCI drivers and the xHCI platform driver.Signed-off-by: Sergei Shtylyov
Signed-off-by: Yoshihiro Shimoda
Signed-off-by: Greg Kroah-Hartman -
The USB PHY member of the HCD structure is renamed to 'usb_phy' and
modifications are done in all drivers accessing it.
This is in preparation to adding the generic PHY support.Signed-off-by: Antoine Tenart
[Sergei: added missing 'drivers/usb/misc/lvstest.c' file, resolved rejects,
updated changelog.]
Signed-off-by: Sergei Shtylyov
Acked-by: Alan Stern
Acked-by: Felipe Balbi
Signed-off-by: Greg Kroah-Hartman -
Patch "usb: gadget: uvc: rename functions to avoid conflicts with host uvc"
renamed a lot of symbols but missed one references that was inside of
an #ifdef:drivers/usb/gadget/function/uvc_v4l2.c:363:23: error: 'uvcg_v4l2_get_unmapped_area' undeclared here (not in a function)
.get_unmapped_area = uvcg_v4l2_get_unmapped_area,
^
drivers/usb/gadget/function/uvc_v4l2.c:344:22: warning: 'uvc_v4l2_get_unmapped_area' defined but not used [-Wunused-function]
static unsigned long uvc_v4l2_get_unmapped_area(struct file *file,
^This renames the reference according the changed function name.
Signed-off-by: Arnd Bergmann
Fixes: 7ea95b110811 ("usb: gadget: uvc: rename functions to avoid conflicts with host uvc")
Cc: Andrzej Pietrasiewicz
Cc: Michael Grzeschik
Acked-by: Laurent Pinchart
Cc: Felipe Balbi
Signed-off-by: Greg Kroah-Hartman -
The newly added sti ehci and ohci drivers come with a single
Kconfig entry that does not depend on either of the base drivers,
which leads to a link error when they are disabled:drivers/built-in.o: In function `ohci_platform_init':
:(.init.text+0x14788): undefined reference to `ohci_init_driver'To fix that, this patch introduces two separate Kconfig options
with proper dependencies, which avoids the problem and is also
more consistent with the other glue drivers.Signed-off-by: Arnd Bergmann
Fixes: d115837259ada ("usb: host: ohci-st: Add OHCI driver support for ST STB devices")
Cc: Peter Griffin
Acked-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
Now that we have completely moved from older USB-PHY drivers
to newer GENERIC-PHY drivers for PHYs available with USB controllers
on Exynos series of SoCs, we can remove the support for the same
in our host drivers too.We also defer the probe for our host in case we end up getting
EPROBE_DEFER error when getting PHYs.Signed-off-by: Vivek Gautam
Acked-by: Jingoo Han
Acked-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman -
The current code only returns -ENOTSUPP for OTG host, but in fact,
embedded host also needs to returns -ENOTSUPP if the peripheral
is not at TPL.Signed-off-by: Peter Chen
Signed-off-by: Greg Kroah-Hartman -
There is no need to init .owner field.
Based on the patch from Peter Griffin
"mmc: remove .owner field for drivers using module_platform_driver"This patch removes the superflous .owner field for drivers which
use the module_platform_driver API, as this is overriden in
platform_driver_register anyway."Signed-off-by: Kiran Padwal
Reviewed-by: Ivan T. Ivanov
Signed-off-by: Greg Kroah-Hartman -
Commit 0cce2eda19923e5e5ccc8b042dec5af87b3ffad0
USB: fix LANGID=0 regressiondefaults to a langid of 0x0409 if it's not properly implemented by the
device. Explain with a higher level error message what this means.Signed-off-by: Scot Doyle
Signed-off-by: Greg Kroah-Hartman
25 Sep, 2014
7 commits
-
With this patch, USB activity can be signaled by blinking a LED. There
are two triggers, one for activity on USB host and one for USB gadget.Both triggers should work with all host/device controllers. Tested only
with musb.Performace: I measured performance overheads on ARM Cortex-A8 (TI
AM335x) running on 600 MHz.Duration of usb_led_activity():
- with no LED attached to the trigger: 2 ± 1 µs
- with one GPIO LED attached to the trigger: 2 ± 1 µs or 8 ± 2 µs (two peaks in histogram)Duration of functions calling usb_led_activity() (with this patch
applied and no LED attached to the trigger):
- __usb_hcd_giveback_urb(): 10 - 25 µs
- usb_gadget_giveback_request(): 2 - 6 µsSigned-off-by: Michal Sojka
Acked-by: Felipe Balbi
Tested-by: Felipe Balbi
Signed-off-by: Greg Kroah-Hartman -
In the next commit, we will want the usb-common module to be composed of
two object files. Since Kbuild cannot "append" another object to an
existing one, we need to rename usb-common.c to something
else (common.c) and create usb-common.o by linking the wanted objects
together. Currently, usb-common.o comprises only common.o.Signed-off-by: Michal Sojka
Acked-by: Felipe Balbi
Tested-by: Felipe Balbi
Signed-off-by: Greg Kroah-Hartman -
Use the recently introduced usb_gadget_giveback_request() in favor of
direct invocation of the completion routine.All places in drivers/usb/ matching "[-.]complete(" were replaced with a
call to usb_gadget_giveback_request(). This was compile-tested with all
ARM drivers enabled and runtime-tested for musb.Signed-off-by: Michal Sojka
Acked-by: Felipe Balbi
Tested-by: Felipe Balbi
Signed-off-by: Greg Kroah-Hartman -
All USB peripheral controller drivers call completion routines directly.
This patch adds usb_gadget_giveback_request() which will be used instead
of direct invocation in the next patch. The goal here is to have a place
where common functionality can be added.Signed-off-by: Michal Sojka
Acked-by: Felipe Balbi
Tested-by: Felipe Balbi
Signed-off-by: Greg Kroah-Hartman -
This patch moves the part of code that initializes the PHY bus width.
This results in simpler code and removes the need to check whether
the Generic PHY Framework is used.Signed-off-by: Kamil Debski
Signed-off-by: Marek Szyprowski
Signed-off-by: Robert Baldyga
Signed-off-by: Greg Kroah-Hartman -
…/linux-phy into usb-next
Kishon writes:
Adds 3 new PHY drivers stih407, stih41x and rcar gen2 PHY. It also
includes miscellaneous cleanup of other PHY drivers.Conflicts:
MAINTAINERS -
…it/johan/usb-serial into usb-next
Johan writes:
USB-serial fixes for v3.17
Here are two more device IDs for v3.17.
Signed-off-by: Johan Hovold <johan@kernel.org>
24 Sep, 2014
23 commits
-
This patch removes the superflous .owner field for drivers which
use the module_platform_driver or platform_driver_register api,
as this is overriden in __platform_driver_register.Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
Currently the DP_PHY_ENABLE register is mapped in the driver,
and accessed to control power to the PHY.
With mfd-syscon and regmap interface available at our disposal,
it's wise to use that instead of using a 'reg' property for the
controller and allocating a memory resource for that.To facilitate this, we have added another compatible string
for Exynso5420 SoC to acquire driver data which contains
different DP-PHY-CONTROL register offset.Signed-off-by: Vivek Gautam
Cc: Jingoo Han
Cc: Kishon Vijay Abraham I
Signed-off-by: Kishon Vijay Abraham I -
This patch adds the new phy-sti41x-usb.c PHY driver found on
STMicroelectronics stih41x consumer electronics SoC's into the STI
arch section of the maintainers file.Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
This patch adds dt documentation bindings for the usb phy found
on STiH415/5 SoC's from STMicroelectronics, which support USB 1.1 and 2.0.Signed-off-by: Maxime Coquelin
Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
This driver adds support for USB (1.1 and 2.0) phy for STiH415 and
STiH416 System-On-Chips from STMicroelectronics.Signed-off-by: Maxime Coquelin
Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
This patch adds the new phy-stih407-usb.c usb phy driver found on
STMicroelectronics stih407 consumer electronics SoC's into the STI
arch section of the maintainers file.Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
This patch adds the dt documentation for the usb picophy found on stih407 SoC family
available from STMicroelectronics.Signed-off-by: Giuseppe Cavallaro
Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
This is the generic phy driver for the picoPHY ports used by the
USB2 and USB3 Host controllers when controlling usb2/1.1 devices. It
is found on STiH407 SoC family from STMicroelectronics.Signed-off-by: Giuseppe Cavallaro
Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
We're using threaded irq on a I2C bus and we're sleeping in
twl4030_usb_irq() as it calls twl4030_usb_linkstat() which
calls the i2c functions. If we ever need to lock for longer
I2C transaction sequences a mutex will allow us to do that
easily.Signed-off-by: Tony Lindgren
Signed-off-by: Kishon Vijay Abraham I -
There's no longer need for tracking the phy state in the driver
with asleep, we can now rely on runtime PM.Signed-off-by: Tony Lindgren
Signed-off-by: Kishon Vijay Abraham I -
We don't need twl4030_phy_power() any longer now that we have
the runtime PM calls. Let's get rid of it as it's confusing.
No functional changes, just move the code and use res instead
of ret as we are not returning that value.Signed-off-by: Tony Lindgren
Signed-off-by: Kishon Vijay Abraham I -
We can now let the interrupt and delayed work do all that's
needed with runtime PM.Signed-off-by: Tony Lindgren
Signed-off-by: Kishon Vijay Abraham I -
It's not being used any longer.
Signed-off-by: Tony Lindgren
Signed-off-by: Kishon Vijay Abraham I -
Using the module_platform_driver macro to register the driver as this gets
rid of a lot of the boilerplate code.Also remove .owner field as this gets overridden in __platform_driver_register.
Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
Use the module_platform_driver macro to register the driver as this gets
rid of a lot of the boilerplate code.Also remove .owner field as this gets overridden in __platform_driver_register.
Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
The site specific OOM messages are unncessary, because they duplicate
messages from the memory subsystem which include dump_stack().Removing these superflous messages makes the kernel smaller. A discussion
here http://patchwork.ozlabs.org/patch/324158/ found that all error paths
from kzalloc will print a error message, and that any error path which maybe
found which doesn't would be considered a bug in kzalloc.Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
The site specific OOM messages are unncessary, because they duplicate
messages from the memory subsystem which include dump_stack().Removing these superflous messages makes the kernel smaller. A discussion
here http://patchwork.ozlabs.org/patch/324158/ found that all error paths
from kzalloc will print a error message, and that any error path which maybe
found which doesn't would be considered a bug in kzalloc.Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
The site specific OOM messages are unncessary, because they duplicate
messages from the memory subsystem which include dump_stack().Removing these superflous messages makes the kernel smaller. A discussion
here http://patchwork.ozlabs.org/patch/324158/ found that all error paths
from kzalloc will print a error message, and that any error path which maybe
found which doesn't would be considered a bug in kzalloc.Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
The site specific OOM messages are unncessary, because they duplicate
messages from the memory subsystem which include dump_stack().Removing these superflous messages makes the kernel smaller. A discussion
here http://patchwork.ozlabs.org/patch/324158/ found that all error paths
from kzalloc will print a error message, and that any error path which maybe
found which doesn't would be considered a bug in kzalloc.Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
Currently this driver is missing a check on the return value of devm_kzalloc,
which would cause a NULL pointer dereference in a OOM situation.This patch adds the aformentioned missing check.
Signed-off-by: Peter Griffin
Acked-by: Andrew Lunn
Signed-off-by: Kishon Vijay Abraham I -
The site specific OOM messages are unncessary, because they duplicate
messages from the memory subsystem which include dump_stack().Removing these superflous messages makes the kernel smaller. A discussion
here http://patchwork.ozlabs.org/patch/324158/ found that all error paths
from kzalloc will print a error message, and that any error path which maybe
found which doesn't would be considered a bug in kzalloc.Signed-off-by: Peter Griffin
Signed-off-by: Kishon Vijay Abraham I -
This PHY, though formally being a part of Renesas USBHS controller, contains the
UGCTRL2 register that controls multiplexing of the USB ports (Renesas calls them
channels) to the different USB controllers: channel 0 can be connected to either
PCI EHCI/OHCI or USBHS controllers, channel 2 can be connected to PCI EHCI/OHCI
or xHCI controllers.This is a new driver for this USB PHY currently already supported under drivers/
usb/phy/. The reason for writing the new driver was the requirement that the
multiplexing of USB channels to the controller be dynamic, depending on what
USB drivers are loaded, rather than static as provided by the old driver. The
infrastructure provided by drivers/phy/phy-core.c seems to fit that purpose
ideally. The new driver only supports device tree probing for now.Signed-off-by: Sergei Shtylyov
Signed-off-by: Kishon Vijay Abraham I -
It seems that only choose_devnum() was not ready to process more hub
events at the same time.All should be fine if we take bus->usb_address0_mutex there. It will
make sure that more devnums will not be chosen for the given bus and
the related devices at the same time.Signed-off-by: Petr Mladek
Acked-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman
