linux-kernel - Re: [PATCH v2 3/5] dt-bindings: regulator: Add binding schema for mt6357 regulators

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: <Y0VHGh/GavvuZY2A@sirena.org.uk>
Date:   Tue, 11 Oct 2022 11:36:10 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Alexandre Mergnat <amergnat@...libre.com>
Cc:     krzysztof.kozlowski@...aro.org, chen.zhong@...iatek.com,
        devicetree@...r.kernel.org, dmitry.torokhov@...il.com,
        fparent@...libre.com, krzysztof.kozlowski+dt@...aro.org,
        lee@...nel.org, lgirdwood@...il.com,
        linux-arm-kernel@...ts.infradead.org, linux-input@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
        matthias.bgg@...il.com, robh+dt@...nel.org, robh@...nel.org
Subject: Re: [PATCH v2 3/5] dt-bindings: regulator: Add binding schema for
 mt6357 regulators

On Tue, Oct 11, 2022 at 11:30:58AM +0200, Alexandre Mergnat wrote:

> > Why enforcing particular name of the regulator?

> The regulator names are forced to match with the datasheet names.

> I think it's a good practice to increase visibility between HW & SW.

> Also, that keep consistency with other Mediatek PMIC schema.

No, this is bad practice which completely misses the point of what the
names are for and the other Mediatek drivers are broken.

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