linux-kernel - RE: [RFC] Regulator state after regulator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9D0D31AA57AAF5499AFDC63D6472631B09C8CE@008-AM1MPN1-036.mgdnok.nokia.com>
Date:	Thu, 28 Apr 2011 11:58:26 +0000
From:	<kalle.jokiniemi@...ia.com>
To:	<broonie@...nsource.wolfsonmicro.com>
CC:	<lrg@...mlogic.co.uk>, <mchehab@...radead.org>,
	<svarbatov@...sol.com>, <saaguirre@...com>,
	<grosikopulos@...sol.com>, <vimarsh.zutshi@...ia.com>,
	<Sakari.Ailus@...ia.com>, <linux-kernel@...r.kernel.org>,
	<linux-media@...r.kernel.org>
Subject: RE: [RFC] Regulator state after regulator_get



 > -----Original Message-----
 > From: ext Mark Brown [mailto:broonie@...nsource.wolfsonmicro.com]
 > Sent: 28. huhtikuuta 2011 14:15
 > To: Jokiniemi Kalle (Nokia-SD/Tampere)
 > Cc: lrg@...mlogic.co.uk; mchehab@...radead.org; svarbatov@...sol.com;
 > saaguirre@...com; grosikopulos@...sol.com; Zutshi Vimarsh (Nokia-
 > SD/Helsinki); Ailus Sakari (Nokia-SD/Helsinki); linux-kernel@...r.kernel.org;
 > linux-media@...r.kernel.org
 > Subject: Re: [RFC] Regulator state after regulator_get
 > 
 > On Thu, Apr 28, 2011 at 11:08:08AM +0000, kalle.jokiniemi@...ia.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
--
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/