On Tue, Feb 11, 2014 at 07:29:40PM -0800, Julius Werner wrote:
I believe I am seeing a polling livelock scenario as described by Julius.
Julius was talking about what happens when the host controller itself
gets reset (and therefore remembers nothing about any device) whereas
the device
Hi,
+ Paul as he might have better details about the Synopsys core host-side
implementation
On Tue, Feb 18, 2014 at 12:42:53PM -0800, Sarah Sharp wrote:
On Tue, Feb 11, 2014 at 07:29:40PM -0800, Julius Werner wrote:
I believe I am seeing a polling livelock scenario as described by
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Tuesday, February 18, 2014 1:05 PM
Hi,
+ Paul as he might have better details about the Synopsys core host-side
implementation
On Tue, Feb 18, 2014 at 12:42:53PM -0800, Sarah Sharp wrote:
On Tue, Feb 11, 2014 at 07:29:40PM -0800, Julius
Julius, are you sure the Synopsys host will actually power off the
ports? The Intel hosts need some special ACPI methods, so I'm not sure
if Dan's issue with ports after power on could even be seen on the
Synopsys host.
The Synopsys issue (as I remember it, please correct me if I'm wrong)
On Tue, Feb 18, 2014 at 2:40 PM, Julius Werner jwer...@chromium.org wrote:
Can you take a look at it, and see if it would address your issue? I
think it will catch the case where we transition from SS.Inactive -
RxDetect - Polling.
I don't think that's targeting the same problem. Hans seems
We don't need to change hub_port_debounce() right away... that was
just an additional suggestion to make things more efficient for
SuperSpeed devices in general. I think for now (in order to solve
Dan's problem), it would be best if he just calls hub_port_debounce()
in
On Tue, Feb 18, 2014 at 3:39 PM, Julius Werner jwer...@chromium.org wrote:
We don't need to change hub_port_debounce() right away... that was
just an additional suggestion to make things more efficient for
SuperSpeed devices in general. I think for now (in order to solve
Dan's problem), it
On Mon, 10 Feb 2014, Dan Williams wrote:
I believe I am seeing a polling livelock scenario as described by Julius.
Julius was talking about what happens when the host controller itself
gets reset (and therefore remembers nothing about any device) whereas
the device still thinks it is in U3. Is
I believe I am seeing a polling livelock scenario as described by Julius.
Julius was talking about what happens when the host controller itself
gets reset (and therefore remembers nothing about any device) whereas
the device still thinks it is in U3. Is that the scenario you're
On Fri, 31 Jan 2014, Dan Williams wrote:
Resuming a powered down port sometimes results in the port state being
stuck in USB_SS_PORT_LS_POLLING:
hub 3-0:1.0: debounce: port 1: total 2000ms stable 0ms status 0x2e0
port1: can't get reconnection after setting port power on, status -110
On Mon, Feb 10, 2014 at 1:26 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Fri, 31 Jan 2014, Dan Williams wrote:
Resuming a powered down port sometimes results in the port state being
stuck in USB_SS_PORT_LS_POLLING:
hub 3-0:1.0: debounce: port 1: total 2000ms stable 0ms status 0x2e0
11 matches
Mail list logo
