linux-kernel - Add "regulator: arizona-ldo1: Use correct device to get enable GPIO" to 4.18 stable tree

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:   Mon, 20 Aug 2018 12:16:17 +0200
From:   Matthias Reichl <hias@...us.com>
To:     stable@...r.kernel.org
Cc:     Charles Keepax <ckeepax@...nsource.cirrus.com>,
        Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Add "regulator: arizona-ldo1: Use correct device to get enable GPIO"
 to 4.18 stable tree

It seems the arizona-ldo1 ldoena fix hasn't made it into 4.18. It
was added to 4.19/mainline, though:

commit a9191579ba1086d91842199263e6fe6bb5eec1ba
Author: Charles Keepax <ckeepax@...nsource.cirrus.com>
Date:   Tue Jun 19 16:10:00 2018 +0100

    regulator: arizona-ldo1: Use correct device to get enable GPIO

Could you please add this commit to the 4.18 stable queue?

Without this fix LDO control via GPIO is broken and Arizona devices
can't be used as no power is applied.

I tested locally with a WM5102 (Cirrus Logic Audio Card on RPi),
with stock 4.18 tree device detection fails:

[    6.075981] arizona spi0.1: Unknown device ID: 0

with this commit added to 4.18 the WM5102 is detected fine:

[    6.060887] arizona spi0.1: WM5102 revision C

so long & thanks,

Hias