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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Apr 2011 12:14:48 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	kalle.jokiniemi@...ia.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

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.
--
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/