From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Niravkumar L Rabara <niravkumarlaxmidas.rabara@altera.com>
Cc: richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: cadence: Add support for NV-DDR interface mode
Date: Fri, 24 Oct 2025 13:11:37 +0200 [thread overview]
Message-ID: <875xc4r1ue.fsf@bootlin.com> (raw)
In-Reply-To: <4a6577ff-7417-4d34-a683-2402736fd9d7@altera.com> (Niravkumar L. Rabara's message of "Fri, 24 Oct 2025 17:47:11 +0800")
>>> + if (dll_phy_gate_open_delay > NVDDR_GATE_CFG_MIN)
>>> + ie_start = NVDDR_GATE_CFG_MIN;
>> Can you double check here? I would expect < instead of > given that
>> you
>> compare with something you named "minimum". Maybe it is legitimate, just
>> warning.
>
> I have double checked, the logic is correct. May be I shouldn't use _MIN
> to avoid confusion.
> In v2 I will change NVDDR_GATE_CFG_MIN to NVDDR_GATE_CFG_STD.
Ok.
>>> + if (nand_interface_is_sdr(conf)) {
>>> + const struct nand_sdr_timings *sdr = nand_get_sdr_timings(conf);
>>> +
>>> + if (IS_ERR(sdr))
>>> + return PTR_ERR(sdr);
>>> +
>>> + ret = cadence_nand_setup_sdr_interface(chip, sdr);
>>> + } else if (chipnr >= 0) {
>> This isn't very clear. Please make it a separate condition if you
>> think
>> you must handle this case. Otherwise you're mixing it with the SDR
>> vs. NVDDR choice, and that's misleading.
> Noted.
> I will make a separate condition check as below in v2.
>
> - } else if (chipnr >= 0) {
> - const struct nand_nvddr_timings *nvddr =
> nand_get_nvddr_timings(conf);
> + } else {
> + if (chipnr < 0)
> + return ret;
Why do you check chipnr only for the NVDDR interface? I don't think it
makes sense. chipnr should probably be checked before the whole if()
block.
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Niravkumar L Rabara <niravkumarlaxmidas.rabara@altera.com>
Cc: richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: cadence: Add support for NV-DDR interface mode
Date: Fri, 24 Oct 2025 13:11:37 +0200 [thread overview]
Message-ID: <875xc4r1ue.fsf@bootlin.com> (raw)
In-Reply-To: <4a6577ff-7417-4d34-a683-2402736fd9d7@altera.com> (Niravkumar L. Rabara's message of "Fri, 24 Oct 2025 17:47:11 +0800")
>>> + if (dll_phy_gate_open_delay > NVDDR_GATE_CFG_MIN)
>>> + ie_start = NVDDR_GATE_CFG_MIN;
>> Can you double check here? I would expect < instead of > given that
>> you
>> compare with something you named "minimum". Maybe it is legitimate, just
>> warning.
>
> I have double checked, the logic is correct. May be I shouldn't use _MIN
> to avoid confusion.
> In v2 I will change NVDDR_GATE_CFG_MIN to NVDDR_GATE_CFG_STD.
Ok.
>>> + if (nand_interface_is_sdr(conf)) {
>>> + const struct nand_sdr_timings *sdr = nand_get_sdr_timings(conf);
>>> +
>>> + if (IS_ERR(sdr))
>>> + return PTR_ERR(sdr);
>>> +
>>> + ret = cadence_nand_setup_sdr_interface(chip, sdr);
>>> + } else if (chipnr >= 0) {
>> This isn't very clear. Please make it a separate condition if you
>> think
>> you must handle this case. Otherwise you're mixing it with the SDR
>> vs. NVDDR choice, and that's misleading.
> Noted.
> I will make a separate condition check as below in v2.
>
> - } else if (chipnr >= 0) {
> - const struct nand_nvddr_timings *nvddr =
> nand_get_nvddr_timings(conf);
> + } else {
> + if (chipnr < 0)
> + return ret;
Why do you check chipnr only for the NVDDR interface? I don't think it
makes sense. chipnr should probably be checked before the whole if()
block.
Miquèl
next prev parent reply other threads:[~2025-10-24 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 7:13 [PATCH] mtd: rawnand: cadence: Add support for NV-DDR interface mode niravkumarlaxmidas.rabara
2025-10-24 7:13 ` niravkumarlaxmidas.rabara
2025-10-24 7:38 ` Miquel Raynal
2025-10-24 7:38 ` Miquel Raynal
2025-10-24 9:47 ` Niravkumar L Rabara
2025-10-24 9:47 ` Niravkumar L Rabara
2025-10-24 11:11 ` Miquel Raynal [this message]
2025-10-24 11:11 ` Miquel Raynal
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=875xc4r1ue.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=niravkumarlaxmidas.rabara@altera.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.