hi all: 2015-01-06 16:06 GMT+08:00 vichy <vichy.kuo@xxxxxxxxx>: > hi alan: > > 2015-01-06 8:39 GMT+08:00 vichy <vichy.kuo@xxxxxxxxx>: >> 2015-01-05 23:40 GMT+08:00 Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>: >>> On Mon, 5 Jan 2015, vichy wrote: >>> >>>> hi all: >>>> after tracing and reading kernel usb source code about run time and >>>> normal suspend. >>>> 1. how could we check the rum time suspend is work on some device? >>>> By plugging in devices and check whether >>>> /sys/bus/usb/devices/.../power/ is empty or not? >>> >>> No. That directory will never be empty. >>> >>> You can check whether runtime suspend works by enabling it: >>> >>> echo auto >/sys/bus/usb/devices/.../power/control >>> >>> You can see whether the device has been suspended by looking at the >>> runtime_status and runtime_suspended_time files in the .../power >>> directory. >>> > I use keyboard, it should be default support runtime suspend, for > testing runtime suspend like the attach log. > insert related modules, change related suspend parameters. > > But I cannot see the keyboard go to suspend even I force autosuspend as 0. > is there any other way to trigger runtime suspend immediately instead > of waiting kernel judge it is idle for a while? > I test the same keyboard on the NB is also not seeing autosuspend work. the kernel version of NB is 3.18 and my embedded system is 3.10 (I also attach usb descriptor of the keyboard I used in the mail) thanks for your help,
Attachment:
liteon.keyboard.desc.txt.tar.bz2
Description: BZip2 compressed data
