On Wed, 2019-09-11 at 20:27 +0200, Oliver Neukum wrote:
> Am Mittwoch, den 11.09.2019, 14:34 + schrieb Joakim Tjernlund:
> > On Wed, 2019-09-11 at 16:22 +0200, Oliver Neukum wrote:
> > > CAUTION: This email originated from outside of the organization. Do not
> > > click links or open attachmen
On 6.9.2019 8.36, Rick Tseng wrote:
NVIDIA 3.1 xHCI card would lose power when moving power state into D3Cold.
Thus we need to wait CNR bit to clear when xhci resmue as xhci init.
Signed-off-by: Rick Tseng
---
drivers/usb/host/xhci.c | 9 +
1 file changed, 9 insertions(+)
diff --git
A Mediatek based smartphone owner reports problems with USB
tethering in Linux. The verbose USB listing shows a rndis_host
interface pair (e0/01/03 + 10/00/00), but the driver fails to
bind with
[ 355.960428] usb 1-4: bad CDC descriptors
The problem is a failsafe test intended to filter out ACM
Am Donnerstag, den 12.09.2019, 07:09 + schrieb Joakim Tjernlund:
> On Wed, 2019-09-11 at 20:27 +0200, Oliver Neukum wrote:
> > Am Mittwoch, den 11.09.2019, 14:34 + schrieb Joakim Tjernlund:
> > > On Wed, 2019-09-11 at 16:22 +0200, Oliver Neukum wrote:
> > > > CAUTION: This email originated
Hi Chandana,
Thank you for the patch!
On 9/11/19 07:54, Chandana Kishori Chiluveru wrote:
> Add interconnect support in dwc3-qcom driver to vote for bus
> bandwidth.
>
> This requires for two different paths - from USB master to
> DDR slave. The other is from APPS master to USB slave.
>
> Signe
On Wed, 11 Sep 2019, Allen Blaylock wrote:
> So I do see the PORT_TEST SetFeature Request and Response when I use tcpdump
> to
> make a capture using usbmon. Unfortunately I am not as familiar with the raw
> usbmon output or some of the diagnostics output by usbmon so I may be missing
> somethin
On Thu, 12 Sep 2019, Alan Stern wrote:
> On Wed, 11 Sep 2019, Allen Blaylock wrote:
>
> > So I do see the PORT_TEST SetFeature Request and Response when I use
> > tcpdump to
> > make a capture using usbmon. Unfortunately I am not as familiar with the raw
> > usbmon output or some of the diagnost
Thank you Alan,
I am still working through understanding the usbmon and this is a helpful hint.
I will contact the device manufacturer and see if there is some alternative
method they recommend for testing.
>Most of the usbmon output shows that a device was attached to port 3 of hub 2
>and enu
If an endpoint is encountered that returns USB3_LPM_DEVICE_INITIATED, keep
checking further endpoints, as there might be periodic endpoints later
that return USB3_LPM_DISABLED due to shorter service intervals.
Without this, the code can set too high a maximum-exit-latency and
prevent the use of mu
Dear Friend,
Hello how are you doing? Please, I am still waiting for your reply on the
message I sent you yesterday
Thanks
Mrs Jessica Becker.
On Fri, 2019-09-13 at 00:49 +1000, Jan Schmidt wrote:
> If an endpoint is encountered that returns USB3_LPM_DEVICE_INITIATED, keep
> checking further endpoints, as there might be periodic endpoints later
> that return USB3_LPM_DISABLED due to shorter service intervals.
>
> Without this, the code c
>I should add that the USB 2.0 spec includes the following text (from section
>11.24.2.13):
>
>Test mode of a downstream facing port can only be used in
>a well defined sequence of hub states. This sequence is
>defined as follows:
>
>1) All enabled downstream facin
On Thu, 12 Sep 2019, Allen Blaylock wrote:
> >I should add that the USB 2.0 spec includes the following text (from section
> >11.24.2.13):
> >
> >Test mode of a downstream facing port can only be used in
> >a well defined sequence of hub states. This sequence is
> >defined
13 matches
Mail list logo