lkml.org 
[lkml]   [2011]   [Apr]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [RFC] Regulator state after regulator_get
Date


> -----Original Message-----
> From: ext Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]
> Sent: 28. huhtikuuta 2011 14:15
> To: Jokiniemi Kalle (Nokia-SD/Tampere)
> Cc: lrg@slimlogic.co.uk; mchehab@infradead.org; svarbatov@mm-sol.com;
> saaguirre@ti.com; grosikopulos@mm-sol.com; Zutshi Vimarsh (Nokia-
> SD/Helsinki); Ailus Sakari (Nokia-SD/Helsinki); linux-kernel@vger.kernel.org;
> linux-media@vger.kernel.org
> Subject: Re: [RFC] Regulator state after regulator_get
>
> On Thu, Apr 28, 2011 at 11:08:08AM +0000, kalle.jokiniemi@nokia.com wrote:
>
> > I don't have a full set of regulators described, that's why things broke when
> > I tried the regulator_full_constraints call earlier. But I don't think it would be
> too
> > big issue to check the current after boot configuration and define all the
> > regulators as you suggest. I will try this approach.
>
> As I said in my previous mail if you've got a reagulator you don't know
> about which is on you can give it an always_on constraint until you
> figure out what (if anything) should be controlling it.

Yeps, I plan to check the PMIC for the regulators that are left on after boot
In the current working setup and then put those "always_on" flags on those
regulators in the final setup.

Thanks for the help!

- Kalle


\
 
 \ /
  Last update: 2011-04-28 14:01    [W:0.225 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site