RE: [RFC] Regulator state after regulator_get

[kalle.jokiniemi]

 > -----Original Message-----
 > From: ext Mark Brown [mailto:broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx]
 > Sent: 28. huhtikuuta 2011 14:15
 > To: Jokiniemi Kalle (Nokia-SD/Tampere)
 > Cc: lrg@xxxxxxxxxxxxxxx; mchehab@xxxxxxxxxxxxx; svarbatov@xxxxxxxxxx;
 > saaguirre@xxxxxx; grosikopulos@xxxxxxxxxx; Zutshi Vimarsh (Nokia-
 > SD/Helsinki); Ailus Sakari (Nokia-SD/Helsinki); linux-kernel@xxxxxxxxxxxxxxx;
 > linux-media@xxxxxxxxxxxxxxx
 > Subject: Re: [RFC] Regulator state after regulator_get
 > 
 > On Thu, Apr 28, 2011 at 11:08:08AM +0000, kalle.jokiniemi@xxxxxxxxx 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/