On Wednesday 08 February 2017 16:17:45, Mathias Nyman wrote:
> On 08.02.2017 15:44, Alexander Stein wrote:
> > This patch adds support for USB2 test mode (Test_J, Test_K,
> > Test_SE0_NAK and Test_Packet) per XHCI spec 4.19.6.
> >
> > USB2 test mode is a required
;Wang, Yu"
Signed-off-by: "Li, Guanglei"
Signed-off-by: "Wu, Hao"
Signed-off-by: Alexander Stein
---
Changes in v2:
* Added additional info about USB2 test modes itself into commit message
* Add URL for same test mode feature on ehci hosts.
dr
On Wednesday 08 February 2017 13:53:30, Greg Kroah-Hartman wrote:
> On Wed, Feb 08, 2017 at 11:26:35AM +0100, Alexander Stein wrote:
> > This patch adds support for USB2 test mode (Test_J, Test_K,
> > Test_SE0_NAK and Test_Packet) per XHCI spec 4.19.6.
>
> What does that m
This patch adds support for USB2 test mode (Test_J, Test_K,
Test_SE0_NAK and Test_Packet) per XHCI spec 4.19.6.
Signed-off-by: "Wang, Yu"
Signed-off-by: "Li, Guanglei"
Signed-off-by: "Wu, Hao"
Signed-off-by: Alexander Stein
---
This patch was taken
This allows someone to grep for the complete warning message as in;
xhci-hcd xhci-hcd.0.auto: USB core suspending device not in U0/U1/U2.
Signed-off-by: Alexander Stein
---
drivers/usb/host/xhci-hub.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/usb/host/xhci
On Wednesday 26 March 2014 13:38:29, Oliver Neukum wrote:
> On Wed, 2014-03-26 at 13:18 +0100, Alexander Stein wrote:
> > On Wednesday 26 March 2014 12:38:24, Oliver Neukum wrote:
> > > On Tue, 2014-03-25 at 10:34 +0100, Alexander Stein wrote:
> > > > As the module
On Wednesday 26 March 2014 11:01:54, Dan Williams wrote:
> On Tue, 2014-03-25 at 10:34 +0100, Alexander Stein wrote:
> > As the module does not use the standard USB mechanism, the appropriate
> > product and vendor IDs have to be added.
>
> Should these really be going into u
On Wednesday 26 March 2014 12:38:24, Oliver Neukum wrote:
> On Tue, 2014-03-25 at 10:34 +0100, Alexander Stein wrote:
> > As the module does not use the standard USB mechanism, the appropriate
> > product and vendor IDs have to be added.
>
> Wait, stop. How do you make sure
As the module does not use the standard USB mechanism, the appropriate
product and vendor IDs have to be added.
Signed-off-by: Michael Ulbricht
Signed-off-by: Alexander Stein
---
drivers/usb/serial/usb-serial-simple.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff
From: Michael Ulbricht
By specifying NO_UNION_NORMAL the ACM driver does only use the first two
USB interfaces (modem data & control). The AT Port, Diagnostic and NMEA
interfaces are left to the USB serial driver.
Signed-off-by: Michael Ulbricht
Signed-off-by: Alexander Stein
---
drivers
On Wednesday 16 October 2013 15:29:53, Alan Stern wrote:
> > > > I'm experiencing problems with our USB-CAN-hardware in a test scenario
> > > > only when being attached to the ehci root-hub.
> > > > When the device is enumerated and has its USB address the driver is
> > > > bound and the can inte
On Wednesday 16 October 2013 11:07:50, Alan Stern wrote:
> On Wed, 16 Oct 2013, Alexander Stein wrote:
>
> > Hello,
> >
> > I'm experiencing problems with our USB-CAN-hardware in a test scenario only
> > when being attached to the ehci root-hub.
> > When
Hello,
I'm experiencing problems with our USB-CAN-hardware in a test scenario only
when being attached to the ehci root-hub.
When the device is enumerated and has its USB address the driver is bound and
the can interface is started. So far so good. If there is a status request
timeout the modul
13 matches
Mail list logo
