From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.com,
linux-mtd@lists.infradead.org, john@phrozen.org
Subject: Re: [PATCH v2 4/8] MTD: xway: remove endless loop
Date: Sun, 19 Jun 2016 14:14:49 +0200 [thread overview]
Message-ID: <20160619141449.5fd34945@bbrezillon> (raw)
In-Reply-To: <1466277252-13867-5-git-send-email-hauke@hauke-m.de>
On Sat, 18 Jun 2016 21:14:08 +0200
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> From: John Crispin <john@phrozen.org>
>
> The reset loop logic could run into a endless loop. Lets fix it as
> requested.
> http://lists.infradead.org/pipermail/linux-mtd/2012-September/044240.html
>
> Signed-off-by: John Crispin <john@phrozen.org>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
> drivers/mtd/nand/xway_nand.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/nand/xway_nand.c b/drivers/mtd/nand/xway_nand.c
> index 346781a..61176c4 100644
> --- a/drivers/mtd/nand/xway_nand.c
> +++ b/drivers/mtd/nand/xway_nand.c
> @@ -73,16 +73,22 @@ struct xway_nand_data {
> static void xway_reset_chip(struct nand_chip *chip)
> {
> unsigned long nandaddr = (unsigned long) chip->IO_ADDR_W;
> + unsigned long timeout;
> unsigned long flags;
>
> nandaddr &= ~NAND_WRITE_ADDR;
> nandaddr |= NAND_WRITE_CMD;
>
> /* finish with a reset */
> + timeout = jiffies + msecs_to_jiffies(20);
> +
> spin_lock_irqsave(&ebu_lock, flags);
> writeb(NAND_WRITE_CMD_RESET, (void __iomem *) nandaddr);
> - while ((ltq_ebu_r32(EBU_NAND_WAIT) & NAND_WAIT_WR_C) == 0)
> - ;
> + do {
> + if ((ltq_ebu_r32(EBU_NAND_WAIT) & NAND_WAIT_WR_C) == 0)
> + break;
> + cond_resched();
> + } while (!time_after_eq(jiffies, timeout));
> spin_unlock_irqrestore(&ebu_lock, flags);
> }
>
AFAICS, this function is doing exactly what
->cmdfunc(NAND_CMD_RESET, -1 , -1) does, except for the NAND_WAIT_WR_C
test? What is this bit representing?
I'd really prefer if you kill this function and just call ->cmdfunc()
instead.
next prev parent reply other threads:[~2016-06-19 12:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 19:14 [PATCH v2 0/8] MTD: xway: fix driver Hauke Mehrtens
2016-06-18 19:14 ` [PATCH v2 1/8] MTD: xway: convert to normal platform driver Hauke Mehrtens
2016-06-19 11:32 ` Boris Brezillon
2016-06-19 11:58 ` Hauke Mehrtens
2016-06-18 19:14 ` [PATCH v2 2/8] MTD: xway: add some more documentation Hauke Mehrtens
2016-06-19 11:39 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 3/8] MTD: xway: the latched command should be persistent Hauke Mehrtens
2016-06-19 11:52 ` Boris Brezillon
2016-06-19 12:04 ` Hauke Mehrtens
2016-06-19 12:09 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 4/8] MTD: xway: remove endless loop Hauke Mehrtens
2016-06-19 12:14 ` Boris Brezillon [this message]
2016-06-19 12:32 ` Hauke Mehrtens
2016-06-19 12:57 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 5/8] MTD: xway: add missing write_buf and read_buf to nand driver Hauke Mehrtens
2016-06-19 12:38 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 6/8] MTD: xway: fix nand locking Hauke Mehrtens
2016-06-19 12:41 ` Boris Brezillon
2016-06-19 12:53 ` Richard Weinberger
2016-06-19 12:56 ` Hauke Mehrtens
2016-06-19 13:04 ` Boris Brezillon
2016-06-19 12:58 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 7/8] MTD: xway: extract read and write function Hauke Mehrtens
2016-06-19 12:42 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 8/8] MTD: xway: use global NAND_CMD_RESET define Hauke Mehrtens
2016-06-19 13:06 ` Boris Brezillon
2016-06-19 12:50 ` [PATCH v2 0/8] MTD: xway: fix driver Boris Brezillon
2016-06-19 13:13 ` Hauke Mehrtens
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=20160619141449.5fd34945@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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