Date: Tue, 9 Dec 2003 19:07:27 -0800 (PST) From: Takanori Watanabe <takawata@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 43707 for review Message-ID: <200312100307.hBA37RoX052303@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=43707 Change 43707 by takawata@takawata_x31 on 2003/12/09 19:06:29 Add my comment. Affected files ... .. //depot/projects/power/notes#11 edit Differences ... ==== //depot/projects/power/notes#11 (text+ko) ==== @@ -28,6 +28,9 @@ that should be sufficient. - The generic PCI bus driver already does this - Need to turn on all non-PCI devices then when we probe/attach. + > Handle Notify events for every ACPI device object. The Notify events + requests device re-enumration...etc. Parent device driver may + install event handler. - define a bus method for powering up/down devices - bus_set_powerstate(parent, child, state) where state is on or off # actually on/off is insufficient for a power management daemon that @@ -58,11 +61,11 @@ commands like eject, etc. # methods should be unique. Command interfaces to userland should dispatch # the right method. Otherwise we've reinvented ioctl :-) + >Some PCMCIA mechanism should be replaced by this mechanism. - convert to a model of suspending the device via device_suspend()/resume() rather than detach()/attach() for turning devices on/off. - This may require fixes to drivers so that they continue to function appropriately when their hardware has been suspended - The second stage will be to make the powering off of devices more automated. This is still in early design stage. It may involve a powerd, it may involve intelligence in the kernel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312100307.hBA37RoX052303>