linux-kernel - Re: [PATCH] dt-bindings: regulators: Document Tegra regulator coupling in json-schema

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]

Date:   Tue, 7 Dec 2021 18:49:07 +0300
From:   Dmitry Osipenko <digetx@...il.com>
To:     Rob Herring <robh@...nel.org>
Cc:     Thierry Reding <thierry.reding@...il.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>, devicetree@...r.kernel.org,
        linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: regulators: Document Tegra regulator
 coupling in json-schema

07.12.2021 18:25, Rob Herring пишет:
> On Mon, Dec 6, 2021 at 3:55 PM Dmitry Osipenko <digetx@...il.com> wrote:
>>
>> 06.12.2021 23:40, Rob Herring пишет:
>>> On Mon, Dec 06, 2021 at 04:40:32PM +0100, Thierry Reding wrote:
>>>> From: Thierry Reding <treding@...dia.com>
>>>>
>>>> Move the NVIDIA Tegra regulator coupling bindings from the free-form
>>>> text format into the existing json-schema file for regulators.
>>>
>>> Do we need these properties for every single regulator? This should be
>>> its own schema file and then referenced where it is needed.
>>
>> These properties are SoC-specific, they describe how regulators are
>> integrated into SoC's power subsystem. Regulators themselves are
>> SoC-independent, i.e. PMIC's vendor and model don't matter for SoC.
> 
> Yes, but in reality the PMIC and SoC are typically somewhat coupled.
> How many PMICs do you need these properties for?

Three PMICs. Realistically we shouldn't have more such PMICs in upstream
in foreseeable future.