On Tue, 6 Jan 2015, vichy wrote: > > 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? No. > 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) If you want to find out what's happening, add some debugging printk statements to autosuspend_check() in drivers/usb/core/driver.c. Maybe also to usb_runtime_suspend(). You might also want to enable CONFIG_PM_ADVANCED_DEBUG and see what the other runtime_* files in the .../power directory say. Alan Stern -- 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
