[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111204155433.GA16287@opensource.wolfsonmicro.com>
Date: Sun, 4 Dec 2011 15:54:35 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Thomas Abraham <thomas.abraham@...aro.org>
Cc: Rajendra Nayak <rnayak@...com>, grant.likely@...retlab.ca,
robherring2@...il.com, linaro-dev@...ts.linaro.org,
patches@...aro.org, tony@...mide.com,
devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
olof@...om.net, linux-omap@...r.kernel.org, lrg@...com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v5 1/4] regulator: helper routine to extract
regulator_init_data
On Sun, Dec 04, 2011 at 06:51:23PM +0530, Thomas Abraham wrote:
> For regulators that are not turned on by bootloader, and which require
> 'apply_uV' constraint, is there any alternative for turning on the
> regulator when using dt?
If the regulator isn't software managed then always_on covers this - the
regulator core will enable any always_on regulators that haven't been
enabled already.
> /* do we need to apply the constraint voltage */
> - if (rdev->constraints->apply_uV &&
> - rdev->constraints->min_uV == rdev->constraints->max_uV) {
> + if ((rdev->constraints->apply_uV &&
> + rdev->constraints->min_uV == rdev->constraints->max_uV) ||
> + (!rdev->constraints->boot_on && rdev->constraints->always_on)) {
> ret = _regulator_do_set_voltage(rdev,
> rdev->constraints->min_uV,
> rdev->constraints->max_uV);
I'm not sure I understand the intended logic there. Voltage constraints
and enable/disable constraints are orthogonal here.
--
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