linux-kernel - Re: [PATCH v4 04/10] memory: ti-aemif: Create aemif_check_cs

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: <8734jsmfqe.fsf@bootlin.com>
Date: Fri, 15 Nov 2024 20:58:17 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Bastien Curutchet <bastien.curutchet@...tlin.com>
Cc: Santosh Shilimkar <ssantosh@...nel.org>,  Krzysztof Kozlowski
 <krzk@...nel.org>,  Richard Weinberger <richard@....at>,  Vignesh
 Raghavendra <vigneshr@...com>,  linux-kernel@...r.kernel.org,
  linux-mtd@...ts.infradead.org,  Thomas Petazzoni
 <thomas.petazzoni@...tlin.com>,  Herve Codina <herve.codina@...tlin.com>,
  Christopher Cordahi <christophercordahi@...ometrics.ca>
Subject: Re: [PATCH v4 04/10] memory: ti-aemif: Create aemif_check_cs_timings()

On 15/11/2024 at 14:26:25 +01, Bastien Curutchet <bastien.curutchet@...tlin.com> wrote:

> aemif_calc_rate() check the validity of a new computed timing against a

                    checks

> 'max' value given as input. This isn't convenient if we want to check
> the CS timing configuration somewhere else in the code.
>
> Wrap the verification of all the chip select's timing configuration into a
> single function to ease its exportation in upcoming patches.
> Remove the 'max' input from aemif_calc_rate() as it's no longer used.
>
> Signed-off-by: Bastien Curutchet <bastien.curutchet@...tlin.com>

Reviewed-by: Miquel Raynal <miquel.raynal@...tlin.com>