mtd: rawnand: marvell: don't set the NAND frequency select
authorChris Packham <chris.packham@alliedtelesis.co.nz>
Thu, 25 May 2023 00:31:53 +0000 (12:31 +1200)
committerMiquel Raynal <miquel.raynal@bootlin.com>
Thu, 1 Jun 2023 16:12:33 +0000 (18:12 +0200)
commitc4d28e30a8d0b979e4029465ab8f312ab6ce2644
tree36b8616084f0133723cf6ae9dc397688bb5c12f9
parent8a6f4d346f3bad9c68b4a87701eb3f7978542d57
mtd: rawnand: marvell: don't set the NAND frequency select

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@alliedtelesis.co.nz>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20230525003154.2303012-2-chris.packham@alliedtelesis.co.nz
drivers/mtd/nand/raw/marvell_nand.c