linux-kernel - Re: [PATCH] regulator: palmas: set supply

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: <20210630200840.GJ5106@sirena.org.uk>
Date:   Wed, 30 Jun 2021 21:08:40 +0100
From:   Mark Brown <broonie@...nel.org>
To:     "H. Nikolaus Schaller" <hns@...delico.com>
Cc:     Tony Lindgren <tony@...mide.com>,
        Graeme Gregory <gg@...mlogic.co.uk>,
        Liam Girdwood <lgirdwood@...il.com>,
        Nishanth Menon <nm@...com>,
        Linux-OMAP <linux-omap@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Discussions about the Letux Kernel 
        <letux-kernel@...nphoenux.org>, kernel@...a-handheld.com,
        Peter Ujfalusi <peter.ujfalusi@...il.com>
Subject: Re: [PATCH] regulator: palmas: set supply_name after registering the
 regulator

On Wed, Jun 30, 2021 at 07:17:28PM +0200, H. Nikolaus Schaller wrote:

> Splitting into many regulators also needs to touch the device trees
> to have individual compatible entries which currently do not exist.

No, it doesn't.  There's absolutely no need for any specific mapping
between Linux devices and compatible strings or nodes in the DT, we can
create any number of Linux devices for any number of compatibles - just
look at MFDs (where we create multiple Linux devices for a single DT
compatible string) or system devices (where we create Linux devices with
potentially no node in the device tree).

> On the other hand, a theoretical system could have a real fixed regulator
> in between (maybe a power switch?) and should still work. Why should 
> driver core care about that case and not the core system it is using?

For deferred probe to be guaranteed to work we really should have one
regulator per Linux device but in practice that is overhead and effort
that almost never buys us anything in practical systems (I can't
emphasize strongly enough how unusual chains of more than two regulators
are) so we don't enforce doing that.

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