Fix soft lockup when resetting remote device attached
to usb host. Configuration:
pppd -> musb hub -> usb-serial -> gms modem
When gsm modem resets, musb rolls in incoming rx interrupts
which does not give any time to other application as result
it totally lock ups. Solution is to keep original log
On Tue, Apr 26, 2016 at 05:11:36AM +, Jun Li wrote:
> Hi
>
> > -Original Message-
> > From: Peter Chen [mailto:hzpeterc...@gmail.com]
> > Sent: Tuesday, April 26, 2016 11:47 AM
> > To: Jun Li
> > Cc: Roger Quadros ; st...@rowland.harvard.edu;
> > ba...@kernel.org; gre...@linuxfoundati
Hi,
Ivaylo Dimitrov writes:
> Looks like there's some issue with the USB gadgets and configfs.
>
> I'm seeing rmmod of the UDC driver cause a warning and then reboot
> hangs the system. This happens at least with v4.4, and I've reproduced
> it with dwc3 and musb so it seems t
Hi,
Grygorii Strashko writes:
> Now not all DMA paremters configured properly for "xhci-hcd" platform
> device which is created manually. For example: dma_pfn_offset, dam_ops
> and iommu configuration will not corresponds "dwc3" devices
> configuration. As result, this will cause problems like w
Hi Kishon,
On Wed, Apr 6, 2016 at 7:37 PM, Vivek Gautam wrote:
> Adding vendor specific directories in phy to group
> phy drivers under their respective vendor umbrella.
>
> Also updated the MAINTAINERS file to reflect the correct
> directory structure for phy drivers.
>
> Signed-off-by: Vivek G
Hi
> -Original Message-
> From: Peter Chen [mailto:hzpeterc...@gmail.com]
> Sent: Tuesday, April 26, 2016 11:47 AM
> To: Jun Li
> Cc: Roger Quadros ; st...@rowland.harvard.edu;
> ba...@kernel.org; gre...@linuxfoundation.org; peter.c...@freescale.com;
> dan.j.willi...@intel.com; jun...@fre
On Tue, Apr 26, 2016 at 02:07:56AM +, Jun Li wrote:
> > +struct usb_otg *usb_otg_register(struct device *dev,
> > +struct usb_otg_config *config)
> > +{
> > + struct usb_otg *otg;
> > + struct otg_wait_data *wait;
> > + int ret = 0;
> > +
> > + if (!dev || !c
Hi Mark,
On 04/26/2016 01:30 AM, Mark Brown wrote:
> On Mon, Apr 25, 2016 at 04:04:50PM +0800, Lu Baolu wrote:
>
>> +ret = device_property_read_string(dev, "gpio-name", &gpio_name);
>> +if (!ret) {
>> +gpiod = gpiod_get(dev, gpio_name, GPIOD_ASIS);
>> +if (!IS_ERR(g
Hi Mark,
On 04/26/2016 12:40 AM, Mark Brown wrote:
> On Mon, Apr 25, 2016 at 04:04:49PM +0800, Lu Baolu wrote:
>
>> This is needed to handle the GPIO connected USB vcc pin found on
>> Intel Baytrail devices.
> In what way is this needed? The we defualt to using the driver name if
> no platform ID
Hi Roger
> -Original Message-
> From: Roger Quadros [mailto:rog...@ti.com]
> Sent: Tuesday, April 05, 2016 10:05 PM
> To: st...@rowland.harvard.edu; ba...@kernel.org;
> gre...@linuxfoundation.org; peter.c...@freescale.com
> Cc: dan.j.willi...@intel.com; jun...@freescale.com;
> mathias.ny..
On Mon, Apr 25, 2016 at 12:55:42PM +0200, Lucas Stach wrote:
> The Chipidea EHCI core seems to behave sanely and doesn't need
> the IO watchdog. This kills off 10 non-deferrable wakeup events
> per second when the controller is otherwise idle.
>
What does this 10 wakeup events? From what I see, i
Hi Alan,
On 2016/4/25 22:43, Alan Stern wrote:
> On Sat, 23 Apr 2016, Jiancheng Xue wrote:
>
>> Some generic-ehci compatible controllers have more than one reset signal
>> lines, e.g., Synopsys DWC USB2.0 Host-AHB Controller has two resets bus_reset
>> and roothub_reset. Two more resets are added
On Mon, Apr 25, 2016 at 10:09:20AM +, Jun Li wrote:
> Hi
>
> > -Original Message-
> > From: Peter Chen [mailto:hzpeterc...@gmail.com]
> > Sent: Monday, April 25, 2016 2:23 PM
> > To: Jun Li
> > Cc: Peter Chen ; linux-usb@vger.kernel.org;
> > baolin.w...@linaro.org
> > Subject: Re: [PA
Hi,
On 04/26/2016 07:51 AM, Chanwoo Choi wrote:
> Hi Lu,
>
> On 2016년 04월 25일 17:04, Lu Baolu wrote:
>> GPIO resource could be retrieved through APCI as well.
>>
>> Signed-off-by: Lu Baolu
>> Reviewed-by: Felipe Balbi
>> Acked-by: Chanwoo Choi
>> ---
>> drivers/extcon/extcon-usb-gpio.c | 3 ++-
Hi,
On 04/26/2016 07:51 AM, Chanwoo Choi wrote:
> Hi Lu,
>
> On 2016년 04월 25일 17:04, Lu Baolu wrote:
>> This is needed to handle the GPIO connected USB ID pin found on
>> Intel Baytrail devices.
>>
>> Signed-off-by: Lu Baolu
>> Reviewed-by: Felipe Balbi
>> Acked-by: Chanwoo Choi
>> ---
>> driv
On 4/25/2016 12:26 PM, dingu...@opensource.altera.com wrote:
> From: Dinh Nguyen
>
> Allow for platforms that have a reset controller driver in place to bring
> the USB IP out of reset.
>
> Signed-off-by: Dinh Nguyen
> ---
> v7: Use devm_reset_control_get_optional()
> v6: fix 80 line checkpatch
Hi
> -Original Message-
> From: Roger Quadros [mailto:rog...@ti.com]
> Sent: Monday, April 25, 2016 10:04 PM
> To: Jun Li ; st...@rowland.harvard.edu; ba...@kernel.org;
> gre...@linuxfoundation.org; peter.c...@freescale.com
> Cc: dan.j.willi...@intel.com; jun...@freescale.com;
> mathias.ny
Hi Lu,
On 2016년 04월 25일 17:04, Lu Baolu wrote:
> GPIO resource could be retrieved through APCI as well.
>
> Signed-off-by: Lu Baolu
> Reviewed-by: Felipe Balbi
> Acked-by: Chanwoo Choi
> ---
> drivers/extcon/extcon-usb-gpio.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff
Hi Lu,
On 2016년 04월 25일 17:04, Lu Baolu wrote:
> This is needed to handle the GPIO connected USB ID pin found on
> Intel Baytrail devices.
>
> Signed-off-by: Lu Baolu
> Reviewed-by: Felipe Balbi
> Acked-by: Chanwoo Choi
> ---
> drivers/extcon/extcon-usb-gpio.c | 7 +++
> 1 file changed, 7
From: Vladimir Zapolskiy
The usb_get_phy() function returns either a valid pointer to phy or
ERR_PTR() error, check for NULL always fails and may lead to oops on
error path, fix this issue.
Signed-off-by: Vladimir Zapolskiy
Signed-off-by: Bin Liu
---
drivers/usb/musb/jz4740.c | 4 ++--
1 file
This reverts commit 2035772010db634ec8566b658fb1cd87ec47ac77.
Commit 20357720 claims throughput improvement for MSC/UVC, but I
don't see much improvement. Following are the MSC measurement using
dd on AM335x GP EVM.
with BCD_BH:read: 14.9MB/s, write: 20.9MB/s
without BCD_BH: read: 15.2MB/s, w
From: Tal Shorer
Some functions, such as f_sourcesink, rely on an endpoint's desc
field during their requests' complete() callback, so clear it only
_after_ nuking all requests to avoid NULL pointer dereference.
Signed-off-by: Tal Shorer
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_gadget
Hi Greg,
Here are a few fixes for musb for v4.6-rc6.
Tal's patch fixes a musb teardown bug which is uncovered by a g_zero
change in v4.3. HCD_BH flag does not bring any visible benefit but breaks
a few cases, so revert it. Vladimir's patch fixes pointer error check.
Please let me know if any cha
Signed-off-by: Heiko Bauke
---
drivers/net/usb/plusb.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/net/usb/plusb.c b/drivers/net/usb/plusb.c
index 22e1a9a..104fc10 100644
--- a/drivers/net/usb/plusb.c
+++ b/drivers/net/usb/plusb.c
@@ -102,7 +102,7 @@ static
From: Dinh Nguyen
Allow for platforms that have a reset controller driver in place to bring
the USB IP out of reset.
Signed-off-by: Dinh Nguyen
---
v7: Use devm_reset_control_get_optional()
v6: fix 80 line checkpatch warning in dev_err print
v5: updated error conditions for not finding the rese
Now not all DMA paremters configured properly for "xhci-hcd" platform
device which is created manually. For example: dma_pfn_offset, dam_ops
and iommu configuration will not corresponds "dwc3" devices
configuration. As result, this will cause problems like wrong DMA
addresses translation on platfor
Hi,
On 18.04.2016 10:55, Felipe Balbi wrote:
Hi,
Ivaylo Dimitrov writes:
Hi,
On 16.01.2016 12:40, Ivaylo Dimitrov wrote:
Hi,
On 16.01.2016 00:48, Tony Lindgren wrote:
Hi all,
Looks like there's some issue with the USB gadgets and configfs.
I'm seeing rmmod of the UDC driver cause a war
On 4/25/2016 12:30 AM, Philipp Zabel wrote:
> Hi John,
>
> Am Freitag, den 22.04.2016, 20:31 -0700 schrieb John Youn:
>> On 4/20/2016 2:31 PM, dingu...@opensource.altera.com wrote:
>>> From: Dinh Nguyen
>>>
>>> Allow for platforms that have a reset controller driver in place to bring
>>> the USB
I was planning to define all these bits in a separate future patch.
Would you rather prefer the magic numbers defined before fixing the bugs?
I guess I can do that. Is something like this acceptable?
/* CP210X_GET_FLOW/CP210X_SET_FLOW read/write these 0x10 bytes */
struct cp210x_flow_ctl {
On Mon, 25 Apr 2016, Matthew Giassa wrote:
>
> Good morning Alan,
>
> The most recent patch you provided resolved the lockup issue I have been
> encountering. I will carry out full release testing shortly to further
> validate it.
>
> Would this be something that could be proposed for inclusion
On Mon, Apr 25, 2016 at 04:04:50PM +0800, Lu Baolu wrote:
> + ret = device_property_read_string(dev, "gpio-name", &gpio_name);
> + if (!ret) {
> + gpiod = gpiod_get(dev, gpio_name, GPIOD_ASIS);
> + if (!IS_ERR(gpiod)) {
This doesn't look like it's a standard ACPI b
On Mon, 25 Apr 2016 16:25:03 +0100
wrote:
> From: Jim Baxter
>
> "Unable to handle kernel NULL pointer dereference at virtual address
> 0078" is reported with "PC is at eth_start_xmit+0x19c/0x378 [u_ether]"
>
> The failure scenario is seen when closing the NCM connection while the
> TCP/IP
Good morning Alan,
The most recent patch you provided resolved the lockup issue I have been
encountering. I will carry out full release testing shortly to further
validate it.
Would this be something that could be proposed for inclusion in the
kernel, pending cosmetic changes (ie: `alantest', et
On Mon, Apr 25, 2016 at 04:04:49PM +0800, Lu Baolu wrote:
> This is needed to handle the GPIO connected USB vcc pin found on
> Intel Baytrail devices.
In what way is this needed? The we defualt to using the driver name if
no platform ID table, AFAICT this is just restating the same string?
sig
From: Jim Baxter
"Unable to handle kernel NULL pointer dereference at virtual address
0078" is reported with "PC is at eth_start_xmit+0x19c/0x378 [u_ether]"
The failure scenario is seen when closing the NCM connection while the
TCP/IPv6 stack is still trying to transmit over NCM.
Defensive
Hi Shimoda-san,
On Thu, Apr 21, 2016 at 2:57 PM, Geert Uytterhoeven
wrote:
> On Thu, Apr 21, 2016 at 12:27 PM, Yoshihiro Shimoda
> wrote:
>>> > [1.565605] xhci-hcd ee00.usb: xHCI Host Controller
>>> > [1.570636] xhci-hcd ee00.usb: new USB bus registered, assigned
>>> > bus numbe
On 25.04.16 17:42, Jiri Kosina wrote:
> On Mon, 25 Apr 2016, Nazar Mokrynskyi wrote:
>
>> Needed for v2 of the device firmware, otherwise kernel will stuck for few
>> seconds and throw "usb_submit_urb(ctrl) failed: -1" early on system boot.
>>
>> Signed-off-by: Nazar Mokrynskyi
>> ---
>> No change
On Sat, 23 Apr 2016, Jiancheng Xue wrote:
> Some generic-ehci compatible controllers have more than one reset signal
> lines, e.g., Synopsys DWC USB2.0 Host-AHB Controller has two resets bus_reset
> and roothub_reset. Two more resets are added in this patch in order for this
> kind of controller t
On Mon, 25 Apr 2016, Nazar Mokrynskyi wrote:
> Needed for v2 of the device firmware, otherwise kernel will stuck for few
> seconds and throw "usb_submit_urb(ctrl) failed: -1" early on system boot.
>
> Signed-off-by: Nazar Mokrynskyi
> ---
> No changes, just resubmission to ensure absence of unde
On Thu, 14 Apr 2016, David Lechner wrote:
> We will be using a generic syscon device for the TI DA8XX SoC CFGCHIPx
> retisters. This will be used by a number of planned drivers including a
> new USB PHY driver and common clock framework drivers.
>
> The same defines are removed from the platform_
Peter,
On 21/04/16 09:52, Peter Chen wrote:
> On Tue, Apr 05, 2016 at 05:05:12PM +0300, Roger Quadros wrote:
>> It provides APIs for the following tasks
>>
>> - Registering an OTG/dual-role capable controller
>> - Registering Host and Gadget controllers to OTG core
>> - Providing inputs to and kic
Hi,
On 21/04/16 09:38, Jun Li wrote:
> Hi,
>
> ...
>>
>> /**
>> + * usb_gadget_start - start the usb gadget controller and connect to
>> +bus
>> + * @gadget: the gadget device to start
>> + *
>> + * This is external API for use by OTG core.
>> + *
>> + * Start the usb device controller and conne
Needed for v2 of the device firmware, otherwise kernel will stuck for few
seconds and throw "usb_submit_urb(ctrl) failed: -1" early on system boot.
Signed-off-by: Nazar Mokrynskyi
---
No changes, just resubmission to ensure absence of undesired line breaks
---
drivers/hid/hid-ids.h | 1
On Mon, 25 Apr 2016, Nazar Mokrynskyi wrote:
> This is the first time doing contribution to kernel, didn't know
> Thunderbird will break lines, but looks like I've just configured it
> correctly now, so should not happen again.
>
> I can re-send it if absolutely necessary.
Please do. It'll save
Hi,
On Monday 18 April 2016 05:20 PM, Thierry Reding wrote:
> On Wed, Apr 06, 2016 at 07:08:24PM +0200, Thierry Reding wrote:
> [...]
>> I attached what I came up with. It extends the OF PHY provider registry
>> by allowing an additional node to be specified that if specified will
>> serve as the
From: Konrad Leszczynski
if Start Transfer command fails, let's try a little
harder to figure out why the command failed and give
slightly better return codes. This will be usefulf
or isochronous endpoints, at least, which could
decide to retry a given request.
Signed-off-by: Konrad Leszczynski
The XHCI controller presents two USB buses to the system - one for USB2
and one for USB3. The hub init code (hub_port_init) is reentrant but
only locks one bus per thread, leading to a race condition failure when
two threads attempt to simultaneously initialise a USB2 and USB3 device:
[8.03484
On 25.04.16 15:24, Benjamin Tissoires wrote:
> On Apr 25 2016 or thereabouts, Nazar Mokrynskyi wrote:
>> Needed for v2 of the device firmware, otherwise kernel will stuck for few
>> seconds and throw "usb_submit_urb(ctrl) failed: -1" early on system boot.
>>
>> Signed-off-by: Nazar Mokrynskyi
>> -
Hello.
On 4/24/2016 8:09 PM, Konstantin Shkolnyy wrote:
The CRTCTS flag code intended to clear the SERIAL_XOFF_CONTINUE flag, but
CRTSCTS? Also, "is" missing before "intended"?
did it inconsistently. This change is non-functional for existing chips
because the driver never set the flag a
On Apr 25 2016 or thereabouts, Nazar Mokrynskyi wrote:
> Needed for v2 of the device firmware, otherwise kernel will stuck for few
> seconds and throw "usb_submit_urb(ctrl) failed: -1" early on system boot.
>
> Signed-off-by: Nazar Mokrynskyi
> ---
Looks good to me but your mailer might have man
Hello.
On 4/24/2016 8:08 PM, Konstantin Shkolnyy wrote:
A bug in the CRTSCT handling caused RTS to alternate between
CRTSCTS?
CRTSCTS=0 => "RTS transmits active signal" and
CRTSCTS=1 => "RTS receives flow control"
instead of
CRTSCTS=0 => "RTS is statically active" and
CRTSCTS=1 => "RTS r
Needed for v2 of the device firmware, otherwise kernel will stuck for few
seconds and throw "usb_submit_urb(ctrl) failed: -1" early on system boot.
Signed-off-by: Nazar Mokrynskyi
---
drivers/hid/hid-ids.h | 1 +
drivers/hid/usbhid/hid-quirks.c | 1 +
2 files changed, 2 insertions(+)
Hi,
Jim Lin writes:
> On 2016年04月22日 19:52, Felipe Balbi wrote:
>> * PGP Signed by an unknown key
>>
>>
>> Hi Jim,
>>
>> Jim Lin writes:
>>> Android N adds os_desc_compat in v2_descriptor by init_functionfs()
>>> (system/core/adb/usb_linux_client.cpp) to support automatic install
>>> of MTP dri
On 2016年04月22日 19:52, Felipe Balbi wrote:
* PGP Signed by an unknown key
Hi Jim,
Jim Lin writes:
Android N adds os_desc_compat in v2_descriptor by init_functionfs()
(system/core/adb/usb_linux_client.cpp) to support automatic install
of MTP driver on Windows for USB device mode.
Current __ff
The Chipidea EHCI core seems to behave sanely and doesn't need
the IO watchdog. This kills off 10 non-deferrable wakeup events
per second when the controller is otherwise idle.
Signed-off-by: Lucas Stach
---
I've only tested this on i.MX6 for now and would like to ask people
on CC to test on thei
On Wed, Apr 20, 2016 at 02:26:58PM -0400, Javier Martinez Canillas wrote:
> The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either
> built-in or as a module, use that macro instead of open coding the same.
>
> Signed-off-by: Javier Martinez Canillas
Now applied, thanks.
Johan
On Sat, Apr 09, 2016 at 01:02:28PM +0200, Julia Lawall wrote:
> The ftdi_sio_quirk structures are never modified, so declare them as const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
Now applied, thanks.
Johan
--
To unsubscribe from this list: send the line "unsubscr
On Sun, Apr 24, 2016 at 12:09:30PM -0500, Konstantin Shkolnyy wrote:
> Replaced several register write calls with one, to simplify adding error
> handling.
>
> Signed-off-by: Konstantin Shkolnyy
> ---
> drivers/usb/serial/cp210x.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-
On Sun, Apr 24, 2016 at 12:09:21PM -0500, Konstantin Shkolnyy wrote:
> Documented "magic numbers" used in the CRTSCT flag code in terms of
> register bit names from the chip specification.
Documenting these is long overdue. I even started adding defines just to
be able to review the first patch in
On Sun, Apr 24, 2016 at 12:09:10PM -0500, Konstantin Shkolnyy wrote:
> The CRTCTS flag code intended to clear the SERIAL_XOFF_CONTINUE flag, but
> did it inconsistently. This change is non-functional for existing chips
> because the driver never set the flag and it's clear by default.
>
> Signed-o
On Sun, Apr 24, 2016 at 12:08:55PM -0500, Konstantin Shkolnyy wrote:
> A bug in the CRTSCT handling caused RTS to alternate between
> CRTSCTS=0 => "RTS transmits active signal" and
> CRTSCTS=1 => "RTS receives flow control"
> instead of
> CRTSCTS=0 => "RTS is statically active" and
> CRTSCTS=1 => "
Hi
> -Original Message-
> From: Peter Chen [mailto:hzpeterc...@gmail.com]
> Sent: Monday, April 25, 2016 2:23 PM
> To: Jun Li
> Cc: Peter Chen ; linux-usb@vger.kernel.org;
> baolin.w...@linaro.org
> Subject: Re: [PATCH 5/5] doc: usb: ci-hdrc-usb2: add property usb-charger-
> detection
>
Hello,
I'm experiencing some issues with a FTDI serial-to-usb chip, which
becomes unresponsive (the endpoint is halted) while logging this
message:
ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped:
-32
Some searching [1] [2] revealed that I'm not the only one. Most people
r
Hi
> -Original Message-
> From: Peter Chen [mailto:hzpeterc...@gmail.com]
> Sent: Monday, April 25, 2016 2:15 PM
> To: Jun Li
> Cc: Peter Chen ; linux-usb@vger.kernel.org;
> baolin.w...@linaro.org
> Subject: Re: [PATCH 1/5] usb: chipidea: add usb charger detection support
>
> On Mon, Apr
Hi,
> -Original Message-
> From: Peter Chen [mailto:hzpeterc...@gmail.com]
> Sent: Monday, April 25, 2016 2:03 PM
> To: Jun Li
> Cc: Peter Chen ; linux-usb@vger.kernel.org;
> baolin.w...@linaro.org
> Subject: Re: [PATCH 4/5] usb: chipidea: imx: add usb charger detection for
> imx7d
>
> O
Hi Geert-san,
> From: Geert Uytterhoeven
> Sent: Monday, April 25, 2016 3:58 PM
>
> Hi Shimoda-san,
>
> On Mon, Apr 25, 2016 at 4:10 AM, Yoshihiro Shimoda
> wrote:
> >> From: Rob Herring
> >> Sent: Friday, April 22, 2016 10:29 PM
> >> On Fri, Apr 22, 2016 at 4:36 AM, Felipe Balbi
> >> wrote:
>
This is needed to handle the GPIO connected USB ID pin found on
Intel Baytrail devices.
Signed-off-by: Lu Baolu
Reviewed-by: Felipe Balbi
Acked-by: Chanwoo Choi
---
drivers/extcon/extcon-usb-gpio.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/extcon/extcon-usb-gpio.c b/dr
GPIO resource could be retrieved through APCI as well.
Signed-off-by: Lu Baolu
Reviewed-by: Felipe Balbi
Acked-by: Chanwoo Choi
---
drivers/extcon/extcon-usb-gpio.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/extcon/extcon-usb-gpio.c b/drivers/extcon/extcon-us
This is needed to handle the GPIO connected USB vcc pin found on
Intel Baytrail devices.
Signed-off-by: Lu Baolu
---
drivers/regulator/fixed.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/regulator/fixed.c b/drivers/regulator/fixed.c
index ff62d69..e6f376f 100644
--- a/driv
Several Intel platforms implement USB dual role by having completely
separate xHCI and dwc3 IPs in PCH or SOC silicons. These two IPs share
a single USB port. There is another external port mux which controls
where the data lines should go. While the USB controllers are part of
the silicon, the por
Add support to retrieve fixed voltage configure information through
ACPI interface. This is needed for Intel Bay Trail devices, where a
GPIO is used to control the USB vbus.
Signed-off-by: Lu Baolu
---
drivers/regulator/fixed.c | 48 +++
1 file changed
In some Intel platforms, a single usb port is shared between USB host
and device controller. The shared port is under control of GPIO pins.
This patch adds the support for USB GPIO controlled port mux.
[baolu: removed .owner per platform_no_drv_owner.cocci]
Signed-off-by: David Cohen
Signed-off-
Several Intel PCHs and SOCs have an internal mux that is used to
share one USB port between device controller and host controller.
The mux is handled through the Dual Role Configuration Register.
Signed-off-by: Heikki Krogerus
Signed-off-by: Lu Baolu
Signed-off-by: Wu Hao
Reviewed-by: Felipe Ba
Add a maintainer entry for Intel USB dual role mux drivers and
add myself as a maintainer.
Signed-off-by: Lu Baolu
---
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 03e00c7..e2609e6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5878,
In some Intel platforms, a single usb port is shared between USB host
and device controllers. The shared port is under control of a switch
which is defined in the Intel vendor defined extended capability for
xHCI.
This patch adds the support to detect and create the platform device
for the port mu
Some Intel platforms have an USB port mux controlled by GPIOs.
There's a single ACPI platform device that provides 1) USB ID
extcon device; 2) USB vbus regulator device; and 3) USB port
switch device. This MFD driver will split these 3 devices for
their respective drivers.
[baolu: removed .owner p
Intel SOC chips are featured with USB dual role. The host role is
provided by Intel xHCI IP, and the gadget role is provided by IP
from designware. Tablet platform designs always share a single
port for both host and gadget controllers. There is a mux to
switch the port to the right controller acco
Hi
> -Original Message-
> From: Peter Chen [mailto:hzpeterc...@gmail.com]
> Sent: Monday, April 25, 2016 11:27 AM
> To: Jun Li
> Cc: Peter Chen ; linux-usb@vger.kernel.org;
> baolin.w...@linaro.org
> Subject: Re: [PATCH 1/5] usb: chipidea: add usb charger detection support
>
> On Mon, Ap
Hi John,
Am Freitag, den 22.04.2016, 20:31 -0700 schrieb John Youn:
> On 4/20/2016 2:31 PM, dingu...@opensource.altera.com wrote:
> > From: Dinh Nguyen
> >
> > Allow for platforms that have a reset controller driver in place to bring
> > the USB IP out of reset.
> >
> > Signed-off-by: Dinh Nguy
79 matches
Mail list logo
