From owner-p4-projects@FreeBSD.ORG Tue Dec 9 19:07:29 2003 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 2F9DA16A4D0; Tue, 9 Dec 2003 19:07:29 -0800 (PST) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F25F616A4CE for ; Tue, 9 Dec 2003 19:07:28 -0800 (PST) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2574C43D29 for ; Tue, 9 Dec 2003 19:07:28 -0800 (PST) (envelope-from takawata@freebsd.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.12.9/8.12.9) with ESMTP id hBA37RXJ052306 for ; Tue, 9 Dec 2003 19:07:27 -0800 (PST) (envelope-from takawata@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.12.9/8.12.9/Submit) id hBA37RoX052303 for perforce@freebsd.org; Tue, 9 Dec 2003 19:07:27 -0800 (PST) (envelope-from takawata@freebsd.org) Date: Tue, 9 Dec 2003 19:07:27 -0800 (PST) Message-Id: <200312100307.hBA37RoX052303@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to takawata@freebsd.org using -f From: Takanori Watanabe To: Perforce Change Reviews Subject: PERFORCE change 43707 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 03:07:29 -0000 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.