> Did you run into an issue where port status change events weren't being
> generated because the Port Reset flag was set? I'm trying to figure out
> if this addresses a real issue you hit (and thus should be queued for
> stable), or if this is just a precaution.
As Benson said, we're seeing this
On Wed, Oct 16, 2013 at 4:57 PM, Sarah Sharp
wrote:
>
> Did you run into an issue where port status change events weren't being
> generated because the Port Reset flag was set? I'm trying to figure out
> if this addresses a real issue you hit (and thus should be queued for
> stable), or if this i
On Tue, Oct 15, 2013 at 05:45:00PM -0700, Julius Werner wrote:
> This patch adds the Port Reset Change flag to the set of bits that are
> preemptively cleared on init/resume of a hub. In theory this bit should
> never be set unexpectedly... in practice it can still happen if BIOS,
> SMM or ACPI cod
On Tue, 15 Oct 2013, Julius Werner wrote:
> This patch adds the Port Reset Change flag to the set of bits that are
> preemptively cleared on init/resume of a hub. In theory this bit should
> never be set unexpectedly... in practice it can still happen if BIOS,
> SMM or ACPI code plays around with
This patch adds the Port Reset Change flag to the set of bits that are
preemptively cleared on init/resume of a hub. In theory this bit should
never be set unexpectedly... in practice it can still happen if BIOS,
SMM or ACPI code plays around with USB devices without cleaning up
correctly. This is
