Assign ports previously owned by the EHCI controllers to the XHCI
controller. There are two external USB ports (UTMI ports 0/2 and
USB3 ports 0/1) and an internal USB port (UTMI port 1). PCIe lanes
0 and 1 are used by the USB3 ports.
Signed-off-by: Andrew Bresticker abres...@chromium.org
---
Assign USB ports previously owned by the EHCI controllers to the XHCI
controller. There is a mini-PCIe USB port (UTMI port 1) and a USB A
connector (UTMI port 2, USB3 port 0). PCIe lane 0 is used for USB3
port 0.
Signed-off-by: Andrew Bresticker abres...@chromium.org
---
In addition to the PCIe and SATA PHYs, the XUSB pad controller also
supports 3 UTMI, 2 HSIC, and 2 USB3 PHYs. Each USB3 PHY uses a single
PCIe or SATA lane and is mapped to one of the three UTMI ports.
Signed-off-by: Andrew Bresticker abres...@chromium.org
---
Add support for the on-chip XHCI host controller present on Tegra SoCs.
The driver is currently very basic: it loads the controller with its
firmware, starts the controller, and is able to service messages sent
by the controller's firmware. The hardware supports device mode as
well as runtime
Add nodes for the Tegra XUSB mailbox and Tegra XHCI controller.
Update the XUSB pad controller node with a phandle to the XUSB
mailbox.
Signed-off-by: Andrew Bresticker abres...@chromium.org
---
arch/arm/boot/dts/tegra124.dtsi | 31 +++
1 file changed, 31
Add device-tree binding documentation for the XHCI controller present
on Tegra124 and later SoCs.
Signed-off-by: Andrew Bresticker abres...@chromium.org
---
.../bindings/usb/nvidia,tegra124-xhci.txt | 76 ++
1 file changed, 76 insertions(+)
create mode 100644
Add new bindings used for USB support by the Tegra XUSB pad controller.
This includes additional PHY types, USB-specific pinconfig properties, etc.
Signed-off-by: Andrew Bresticker abres...@chromium.org
---
.../pinctrl/nvidia,tegra124-xusb-padctl.txt| 53 --
Add device-tree bindings for the Tegra XUSB mailbox which will be used
for communication between the Tegra XHCI controller and the host.
Signed-off-by: Andrew Bresticker abres...@chromium.org
---
.../bindings/mailbox/nvidia,tegra124-xusb-mbox.txt | 25 ++
1 file changed, 25
The Tegra XHCI controller communicates requests to the host through
a mailbox interface. Host drivers which can handle these requests,
such as the Tegra XUSB pad controller driver and upcoming Tegra XHCI
host controller driver, can send messages and register to be notified
of incoming messages.
This series adds support for XHCI on NVIDIA Tegra SoCs. This includes:
- extending the XUSB pad controller driver to support the USB PHY
types (UTMI, HSIC, and USB3),
- adding a driver for the mailbox used to communicate with the XHCI
controller's firmware, and
- adding a XHCI
On Tue, Jun 17, 2014 at 03:44:58PM -0700, Greg Kroah-Hartman wrote:
On Fri, Jun 13, 2014 at 11:35:13AM +0300, Alexey Tulia wrote:
This fixes the following warning:
- WARNING: __constant_cpu_to_le32 should be cpu_to_le32
What produces this warning?
This warning was found by
On Wed, 2014-06-18 at 00:06 -0700, Greg Kroah-Hartman wrote:
On Wed, Jun 18, 2014 at 09:49:39AM +0300, Alexey Tulia wrote:
On Tue, Jun 17, 2014 at 03:44:58PM -0700, Greg Kroah-Hartman wrote:
On Fri, Jun 13, 2014 at 11:35:13AM +0300, Alexey Tulia wrote:
This fixes the following warning:
On 18 June 2014 10:05, Jingoo Han jg1@samsung.com wrote:
Make of_device_id array const, because all OF functions handle
it as const.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/usb/host/ehci-spear.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 18 June 2014 10:08, Jingoo Han jg1@samsung.com wrote:
Make of_device_id array const, because all OF functions handle
it as const.
Signed-off-by: Jingoo Han jg1@samsung.com
---
drivers/usb/host/ohci-spear.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, Jun 17, 2014 at 07:41:44PM +0300, Janne Kanniainen wrote:
This driver adds support for USB controlled led panels that exists in
MSI GT683R laptop
Changes in v2:
- sorted headers to alphabetic order
- using devm_kzalloc
- using BIT(n)
- using usb_control_msg
ping ?
From: Kuninori Morimoto kuninori.morimoto...@renesas.com
Current usbhs gadget driver didn't complete STATUS stage after receiving.
It wasn't problem for us before, because some USB class doesn't use
DATA OUT stage in control transfer.
But, it is required on some device.
Dan Williams dan.j.willi...@intel.com writes:
I put patch 3 usb: fix hub-port pm_runtime_enable() vs runtime pm
transitions through it's paces, but I'd still like to see a positive
test report from Bjørn... even if it's too late to add a Tested-by.
Fixes the problem for me. Thanks
Bjørn
--
From: vichy
hi david:
...
From one of the patches (not applied) I sent last November ...
Include the unknown address when the DMA pointer from an event isn't part
of the current TD. This will happen if the error code is TRB error.
do you mean below patch?
This reverts commit 1af54b7a4.
The commit tried to address cases in which isochronous transfers are 'not
reliable', most probably in the tests conducted, polling for the
MUSB_TXCSR_TXPKTRDY bit in MUSB_TXCSR is done too late.
Hence, it installs a work struct which basically busy-polls for the
The musb/cppi41 code installs a hrtimer to work around DMA completion
interrupts that have fired too early on AM335x hardware. This timer
is currently programmed to first fire 140 nanoseconds after the DMA
completion callback. According to the commit which introduced it
(a655f481d83, usb: musb:
Hi,
I've been debugging issues with musb in host mode and both full-speed
and high-speed USB audio devices with cppi41 DMA mode enabled.
The effect that was observed with full-speed devices was that CPU load
went up to 100% due to the dma channels dma_completion work struct.
For FS devices, the
From: Of Daniel Mack
Sent: 18 June 2014 10:28
To: ba...@ti.com; george.cher...@ti.com; bige...@linutronix.de
Cc: sebastian.reim...@googlemail.com; linux-usb@vger.kernel.org; Daniel Mack
Subject: [PATCH 2/2] usb: musb: cppi41: fire hrtimer according to programmed
channel length
The
On 06/18/2014 11:32 AM, David Laight wrote:
From: Of Daniel Mack
Sent: 18 June 2014 10:28
To: ba...@ti.com; george.cher...@ti.com; bige...@linutronix.de
Cc: sebastian.reim...@googlemail.com; linux-usb@vger.kernel.org; Daniel Mack
Subject: [PATCH 2/2] usb: musb: cppi41: fire hrtimer according
+ Nishant and Rajendra for review.
On 05/05/2014 12:54 PM, Roger Quadros wrote:
Add the sysconfig class bits for the Super Speed USB
controllers
CC: Paul Walmsley p...@pwsan.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 12
1
On Wednesday 18 June 2014 04:40 PM, Roger Quadros wrote:
+ Nishant and Rajendra for review.
On 05/05/2014 12:54 PM, Roger Quadros wrote:
Add the sysconfig class bits for the Super Speed USB
controllers
CC: Paul Walmsley p...@pwsan.com
Signed-off-by: Roger Quadros rog...@ti.com
verified
On 06/18/2014 02:19 PM, Rajendra Nayak wrote:
On Wednesday 18 June 2014 04:40 PM, Roger Quadros wrote:
+ Nishant and Rajendra for review.
On 05/05/2014 12:54 PM, Roger Quadros wrote:
Add the sysconfig class bits for the Super Speed USB
controllers
CC: Paul Walmsley p...@pwsan.com
dear linuxfoundation:
Because of the usb driver parameters error that leads to failed in
reconnect. now i want to modify the error parameter and
move device pid fffe from zte_ev.c back to option.c for our company.
modify reason:
1. Move device pid fffe from zte_ev.c back to option.c for
On Wed, Jun 18 2014, Yang,Wei wrote:
On 06/17/2014 10:18 PM, Alan Stern wrote:
That is a strange question to ask. If you did not know that I approved
the patch, why did you insert my Acked-By:?
I added your Acked-By, as when you reviewed V3, you mentioned that I
*may* add your Acked-by in
Messages from the modem exceeding 256 bytes cause communication
failure.
The WDM protocol is strictly read on demand, meaning that we only
poll for unread data after receiving a notification from the modem.
Since we have no way to know how much data the modem has to send,
we must make sure that
This short series contains two patches intended for 3.16:
1/2: change some variable (and function) names to reflect their actual purpose
2/2: eliminate dependency on yet unknown interface numbers
Rebased onto Greg's usb-next with this series:
Function's interface directories need to be created when the function
directory is created, but interface numbers are not known until
the gadget is ready and bound to udc, so we cannot use numbers
as part of interface directory names.
Let the client decide what names to use.
Signed-off-by:
A number of variables serve a generic purpose of handling
compatible id and subcompatible id, but the names suggest they
are for rndis only. Rename to reflect variables' purpose.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/configfs.c | 32
hi David:
2014-06-18 16:45 GMT+08:00 David Laight david.lai...@aculab.com:
From: vichy
hi david:
...
From one of the patches (not applied) I sent last November ...
Include the unknown address when the DMA pointer from an event isn't part
of the current TD. This will happen if the error
I think this is good, even if I admit I am starting to feel pretty
unconfortable with this situation where a firmware is using an unknown
combination of two protocols, not respecting both AT spec and CDC WDM one.
That may explain why the device refuses some commands sometimes, such as
at+clac
.
Oh - I forgot to say: I can provide a tested-by in some hours. I have my E3131
at something like 2.1 KM going by feets, from here at University.
On Wed, 18 Jun 2014, Bjørn Mork wrote:
==Date: Wed, 18 Jun 2014 14:21:24
==From: Bjørn Mork bj...@mork.no
==To: net...@vger.kernel.org
==Cc:
On Wed, 2014-06-18 at 14:21 +0200, Bjørn Mork wrote:
Messages from the modem exceeding 256 bytes cause communication
failure.
The WDM protocol is strictly read on demand, meaning that we only
poll for unread data after receiving a notification from the modem.
Since we have no way to know
From: vichy
...
and I get error message as
platform-xhci: ERROR Transfer event TRB DMA ptr 483702160 not part of current
TD
platform-xhci: trb_comp_code = 0x1, event status -115, buffer
1cd4b590, len 100, flags 1038001
that seems wired.
complete code is success and not short package.
On Wed, Jun 18, 2014 at 1:18 AM, Bjørn Mork bj...@mork.no wrote:
Dan Williams dan.j.willi...@intel.com writes:
I put patch 3 usb: fix hub-port pm_runtime_enable() vs runtime pm
transitions through it's paces, but I'd still like to see a positive
test report from Bjørn... even if it's too late
On Tue, 17 Jun 2014, Dan Williams wrote:
In the case where platform firmware has specified conflicting values for
port locations it is confusing and otherwise not helpful to throw a
backtrace. Instead, include enough information to determine that
firmware has done something wrong and
On Tue, 17 Jun 2014, Dan Williams wrote:
Commit 9262c19d14c4 usb: disable port power control if not supported in
wHubCharacteristics gated enabling runtime pm for usb_port devices on
whether the parent hub supports power control, which causes a
regression. The port must still be allowed to
On Wed, 18 Jun 2014, Michal Nazarewicz wrote:
On Wed, Jun 18 2014, Yang,Wei wrote:
On 06/17/2014 10:18 PM, Alan Stern wrote:
That is a strange question to ask. If you did not know that I approved
the patch, why did you insert my Acked-By:?
I added your Acked-By, as when you reviewed
On Wed, Jun 18, 2014 at 7:54 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 17 Jun 2014, Dan Williams wrote:
Commit 9262c19d14c4 usb: disable port power control if not supported in
wHubCharacteristics gated enabling runtime pm for usb_port devices on
whether the parent hub supports
On Wed, 18 Jun 2014, Dan Williams wrote:
On Wed, Jun 18, 2014 at 7:54 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 17 Jun 2014, Dan Williams wrote:
Commit 9262c19d14c4 usb: disable port power control if not supported in
wHubCharacteristics gated enabling runtime pm for
This driver adds support for USB controlled led panels that exists in
MSI GT683R laptop
Signed-off-by: Janne Kanniainen janne.kanniai...@gmail.com
---
Changes in v2:
- sorted headers to alphabetic order
- using devm_kzalloc
- using BIT(n)
- using usb_control_msg
On Wed, Jun 18, 2014 at 07:05:02PM +0300, Janne Kanniainen wrote:
This driver adds support for USB controlled led panels that exists in
MSI GT683R laptop
Signed-off-by: Janne Kanniainen janne.kanniai...@gmail.com
Reviewed-by: Johan Hovold jo...@kernel.org
Thanks, Janne!
Johan
---
On Tue, Jun 17, 2014 at 8:47 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
3.10 is a pretty old kernel, you need to ask support from whoever gave
you that kernel, unless you can try v3.16-rc1 on your board.
Thanks for responding.
We are just running Vanilla 3.10 from kernel.org without any vendor
I am sorry - I am not in good conditions to perform the testing. But - I think
it sould be fine anyway.
Sorry Bjorn. I might be able to do it in the weekend if you would like.
Enrico
On Wed, 18 Jun 2014, Dan Williams wrote:
==Date: Wed, 18 Jun 2014 16:03:17
==From: Dan Williams d...@redhat.com
On 06/17/2014 05:17 AM, Wang, Yu Y wrote:
Hi All,
I have one question about Linux xHCI driver. Need your help to introduce more
backgrounds.
About the S3 flow:
1, Freeze all user processes.
2, Freeze all kernel threads (including workqueue thread).
3, Trying to suspend all devices.
While testing usb host on Qualcomm APQ8064, I encountered few issues.
These patches fixes those issues.
Without these patches USB is not functional on AQ8064.
All the patches are tested on IFC6410.
Thanks,
srini
Srinivas Kandagatla (3):
usb: Kconfig: make EHCI_MSM selectable for QCOM SOCs
This patch makes the msm ehci driver available to use on QCOM SOCs,
which have the same IP.
Signed-off-by: Srinivas Kandagatla srinivas.kandaga...@linaro.org
---
drivers/usb/host/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/Kconfig
This patch makes the phy reset clk and reset line optional as this clk
is not available on boards like IFC6410 with APQ8064.
Signed-off-by: Srinivas Kandagatla srinivas.kandaga...@linaro.org
---
drivers/usb/phy/phy-msm-usb.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff
Use case is when the phy is configured in host mode and a usb device is
attached to board before bootup. On bootup, with the existing code and
runtime pm enabled, the driver would decrement the pm usage count
without checking the current state of the phy. This pm usage count
decrement would
No problem. I think Dan's testing is sufficient verification that this doesn't
have unexpected side effects.
Bjørn
On 18 June 2014 18:32:58 CEST, Enrico Mioso mrkiko...@gmail.com wrote:
I am sorry - I am not in good conditions to perform the testing. But -
I think
it sould be fine anyway.
On Wed, 18 Jun 2014, Mathias Nyman wrote:
On 06/17/2014 05:17 AM, Wang, Yu Y wrote:
Hi All,
I have one question about Linux xHCI driver. Need your help to introduce
more backgrounds.
About the S3 flow:
1, Freeze all user processes.
2, Freeze all kernel threads (including
On Wed, Jun 18, 2014 at 12:17:55AM -0700, Joe Perches wrote:
On Wed, 2014-06-18 at 00:06 -0700, Greg Kroah-Hartman wrote:
On Wed, Jun 18, 2014 at 09:49:39AM +0300, Alexey Tulia wrote:
On Tue, Jun 17, 2014 at 03:44:58PM -0700, Greg Kroah-Hartman wrote:
On Fri, Jun 13, 2014 at 11:35:13AM
This driver adds support for USB controlled led panels that exists in
MSI GT683R laptop
Signed-off-by: Janne Kanniainen janne.kanniai...@gmail.com
Reviewed-by: Johan Hovold jo...@kernel.org
Thanks, Janne!
Johan
Thank you for reviewing my patch :) I sure learnt a
lot from you and if I
On Wed, Jun 18, 2014 at 09:41:35PM +0300, Janne Kanniainen wrote:
This driver adds support for USB controlled led panels that exists in
MSI GT683R laptop
Signed-off-by: Janne Kanniainen janne.kanniai...@gmail.com
Reviewed-by: Johan Hovold jo...@kernel.org
Thanks, Janne!
Johan
On Wed, Jun 18, 2014 at 9:17 AM, Barry G mr.sc...@gmail.com wrote:
NIP [c02b3f58] usb_gadget_map_request+0x118/0x1a4
LR [c02bc68c] fsl_ep_queue+0xc4/0x19c
Call Trace:
[dfff7ea8] [c02bc68c] fsl_ep_queue+0xc4/0x19c
[dfff7ec8] [c02b7514] composite_setup+0x1324/0x13e8
[dfff7f20] [c02bd070]
On Wed, Jun 18, 2014 at 4:47 PM, Barry G mr.sc...@gmail.com wrote:
Seems to me the right solution is making a patch to add the 83XX stuff
to the id_table
and finding the right place to set_dma_ops? I am fine doing the leg work of
creating/testing/submitting the patch providing that sounds
On Wed, Jun 18, 2014 at 1:00 PM, Fabio Estevam feste...@gmail.com wrote:
Can't you use the chipidea driver instead of
drivers/usb/gadget/fsl_udc_core.c?
I was under the impression that the chipidea stuff was for iMX series
processors.
The comments in fsl_udc_core.c say it is for the MPC8349E
On Wed, Jun 18, 2014 at 5:31 PM, Barry G mr.sc...@gmail.com wrote:
On Wed, Jun 18, 2014 at 1:00 PM, Fabio Estevam feste...@gmail.com wrote:
Can't you use the chipidea driver instead of
drivers/usb/gadget/fsl_udc_core.c?
I was under the impression that the chipidea stuff was for iMX series
On Wed, 18 Jun 2014, Johan Hovold wrote:
This driver adds support for USB controlled led panels that exists in
MSI GT683R laptop
Signed-off-by: Janne Kanniainen janne.kanniai...@gmail.com
Reviewed-by: Johan Hovold jo...@kernel.org
Thanks, Janne!
Now applied. Thanks Janne for the
On 06/18/2014 07:44 PM, Michal Nazarewicz wrote:
On Wed, Jun 18 2014, Yang,Wei wrote:
On 06/17/2014 10:18 PM, Alan Stern wrote:
That is a strange question to ask. If you did not know that I approved
the patch, why did you insert my Acked-By:?
I added your Acked-By, as when you reviewed V3,
From: David Mosberger-Tang dav...@egauge.net
Signed-off-by: Davidm Mosberger dav...@egauge.net
---
drivers/usb/host/max3421-hcd.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/host/max3421-hcd.c b/drivers/usb/host/max3421-hcd.c
index f8ecd7d..6dbf1e9 100644
---
From: David Mosberger-Tang dav...@egauge.net
Bit fields are not MP-safe.
Signed-off-by: Davidm Mosberger dav...@egauge.net
---
drivers/usb/host/max3421-hcd.c | 45 ++--
1 file changed, 20 insertions(+), 25 deletions(-)
diff --git
On Wed, 18 Jun 2014, Mathias Nyman wrote:
On 06/17/2014 05:17 AM, Wang, Yu Y wrote:
Hi All,
I have one question about Linux xHCI driver. Need your help to introduce
more backgrounds.
About the S3 flow:
1, Freeze all user processes.
2, Freeze all kernel threads (including
66 matches
Mail list logo
