linux-kernel - Re: [PATCH v2 03/11] regulator: dt-bindings: mt6358: Convert to DT 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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 23 Aug 2023 07:48:13 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Chen-Yu Tsai <wenst@...omium.org>
Cc:     Lee Jones <lee@...nel.org>, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Matthias Brugger <matthias.bgg@...il.com>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>,
        Mark Brown <broonie@...nel.org>,
        Zhiyong Tao <zhiyong.tao@...iatek.com>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org,
        linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v2 03/11] regulator: dt-bindings: mt6358: Convert to DT
 schema

On 23/08/2023 05:54, Chen-Yu Tsai wrote:
>>> +
>>> +    regulator {
>>> +        compatible = "mediatek,mt6358-regulator";
>>> +
>>> +        buck_vgpu {
>>> +            regulator-name = "vgpu";
>>> +            regulator-min-microvolt = <625000>;
>>> +            regulator-max-microvolt = <900000>;
>>> +            regulator-ramp-delay = <6250>;
>>> +            regulator-enable-ramp-delay = <200>;
>>> +            regulator-allowed-modes = <MT6397_BUCK_MODE_AUTO
>>
>> mt6397?
>>
>> Both cases look a bit confusing.
> 
> There's only two regulator binding header files, mt6397 and mt6360.
> They seem to correspond to the two classes of PMICs that MediaTek has.
> I believe the two header files and thus the macros are meant to be
> shared?

Defines have specific model name, so they do not look like meant to be
shared. If all the values of the binding match, they can be shared, but
then this should be mentioned in the binding plus it should be used in
the driver. I don't see your driver patches add include of this header.

> 
> MT6397 and co refer to their AP PMICs, i.e. PMICs that are companion
> chips to the SoC and provide most of the power rails a system needs,
> along with things like RTC, audio codecs, etc.. The MT6358 and MT6366
> belong to this class.
> 
> MT6360 and possibly others refer to their charger PMICs, which integrate
> a battery charger, USB type-C PD stuff, LED drivers, and a handful of
> regulators.


Best regards,
Krzysztof