From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Christophe Kerello <christophe.kerello@foss.st.com>
Cc: <richard@nod.at>, <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH] mtd: rawnand: stm32_fmc2: do not support EDO mode
Date: Mon, 27 Mar 2023 10:11:56 +0200 [thread overview]
Message-ID: <20230327101156.0ec2816a@xps-13> (raw)
In-Reply-To: <fcb600af-88dc-55a7-917e-4cf4673c2973@foss.st.com>
Hi Christophe,
christophe.kerello@foss.st.com wrote on Mon, 27 Mar 2023 10:02:13 +0200:
> Hello Miquel,
>
> On 3/24/23 17:34, Christophe Kerello wrote:
> > Hello Miquel,
> >
> > On 3/24/23 17:25, Miquel Raynal wrote:
> >> Hi Christophe,
> >>
> >> christophe.kerello@foss.st.com wrote on Fri, 24 Mar 2023 17:09:18 +0100:
> >>
> >>> FMC2 controller does not support EDO mode (timings mode 4 and 5).
> >>>
> >>> Signed-off-by: Christophe Kerello <christophe.kerello@foss.st.com>
> >>> Fixes: 2cd457f328c1 ("mtd: rawnand: stm32_fmc2: add STM32 FMC2 NAND >>> flash controller driver")
> >>> ---
> >>> drivers/mtd/nand/raw/stm32_fmc2_nand.c | 3 +++
> >>> 1 file changed, 3 insertions(+)
> >>>
> >>> diff --git a/drivers/mtd/nand/raw/stm32_fmc2_nand.c >>> b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> >>> index 5d627048c420..3abb63d00a0b 100644
> >>> --- a/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> >>> +++ b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> >>> @@ -1531,6 +1531,9 @@ static int >>> stm32_fmc2_nfc_setup_interface(struct nand_chip *chip, int chipnr,
> >>> if (IS_ERR(sdrt))
> >>> return PTR_ERR(sdrt);
> >>> + if (sdrt->tRC_min < 30000)
> >>
> >> When introducing NV-DDR support we as well added a timings.mode field,
> >> perhaps you could use it?
> >
> > Yes, I can use it. It will be done in V2.
> >
> > Regards,
> > Christophe Kerello.
> >
>
> I had a look at Kernel LTS, and timings.mode was introduced on Kernel LTS 5.10. As this patch has also to be applied on Kernel LTS 5.4, my proposal is to send a new patch set. The first patch will be the current patch (fix for all Kernel LTS) and the second patch will use timings.mode instead of checking tRC_min timings for next Kernel delivery. Is this proposal acceptable?
Works for me!
Thanks,
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: Christophe Kerello <christophe.kerello@foss.st.com>
Cc: <richard@nod.at>, <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH] mtd: rawnand: stm32_fmc2: do not support EDO mode
Date: Mon, 27 Mar 2023 10:11:56 +0200 [thread overview]
Message-ID: <20230327101156.0ec2816a@xps-13> (raw)
In-Reply-To: <fcb600af-88dc-55a7-917e-4cf4673c2973@foss.st.com>
Hi Christophe,
christophe.kerello@foss.st.com wrote on Mon, 27 Mar 2023 10:02:13 +0200:
> Hello Miquel,
>
> On 3/24/23 17:34, Christophe Kerello wrote:
> > Hello Miquel,
> >
> > On 3/24/23 17:25, Miquel Raynal wrote:
> >> Hi Christophe,
> >>
> >> christophe.kerello@foss.st.com wrote on Fri, 24 Mar 2023 17:09:18 +0100:
> >>
> >>> FMC2 controller does not support EDO mode (timings mode 4 and 5).
> >>>
> >>> Signed-off-by: Christophe Kerello <christophe.kerello@foss.st.com>
> >>> Fixes: 2cd457f328c1 ("mtd: rawnand: stm32_fmc2: add STM32 FMC2 NAND >>> flash controller driver")
> >>> ---
> >>> drivers/mtd/nand/raw/stm32_fmc2_nand.c | 3 +++
> >>> 1 file changed, 3 insertions(+)
> >>>
> >>> diff --git a/drivers/mtd/nand/raw/stm32_fmc2_nand.c >>> b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> >>> index 5d627048c420..3abb63d00a0b 100644
> >>> --- a/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> >>> +++ b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> >>> @@ -1531,6 +1531,9 @@ static int >>> stm32_fmc2_nfc_setup_interface(struct nand_chip *chip, int chipnr,
> >>> if (IS_ERR(sdrt))
> >>> return PTR_ERR(sdrt);
> >>> + if (sdrt->tRC_min < 30000)
> >>
> >> When introducing NV-DDR support we as well added a timings.mode field,
> >> perhaps you could use it?
> >
> > Yes, I can use it. It will be done in V2.
> >
> > Regards,
> > Christophe Kerello.
> >
>
> I had a look at Kernel LTS, and timings.mode was introduced on Kernel LTS 5.10. As this patch has also to be applied on Kernel LTS 5.4, my proposal is to send a new patch set. The first patch will be the current patch (fix for all Kernel LTS) and the second patch will use timings.mode instead of checking tRC_min timings for next Kernel delivery. Is this proposal acceptable?
Works for me!
Thanks,
Miquèl
next prev parent reply other threads:[~2023-03-27 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 16:09 [PATCH] mtd: rawnand: stm32_fmc2: do not support EDO mode Christophe Kerello
2023-03-24 16:09 ` Christophe Kerello
2023-03-24 16:25 ` Miquel Raynal
2023-03-24 16:25 ` Miquel Raynal
2023-03-24 16:34 ` Christophe Kerello
2023-03-24 16:34 ` Christophe Kerello
2023-03-27 8:02 ` Christophe Kerello
2023-03-27 8:02 ` Christophe Kerello
2023-03-27 8:11 ` Miquel Raynal [this message]
2023-03-27 8: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=20230327101156.0ec2816a@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=christophe.kerello@foss.st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.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.