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: <20170613174628.sv4v76s7torrn5jx@sirena.org.uk>
Date:   Tue, 13 Jun 2017 18:46:28 +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 04:41:58PM +0200, Michał Mirosław wrote:

> This allows for (acyclic) references from tps6591x supplies to
> its outputs.

This is clearly not something that should be open coded in individual
drivers, aside from the code duplication it is obviously possible to
have two different chips supplying each other which this wouldn't help
at all.  Is this happening for you with current kernels, we have a few
mechanisms for deferring bindings of supplies which should help here.

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