From: Miquel Raynal <miquel.raynal@bootlin.com>
To: kory.maincent@bootlin.com
Cc: u-boot@lists.denx.de, thomas.petazzoni@bootlin.com,
"Patrice Chotard" <patrice.chotard@foss.st.com>,
"Wolfgang Denk" <wd@denx.de>, "Pali Rohár" <pali@kernel.org>,
"Simon Glass" <sjg@chromium.org>,
"Marek Behún" <marek.behun@nic.cz>
Subject: Re: [PATCH v2] mtd: rawnand: Add support to dedicated function to set timings
Date: Fri, 24 Jun 2022 20:09:55 +0200 [thread overview]
Message-ID: <20220624200955.7ca7bdcf@xps-13> (raw)
In-Reply-To: <20220622091145.1207923-1-kory.maincent@bootlin.com>
Hi Köry,
kory.maincent@bootlin.com wrote on Wed, 22 Jun 2022 11:11:45 +0200:
> From: Kory Maincent <kory.maincent@bootlin.com>
>
> With the current code if the board has an ONFI compliant NAND without
> support to the get and set features, U-boot returns an ENOTSUP error when
> trying to tune the timings which prevents the probe of the device.
> Indeed onfi_set_features() return ENOTSUP error if set/get features is not
> supported. In the case of timings we should not return ENOTSUP because we
> can use the default timings. The NAND is already capable of listening at
> its highest supported rate, so we assume in this case that it is fine to
> skip the operation.
>
> Fix it by adding an intermediate nand_onfi_set_timings() function which
> does not error out if set/get feature is not supported.
>
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
Seems legitimate.
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
>
> Change since v1:
> - Update commit message
>
> drivers/mtd/nand/raw/nand_base.c | 30 +++++++++++++++++++-----------
> 1 file changed, 19 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/mtd/nand/raw/nand_base.c b/drivers/mtd/nand/raw/nand_base.c
> index 6f81257cf1..e8ece0a4a0 100644
> --- a/drivers/mtd/nand/raw/nand_base.c
> +++ b/drivers/mtd/nand/raw/nand_base.c
> @@ -974,6 +974,22 @@ static int nand_reset_data_interface(struct nand_chip *chip, int chipnr)
> return ret;
> }
>
> +static int nand_onfi_set_timings(struct mtd_info *mtd, struct nand_chip *chip)
> +{
> + if (!chip->onfi_version ||
> + !(le16_to_cpu(chip->onfi_params.opt_cmd)
> + & ONFI_OPT_CMD_SET_GET_FEATURES))
> + return 0;
> +
> + u8 tmode_param[ONFI_SUBFEATURE_PARAM_LEN] = {
> + chip->onfi_timing_mode_default,
> + };
> +
> + return chip->onfi_set_features(mtd, chip,
> + ONFI_FEATURE_ADDR_TIMING_MODE,
> + tmode_param);
> +}
> +
> /**
> * nand_setup_data_interface - Setup the best data interface and timings
> * @chip: The NAND chip
> @@ -999,17 +1015,9 @@ static int nand_setup_data_interface(struct nand_chip *chip, int chipnr)
> * Ensure the timing mode has been changed on the chip side
> * before changing timings on the controller side.
> */
> - if (chip->onfi_version) {
> - u8 tmode_param[ONFI_SUBFEATURE_PARAM_LEN] = {
> - chip->onfi_timing_mode_default,
> - };
> -
> - ret = chip->onfi_set_features(mtd, chip,
> - ONFI_FEATURE_ADDR_TIMING_MODE,
> - tmode_param);
> - if (ret)
> - goto err;
> - }
> + ret = nand_onfi_set_timings(mtd, chip);
> + if (ret)
> + goto err;
>
> ret = chip->setup_data_interface(mtd, chipnr, chip->data_interface);
> err:
Thanks,
Miquèl
next prev parent reply other threads:[~2022-06-24 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 9:11 [PATCH v2] mtd: rawnand: Add support to dedicated function to set timings kory.maincent
2022-06-24 18:09 ` Miquel Raynal [this message]
2022-07-08 16:39 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220624200955.7ca7bdcf@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=kory.maincent@bootlin.com \
--cc=marek.behun@nic.cz \
--cc=pali@kernel.org \
--cc=patrice.chotard@foss.st.com \
--cc=sjg@chromium.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=u-boot@lists.denx.de \
--cc=wd@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox