From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Christophe Kerello <christophe.kerello@st.com>
Cc: <richard@nod.at>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>, <marek.vasut@gmail.com>,
<vigneshr@ti.com>, <bbrezillon@kernel.org>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Amelie Delaunay <amelie.delaunay@st.com>
Subject: Re: [PATCH] mtd: rawnand: stm32_fmc2: increase DMA completion timeouts
Date: Thu, 27 Jun 2019 18:59:01 +0200 [thread overview]
Message-ID: <20190627185901.6247a77c@xps13> (raw)
In-Reply-To: <1561128480-14531-1-git-send-email-christophe.kerello@st.com>
Hi Christophe,
Christophe Kerello <christophe.kerello@st.com> wrote on Fri, 21 Jun
2019 16:48:00 +0200:
> When the system is overloaded, DMA data transfer completion occurs after
> 100ms. Increase the timeouts to let it the time to complete.
>
> Signed-off-by: Amelie Delaunay <amelie.delaunay@st.com>
The first SoB should be the author's. Either Amelie is the author and
you should use 'git commit --amend --author=..." or she is not and
should be dropped (unless she sends the patch which is yours, and in
this case her name should appear second).
> Signed-off-by: Christophe Kerello <christophe.kerello@st.com>
> ---
> drivers/mtd/nand/raw/stm32_fmc2_nand.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/nand/raw/stm32_fmc2_nand.c b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> index 4aabea2..c7f7c6f 100644
> --- a/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> +++ b/drivers/mtd/nand/raw/stm32_fmc2_nand.c
> @@ -981,7 +981,7 @@ static int stm32_fmc2_xfer(struct nand_chip *chip, const u8 *buf,
>
> /* Wait DMA data transfer completion */
> if (!wait_for_completion_timeout(&fmc2->dma_data_complete,
> - msecs_to_jiffies(100))) {
> + msecs_to_jiffies(500))) {
> dev_err(fmc2->dev, "data DMA timeout\n");
> dmaengine_terminate_all(dma_ch);
> ret = -ETIMEDOUT;
> @@ -990,7 +990,7 @@ static int stm32_fmc2_xfer(struct nand_chip *chip, const u8 *buf,
> /* Wait DMA ECC transfer completion */
> if (!write_data && !raw) {
> if (!wait_for_completion_timeout(&fmc2->dma_ecc_complete,
> - msecs_to_jiffies(100))) {
> + msecs_to_jiffies(500))) {
IIRC I already asked you this but could you please make a define and at
the same time make it 1000 ms, I don't see the point in being close
to the maximum latency. If this is reached, your transfer was
screwed already, there is no performance impact here.
Sorry for the late notice but I will close the nand/next branch
tomorrow, so I'll queue your v2 only if I receive it soon enough :)
Thanks,
Miquèl
prev parent reply other threads:[~2019-06-27 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 14:48 [PATCH] mtd: rawnand: stm32_fmc2: increase DMA completion timeouts Christophe Kerello
2019-06-27 16:59 ` Miquel Raynal [this message]
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=20190627185901.6247a77c@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=amelie.delaunay@st.com \
--cc=bbrezillon@kernel.org \
--cc=christophe.kerello@st.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marek.vasut@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox