Re: How to distinguish device classes which attached on port

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jul 03, 2013 at 10:42:10AM +0800, Huang Rui wrote:
> Hi,
> 
> Sometimes I was encounterd an issue that auto-wakeup at second time
> from S3 if use mouse to wakeup OS at first time.

I'm confused by this sentence.  Are you trying to get the system to come
out of S3 by using your mouse (e.g. clicking a mouse button)?  And
sometimes it doesn't work?

You're missing a bunch of details in this bug report as well:

1. What system are you running under?

2. What does `sudo lspci -vvv` show?

3. What kernel version are you running?

4. Does the problem with remote wakeup only occur with your mouse or
does it occur with other USB device classes?

5. Does the issue only occur with one particular mouse, or with all your
mice?

6. Do the effected mice work fine under a different xHCI host or EHCI
host?

> Then I reset the port
> which current status is connected in PORTSC during pci resume process
> in host controller driver (xHCI), this issue doesn't happen. But
> resetting all connected port is not good.

So resetting the port after resume from S3 allows the remote wakeup to
correctly propagate up during the second S3?

> So have you any ideas to
> distinguish that the device class is mouse which attached on port in
> host controller drivers?

You're proposing a solution before clearly defining the problem.  Please
explain to us, in detail, what the problem is, with step-by-step
instructions on how to reproduce it.

Sarah Sharp
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux