Hi! >>> I works on an hardware that have the gsm connect to wm8753 and the >>> bluetooth subsystem >>> too direct connected. So I would like that a phone call for example >>> remains on during >>> system suspend. With this approch I can disable suspend of an entire >>> subtree of device, >>> that can be used by other hardware component. This change avoid any >>> specific change to the >>> driver. >> >> Why do you want to avoid changing the driver, actually? >> > Because, the driver may be connected to other device and you must change > the entire > set. This simple modification can help to share devices on an embedded > board and control > suspend/resume enable from user space. I don't know if it can be usefull > on broken board/device too. Do you see any possible risk with this > change? Yes. Most devices (on a PC for example) will not like this being enabled, right? So you are basically introducing a "break me" sysfs variable. I guess you should audit the drivers you are interested in to see if they can survive with the hardware alive while the rest of system is suspended, then add the option to the ones that can. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
