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]
Message-ID: <20170613204239.ans4j535st7kjee6@sirena.org.uk>
Date:   Tue, 13 Jun 2017 21:42:39 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Michał Mirosław <mirq-linux@...e.qmqm.pl>
Cc:     linux-kernel@...r.kernel.org, Tony Lindgren <tony@...mide.com>,
        Liam Girdwood <lgirdwood@...il.com>, j-keerthy@...com,
        linux-omap@...r.kernel.org
Subject: Re: [PATCH v2 2/2] regulator: tps65910: Allow supply references to
 the same chip

On Tue, Jun 13, 2017 at 10:22:17PM +0200, Michał Mirosław wrote:
> On Tue, Jun 13, 2017 at 06:46:28PM +0100, Mark Brown wrote:

> > at all.  Is this happening for you with current kernels, we have a few
> > mechanisms for deferring bindings of supplies which should help here.

> What mechanisms would that be? What I observed is that whenever
> a regulator's supply is not available but described in device-tree,
> the whole device's registration is deferred.

Mainly "Don't use regulators as supplies until the parent is bound",
there were some older ones IIRC.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ