> > After I set VT6212L USB2.0 controller into D3hot > mode, > > connecting/disconnecting usb drive doesn't > generate > > any PME# assertion. > > No, it won't do any of that unless > CONFIG_USB_SUSPEND > is enabled. I've certainly observed the PME# bit be > set > in the PCI config space after forcing the HCD to put > such > controllers into D3hot through sysfs. > > But note that the whole USB wakeup mechanism happens > to > be marked EXPERIMENTAL. It's been tested in > isolation, > but not integrated with things like S1 or S3 sleep > ... > and the last time I tried to enable ACPI wakeup > (with > the /proc/acpi/wakeup file), it didn't work at all.
Thanks you, David. I will look into it see if we can get the PME# generated with an 'outdated' kernel(2.4.22). > > function 2 configuration in D3hot mode: > > > > 00 01 02 03 04 05 06 07 08 09 > 0a > > 0b 0c 0d 0e 0f > > ... etc. FYI it's much easier to understand "lspci > -vv" > than the hex dump; pass "-xxx" if you like too of > course. Have no lspci tool available since I am dealing with a SOC based embedded prototype. Have to use my own application to dump those registers. Regards, --Craig __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
