linux-kernel - RFC power domain vs generic supply 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-next>] [day] [month] [year] [list]

Message-ID: <CAOf5uwnZvJWhwf=h8nx=MmZz4BOyaq_BTr8vyDcGHqnBO7jK1Q@mail.gmail.com>
Date:   Tue, 8 Jun 2021 08:01:20 +0200
From:   Michael Nazzareno Trimarchi <michael@...rulasolutions.com>
To:     LKML <linux-kernel@...r.kernel.org>,
        Mark Brown <broonie@...nel.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: RFC power domain vs generic supply regulator

Hi all

I'm trying to understand how to deal with devices that do not provide
a supply handle connection using the device tree, or if there is a
generic way
to connect to a regulator. The pinctrl has a generic binding inside
dd.c that allow to mux pinout during probing or it allows to define a
power domain,
According to the code I read the power domain can be only connected to
the SoC power domain but in general a generic power domain can be
connected
to any source aka a regulator. For example and spi-nor can be powered
but a gpio regulator or any kind of supply connection and bunch of
devices
can just need a supply if they are probed or binded runtime. Can
someone give me feedback on this topic?

Michael