linux-kernel - Re: About [PATCH 1/2] regulator: core: Provide a dummy regulator with full constraints

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 12 Oct 2013 13:14:12 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Wei Ni <wni@...dia.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: About [PATCH 1/2] regulator: core: Provide a dummy regulator
 with full constraints

On Tue, Oct 08, 2013 at 05:46:49PM +0800, Wei Ni wrote:

> In the regulator_dev_lookup(), it will try to read the "xx-supply" to
> get the regnode, but I didn't set the vcc-supply in dts file for lm90,
> so the of_get_regulator() will return NULL, then the
> regulator_dev_lookup() will set the ret to -ENODEV, and return the rdev
> as NULL.

OK, I think the device tree board code just needs to set full
constraints during machine initialisation.  We can't have multiple
initcalls in the regulator code and doing it there is really a bit of a
workaround anyway.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)