On 04/01/18 01:12, Matthew Dharm wrote:
The TUR commands come from the sd_mod (I think). Definitely not from
usb-storage. So I would take it up at that level.
Thanks Matt. I'm going to do that. And that information also helps me
try to find the right code to patch.
--
To unsubscribe from th
On 19.12.2017 12:16, yinbo@nxp.com wrote:
From: yinbo.zhu
When a transaction error (defined in Section 4.10.2.3, "USB
Transaction Error" of the xHCI Specification) occurs on the
USB, the host controller reports this through a transfer
event with the completion code "USB Transaction Error".
On 19.12.2017 12:16, yinbo@nxp.com wrote:
From: yinbo.zhu
This is a occasional problem where the software issues an End
Transfer command while a USB transfer is in progress,
resulting in the TxFIFO being flushed when the lower layer is
waiting for data, causing the super speed (ss) transmi
On Wed, Jan 03, 2018 at 07:53:02PM +0100, Christian Holl wrote:
> This adds the ELV ALC 8xxx Battery Charging device
> to the list of USB IDs of drivers/usb/serial/cp210x.c
>
> Signed-off-by: Christian Holl
> ---
Thanks for resending, this one applied just fine.
Johan
--
To unsubscribe from thi
On 19.12.2017 12:16, yinbo@nxp.com wrote:
From: yinbo.zhu
This issue is observed in USB 2.0 mode when the USB 3.0 host
controller is connected to a FS/LS device via a hub. The
host controller issues start-split (SSPLIT) and (CSPLIT)
tokens to accomplish a split-transaction. A
split-transact
On 01/04/2018 06:58 AM, Jun Sun wrote:
Hi, all,
I'm playing with USB gadget with configfs on raspberry pi zero w. My
goal is to setup a generic functionfs function that uses Windows OS
descriptor so that windows would automatically install winusb driver.
It seems I would have to
- enable MS-
On Thu, 4 Jan 2018, Maxim Moseychuk wrote:
> Some low-speed devices (for example, bluetooth) do not have
> time to initialize. For them, ETIMEDOUT is a valid error.
> We need to give them another try. Otherwise, they will
> never be initialized correctly and in dmesg will be messages
> "Bluetooth:
On Wed, 3 Jan 2018, Matthew Dharm wrote:
> The TUR commands come from the sd_mod (I think). Definitely not from
> usb-storage. So I would take it up at that level.
>
> Matt
>
> On Wed, Jan 3, 2018 at 4:25 PM, Eduardo Trápani wrote:
> > Usually the kernel reads the pendrive like this:
> >
> >
В Чт, 04/01/2018 в 11:57 -0500, Alan Stern пишет:
> On Thu, 4 Jan 2018, Maxim Moseychuk wrote:
>
> > Some low-speed devices (for example, bluetooth) do not have
> > time to initialize. For them, ETIMEDOUT is a valid error.
> > We need to give them another try. Otherwise, they will
> > never be ini
But under some conditions, the last TEST UNIT READY is not being sent
and because of that, on this device: Kingston DT 101 G2, the drive's
activity light keeps on blinking even though nothing is being done (no
read/writes/inquiries).
In addition to Matt's comments, it's worth pointing out that t
Hello,
I need some advice how to debug a device, that under Windows presents 2
virtual com ports. Windows .sys. file mentions a "Jungo CDC ACM OBEX
Driver".
I get the following dmesg output
> [ 1700.263981] usb 1-1.4: new full-speed USB device number 10 using
> ehci-pci
> [ 1700.378186] usb 1-1
Some low-speed and full-speed devices (for example, bluetooth)
do not have time to initialize. For them, ETIMEDOUT is a valid error.
We need to give them another try. Otherwise, they will
never be initialized correctly and in dmesg will be messages
"Bluetooth: hci0 command 0x1002 tx timeout" or sim
On 01/03/2018 02:18 AM, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_dbg debug message.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/usb/usbip/vhci_rx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/usbip/vhci_
Add USB device support.
Signed-off-by: Chris Brandt
---
arch/arm/boot/dts/r7s72100.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/r7s72100.dtsi b/arch/arm/boot/dts/r7s72100.dtsi
index ab9645a42eca..eb414e735185 100644
--- a/arch/arm/boot/dts/r7s7
This patch adds the capability to support RZ/A1 SoCs.
Signed-off-by: Chris Brandt
---
drivers/usb/renesas_usbhs/Makefile | 2 +-
drivers/usb/renesas_usbhs/common.c | 17 +
drivers/usb/renesas_usbhs/common.h | 6 +
drivers/usb/renesas_usbhs/rza.c| 52
This series adds RZ/A1 gadget support to the renesas_usbhs driver.
Basically, it's almost the same HW as the R-Car (and SH) parts.
The only real difference is the some extra registers for the PHY.
This was tested on an RSK board by connecting to a PC as an
Ethernet CDC gadget.
Chris Brandt (3):
Document support for RZ/A1 SoCs
Signed-off-by: Chris Brandt
---
Documentation/devicetree/bindings/usb/renesas_usbhs.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
b/Documentation/devicetree/bindings/usb/renesas_usbhs.txt
index 4
On 12/29/2017 3:34 AM, Marc Zyngier wrote:
> On Wed, 27 Dec 2017 20:37:07 +,
> Troy Kisky wrote:
>>
>> On 12/27/2017 2:37 AM, Marc Zyngier wrote:
>>> On Tue, 26 Dec 2017 21:57:58 +,
>>> Troy Kisky wrote:
On 12/26/2017 1:52 PM, Troy Kisky wrote:
> On 12/25/2017 2:10 AM, Marc Zy
18 matches
Mail list logo
