linux-kernel - Re: [PATCH v3 2/2] mtd: rawnand: marvell: don't set the NAND frequency select

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: <20230526180215.924342-1-miquel.raynal@bootlin.com>
Date:   Fri, 26 May 2023 20:02:15 +0200
From:   Miquel Raynal <miquel.raynal@...tlin.com>
To:     Chris Packham <chris.packham@...iedtelesis.co.nz>,
        miquel.raynal@...tlin.com, richard@....at, vigneshr@...com,
        bbrezillon@...nel.org
Cc:     linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/2] mtd: rawnand: marvell: don't set the NAND frequency select

On Thu, 2023-05-25 at 00:31:53 UTC, Chris Packham wrote:
> marvell_nfc_setup_interface() uses the frequency retrieved from the
> clock associated with the nand interface to determine the timings that
> will be used. By changing the NAND frequency select without reflecting
> this in the clock configuration this means that the timings calculated
> don't correctly meet the requirements of the NAND chip. This hasn't been
> an issue up to now because of a different bug that was stopping the
> timings being updated after they were initially set.
> 
> Fixes: b25251414f6e ("mtd: rawnand: marvell: Stop implementing ->select_chip()")
> Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>

Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/fixes, thanks.

Miquel