[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

From: Huki Huang When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens.

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

From: Huki Huang When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens.

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3 usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

[PATCH v2] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device

RE: [PATCH] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

On Mon, 11 Jul 2016: Alan Stern wrote: > On Mon, 11 Jul 2016, Huang, Huki wrote: > > When end user inserts a usb3 device and put dut to s3. > What does "dut" mean? DUT : Device under test > > Then hotplug the usb3 disk under s3. > Do you mean that the devic

FW: [PATCH] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

On Mon, 11 Jul 2016: Alan Stern wrote: > On Mon, 11 Jul 2016, Huang, Huki wrote: > > When end user inserts a usb3 device and put dut to s3. > What does "dut" mean? DUT : Device under test > > Then hotplug the usb3 disk under s3. > Do you mean that the devic

[PATCH] usb3: Fixed usb3 device is not detected in s0 when hotplug usb3 disk under S3

When end user inserts a usb3 device and put dut to s3. Then hotplug the usb3 disk under s3. The device will be lost upon resuming from s3. There is a corner case that the hub->change_bits for the usb3 port is not set when usb port change event happens. This will cause hub driver ignore the device