mtd: rawnand: handle differently chip/controller errors about timings

Usually, the source of the error when setting/getting features does not
matter (if the controller does not support sending the command or if
the chip does not support the operation).

When it comes to timings, if the controller fails it is an error while
if the chip does not support the operation, it can be silently supposed
that it already works with the maximum supported timings.

Introduce some logic in nand_setup_data_interface() to handle that
difference.

Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>

diff --git a/drivers/mtd/nand/raw/nand_base.c b/drivers/mtd/nand/raw/nand_base.c
index d344dcb1262023ecb5686daf013b6bd9195e1e5f..2109fc223ff2dda2b966db02dcd8af4279f522b9 100644 (file)
--- a/drivers/mtd/nand/raw/nand_base.c
+++ b/drivers/mtd/nand/raw/nand_base.c
@@ -1272,11 +1272,13 @@ static int nand_setup_data_interface(struct nand_chip *chip, int chipnr)
        if (!chip->setup_data_interface)
                return 0;
 
-       /* Change the mode on the chip side */
-       ret = nand_set_features(chip, ONFI_FEATURE_ADDR_TIMING_MODE,
-                               tmode_param);
-       if (ret)
-               return ret;
+       /* Change the mode on the chip side (if supported by the NAND chip) */
+       if (nand_supports_set_get_features(chip)) {
+               ret = nand_set_features(chip, ONFI_FEATURE_ADDR_TIMING_MODE,
+                                       tmode_param);
+               if (ret)
+                       return ret;
+       }
 
        /* Change the mode on the controller side */
        return chip->setup_data_interface(mtd, chipnr, &chip->data_interface);