[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140306093826.GO13126@sirena.org.uk>
Date: Thu, 6 Mar 2014 17:38:26 +0800
From: Mark Brown <broonie@...nel.org>
To: Krzysztof Kozlowski <k.kozlowski@...sung.com>
Cc: Sangbeom Kim <sbkim73@...sung.com>,
Liam Girdwood <lgirdwood@...il.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org,
Kyungmin Park <kyungmin.park@...sung.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Tomasz Figa <t.figa@...sung.com>,
Yadwinder Singh Brar <yadi.brar@...sung.com>,
Sachin Kamat <sachin.kamat@...aro.org>
Subject: Re: [PATCH 2/3] regulator: s2mps11: Add set_suspend_disable for
S2MPS14
On Wed, Mar 05, 2014 at 10:22:52AM +0100, Krzysztof Kozlowski wrote:
> + ret = regmap_read(rdev->regmap, rdev->desc->enable_reg, &data);
> + if (ret < 0)
> + return ret;
> +
> + /*
> + * Don't enable suspend mode if regulator is already disabled because
> + * this would effectively for a short time turn on the regulator after
> + * resuming.
> + */
> + if (!(data & rdev->desc->enable_mask))
> + return 0;
> +
> + return regmap_update_bits(rdev->regmap, rdev->desc->enable_reg,
> + rdev->desc->enable_mask, S2MPS14_ENABLE_SUSPEND);
> +}
What happens if the regulator gets enabled between this being called
and the device suspending? I'd expect this to be storing the state and
then changing what gets written during enable and disable operations (if
the hardware does what I think it does).
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists