[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1232021071.4934.366.camel@vega.slimlogic.co.uk>
Date: Thu, 15 Jan 2009 12:04:30 +0000
From: Liam Girdwood <lrg@...mlogic.co.uk>
To: David Brownell <david-b@...bell.net>
Cc: Mark Brown <broonie@...ena.org.uk>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [patch 2.6.29-rc] regulator: add get_status()
On Wed, 2009-01-14 at 23:03 -0800, David Brownell wrote:
> From: David Brownell <dbrownell@...rs.sourceforge.net>
>
> Based on previous LKML discussions:
>
> * Update docs for regulator sysfs class attributes to highlight
> the fact that all current attributes are intended to be control
> inputs, including notably "state" and "opmode" which previously
> implied otherwise.
>
> * Define a new regulator driver get_status() method, which is the
> first method reporting regulator outputs instead of inputs.
> It can report on/off and error status; or instead of simply
> "on", report the actual operating mode.
>
> For the moment, this is a sysfs-only interface, not accessible to
> regulator clients. Such clients can use the current notification
> interfaces to detect errors, if the regulator reports them.
>
> Signed-off-by: David Brownell <dbrownell@...rs.sourceforge.net>
> ---
Applied.
Thanks
Liam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists