Message ID | 20200529111322.7184-8-miquel.raynal@bootlin.com |
---|---|
State | Accepted |
Headers | show |
Series | Allow vendor drivers to propose their own timings | expand |
On Fri, 2020-05-29 at 11:13:01 UTC, Miquel Raynal wrote: > Avoid relying just on the default timing mode to discriminate if the > data interface must be restored. This field should only be used > at initialization time by legacy chips statically defined. Do a > memcmp() instead. > > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> > Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com> Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git nand/next. Miquel
diff --git a/drivers/mtd/nand/raw/nand_base.c b/drivers/mtd/nand/raw/nand_base.c index 534ee75d0f2b..3526c2a50bbe 100644 --- a/drivers/mtd/nand/raw/nand_base.c +++ b/drivers/mtd/nand/raw/nand_base.c @@ -2512,7 +2512,8 @@ int nand_reset(struct nand_chip *chip, int chipnr) * nand_setup_data_interface() uses ->set/get_features() which would * fail anyway as the parameter page is not available yet. */ - if (!chip->onfi_timing_mode_default) + if (!memcmp(&chip->data_interface, &saved_data_intf, + sizeof(saved_data_intf))) return 0; chip->data_interface = saved_data_intf;