Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964973AbWBHRJK (ORCPT ); Wed, 8 Feb 2006 12:09:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965179AbWBHRJJ (ORCPT ); Wed, 8 Feb 2006 12:09:09 -0500 Received: from cavan.codon.org.uk ([217.147.92.49]:678 "EHLO vavatch.codon.org.uk") by vger.kernel.org with ESMTP id S964916AbWBHRJH (ORCPT ); Wed, 8 Feb 2006 12:09:07 -0500 Date: Wed, 8 Feb 2006 17:08:58 +0000 From: Matthew Garrett To: Greg KH Cc: linux-pm@lists.osdl.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [linux-pm] Re: [PATCH, RFC] [1/3] Generic in-kernel AC status Message-ID: <20060208170857.GA29818@srcf.ucam.org> References: <20060208125753.GA25562@srcf.ucam.org> <20060208130422.GB25659@srcf.ucam.org> <20060208165803.GA15239@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060208165803.GA15239@kroah.com> User-Agent: Mutt/1.5.9i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@codon.org.uk X-SA-Exim-Scanned: No (on vavatch.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3120 Lines: 125 On Wed, Feb 08, 2006 at 08:58:03AM -0800, Greg KH wrote: > > +void pm_set_ac_status(int (*ac_status_function)(void)) > > No extra line in there please. That matches the style used in the rest of the file. > And perhaps a bit more description of what this is used for? Ok. > > +{ > > + down(&pm_sem); > > Shouldn't this be a mutex? It is, isn't it? The name's somewhat misleading, but I was just using what already existed... > > + get_ac_status = ac_status_function; > > + up(&pm_sem); > > +} > > + > > +EXPORT_SYMBOL(pm_set_ac_status); > > No extra line between the function and the EXPORT_SYMBOL please. Sure. > Also, how about EXPORT_SYMBOL_GPL()? If that's considered reasonable, sure. > And, who will be using this interface, and what for? The backlight interface only supports exporting and setting the current brightness. For various bits of hardware, the AC and DC brightnesses are stored separately. Drivers would need to know which brightness value to export to userspace. I have an HP backlight driver here which would benefit from this, and I'm looking at the same issue for a Panasonic one. Here's an updated version, anyway. Signed-Off-By: Matthew Garrett diff --git a/include/linux/pm.h b/include/linux/pm.h index 5be87ba..59ece0f 100644 --- a/include/linux/pm.h +++ b/include/linux/pm.h @@ -129,6 +129,8 @@ struct pm_ops { extern void pm_set_ops(struct pm_ops *); extern struct pm_ops *pm_ops; +extern void pm_set_ac_status(int (*ac_status_function)(void)); +extern int pm_get_ac_status(void); extern int pm_suspend(suspend_state_t state); diff --git a/kernel/power/main.c b/kernel/power/main.c index 46110d5..929a3c0 100644 --- a/kernel/power/main.c +++ b/kernel/power/main.c @@ -15,7 +15,7 @@ #include #include #include - +#include #include "power.h" @@ -25,6 +25,7 @@ DECLARE_MUTEX(pm_sem); struct pm_ops *pm_ops = NULL; +int (*get_ac_status)(void); suspend_disk_method_t pm_disk_mode = PM_DISK_SHUTDOWN; /** @@ -39,6 +40,36 @@ void pm_set_ops(struct pm_ops * ops) up(&pm_sem); } +/** + * pm_set_ac_status - Set the ac status callback. Returns true if the + * system is on AC and has a registered callback. + * @ops: Pointer to function + */ + +void pm_set_ac_status(int (*ac_status_function)(void)) +{ + down(&pm_sem); + get_ac_status = ac_status_function; + up(&pm_sem); +} +EXPORT_SYMBOL_GPL(pm_set_ac_status); + +/** + * pm_get_ac_status - return true if the system is on AC + */ + +int pm_get_ac_status(void) +{ + int status=0; + + down (&pm_sem); + if (get_ac_status) + status = get_ac_status(); + up (&pm_sem); + + return status; +} +EXPORT_SYMBOL_GPL(pm_get_ac_status); /** * suspend_prepare - Do prep work before entering low-power state. -- Matthew Garrett | mjg59@srcf.ucam.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/