linux-kernel - Re: [PATCH v2 8/9] regulator/rpi-panel-attiny: Don't read the LCD power status

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: <Ye8P7PmOzy6tCnpi@sirena.org.uk>
Date:   Mon, 24 Jan 2022 20:45:32 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Detlev Casanova <detlev.casanova@...labora.com>
Cc:     linux-kernel@...r.kernel.org,
        Dave Stevenson <dave.stevenson@...pberrypi.com>,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH v2 8/9] regulator/rpi-panel-attiny: Don't read the LCD
 power status

On Mon, Jan 24, 2022 at 03:22:35PM -0500, Detlev Casanova wrote:
> On Friday, January 21, 2022 11:30:39 A.M. EST Mark Brown wrote:

> > If that's the case since you're using regmap would it not make sense to
> > enable caching in order to minimise reads in general.

> Would caching avoid all reads if the values are written at least once before? 
> The idea here is to make sure they are never read, I'm not sure if the regmap 
> cache ensures no read in this situation.

All reads for which the value in the hardware is known, either from a
register default or from a previous write.

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