[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140610100232.GD5099@sirena.org.uk>
Date: Tue, 10 Jun 2014 11:02:32 +0100
From: Mark Brown <broonie@...nel.org>
To: Chanwoo Choi <cw00.choi@...sung.com>
Cc: lgirdwood@...il.com, grant.likely@...aro.org, robh+dt@...nel.org,
myungjoo.ham@...sung.com, kyungmin.park@...sung.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 1/2] regulator: of: Add support for parsing
regulator_state for suspend state
On Tue, Jun 10, 2014 at 08:59:01AM +0900, Chanwoo Choi wrote:
> On 06/10/2014 04:21 AM, Mark Brown wrote:
> > If we're going to do that we'd need to define what modes mean in the DT
> > binding - currently there's no support for modes at all because it's
> > complicated to come up with sensible and meaningful generic defintions.
> The 'regulator-mode' of this patch means following defined constant variable
> as following in include/linux/regulator/consumer.h:
> #define REGULATOR_MODE_FAST 0x1
> #define REGULATOR_MODE_NORMAL 0x2
> #define REGULATOR_MODE_IDLE 0x4
> #define REGULATOR_MODE_STANDBY 0x8
> If regulator consumer would use this mode('regulator-mode),
> specific regulator driver should implement rdev->desc->ops->set_suspend_mode function
> to control regulator state according to 'regulator-mode' in suspend state.
Sure, but what do those mean?
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists