linux-kernel - Re: [PATCH v2] arm64: dts: rockchip: rk3399-nanopi4: Fix voltage regulator config

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: <C8ED2EFC-A7D5-418D-A7D9-E1D37B5BECFD@kohlschutter.com>
Date:   Mon, 18 Jul 2022 22:59:03 +0200
From:   Christian Kohlschütter 
        <christian@...lschutter.com>
To:     Robin Murphy <robin.murphy@....com>, wens@...nel.org,
        Heiko Stübner <heiko@...ech.de>,
        Markus Reichl <m.reichl@...etechno.de>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        "open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
        Linux MMC List <linux-mmc@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v2] arm64: dts: rockchip: rk3399-nanopi4: Fix voltage
 regulator config

Am 18.07.2022 um 14:02 schrieb Christian Kohlschütter <christian@...lschutter.com>:
>> 
>> A series of issues exist around the "vcc3v0_sd" voltage regulator that
>> made it necessary to mark it "always-on".
>> 
>> With the patch "regulator: core: Resolve supply name earlier to prevent
>> double-init", this option is no longer necessary.
>> ...
> 
> Walking back on my claim in the commit message that no further patches are needed for the u-boot integration to work.
> Other than that, the actual patch is unchanged.

This change (removing regulator-always-on) doesn't work reliably; please disregard for now.