linux-kernel - Re: [PATCH 0/3] regulator: fan53555: tcs4525 fix and cleanup

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: <eb23c9e400afa67739096fadd95345e951360bd7.camel@collabora.com>
Date:   Thu, 13 May 2021 14:23:19 -0300
From:   Ezequiel Garcia <ezequiel@...labora.com>
To:     Mark Brown <broonie@...nel.org>, Peter Geis <pgwipeout@...il.com>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] regulator: fan53555: tcs4525 fix and cleanup

Hi Peter,

On Wed, 2021-05-12 at 18:04 +0100, Mark Brown wrote:
> On Tue, 11 May 2021 17:13:32 -0400, Peter Geis wrote:
> > The tcs4525 voltage calculation is incorrect, which leads to a deadlock
> > on the rk3566-quartz64 board when loading cpufreq.
> > Fix the voltage calculation to correct the deadlock.
> > While we are at it, add a safety check and clean up the function names
> > to be more accurate.
> > 
> > Peter Geis (3):
> >   regulator: fan53555: fix TCS4525 voltage calulation
> >   regulator: fan53555: only bind tcs4525 to correct chip id
> >   regulator: fan53555: fix tcs4525 function names
> > 
> > [...]
> 
> Applied to
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
> 
> Thanks!
> 
> [1/3] regulator: fan53555: fix TCS4525 voltage calulation
>       commit: f8c8871f5eff3981eeb13421aca2c1cfda4a5204
> [2/3] regulator: fan53555: only bind tcs4525 to correct chip id
>       commit: f9028dcdf589f4ab528372088623aa4e8d324df2
> [3/3] regulator: fan53555: fix tcs4525 function names
>       commit: b3cc8ec04f50d9c860534fe4e3617a8d10ed9ea9
> 

I know this is already applied, but since I tested it,
this indeed fixes cpufreq for me:

Tested-by: Ezequiel Garcia <ezequiel@...labora.com>

Thanks a lot for taking care of it!