From: Miquel Raynal <miquel.raynal@bootlin.com>
To: William Zhang <william.zhang@broadcom.com>
Cc: Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
Linux MTD List <linux-mtd@lists.infradead.org>,
f.fainelli@gmail.com, rafal@milecki.pl, kursad.oney@broadcom.com,
joel.peshkin@broadcom.com, computersforpeace@gmail.com,
anand.gore@broadcom.com, dregan@mail.com,
kamal.dasu@broadcom.com, tomer.yacoby@broadcom.com,
dan.beygelman@broadcom.com,
Florian Fainelli <florian.fainelli@broadcom.com>,
linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>,
Richard Weinberger <richard@nod.at>,
Boris Brezillon <bbrezillon@kernel.org>,
Kamal Dasu <kdasu.kdev@gmail.com>
Subject: Re: [PATCH v3 2/5] mtd: rawnand: brcmnand: Fix potential false time out warning
Date: Tue, 4 Jul 2023 17:21:41 +0200 [thread overview]
Message-ID: <20230704172141.1369c9e8@xps-13> (raw)
In-Reply-To: <20230627193738.19596-3-william.zhang@broadcom.com>
Hi William,
william.zhang@broadcom.com wrote on Tue, 27 Jun 2023 12:37:35 -0700:
> If system is busy during the command status polling function, the driver
> may not get the chance to poll the status register till the end of time
> out and return the premature status. Do a final check after time out
> happens to ensure reading the correct status.
>
> Fixes: 9d2ee0a60b8b ("mtd: nand: brcmnand: Check flash #WP pin status before nand erase/program")
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: stable here and in patch 1 as well.
> ---
>
> Changes in v3: None
> Changes in v2: None
>
> drivers/mtd/nand/raw/brcmnand/brcmnand.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/mtd/nand/raw/brcmnand/brcmnand.c b/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> index 69709419516a..37c2c7cfa00e 100644
> --- a/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> +++ b/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> @@ -1080,6 +1080,14 @@ static int bcmnand_ctrl_poll_status(struct brcmnand_controller *ctrl,
> cpu_relax();
> } while (time_after(limit, jiffies));
>
> + /*
> + * do a final check after time out in case CPU is busy and driver does
> + * not get the enough time to poll to avoid false alarm
Do a final... ...the CPU was busy and the driver did not get enough
time to perform the polling to avoid false alarms.
> + */
> + val = brcmnand_read_reg(ctrl, BRCMNAND_INTFC_STATUS);
> + if ((val & mask) == expected_val)
> + return 0;
> +
> dev_warn(ctrl->dev, "timeout on status poll (expected %x got %x)\n",
> expected_val, val & mask);
>
Otherwise looks good.
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: William Zhang <william.zhang@broadcom.com>
Cc: Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
Linux MTD List <linux-mtd@lists.infradead.org>,
f.fainelli@gmail.com, rafal@milecki.pl, kursad.oney@broadcom.com,
joel.peshkin@broadcom.com, computersforpeace@gmail.com,
anand.gore@broadcom.com, dregan@mail.com,
kamal.dasu@broadcom.com, tomer.yacoby@broadcom.com,
dan.beygelman@broadcom.com,
Florian Fainelli <florian.fainelli@broadcom.com>,
linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>,
Richard Weinberger <richard@nod.at>,
Boris Brezillon <bbrezillon@kernel.org>,
Kamal Dasu <kdasu.kdev@gmail.com>
Subject: Re: [PATCH v3 2/5] mtd: rawnand: brcmnand: Fix potential false time out warning
Date: Tue, 4 Jul 2023 17:21:41 +0200 [thread overview]
Message-ID: <20230704172141.1369c9e8@xps-13> (raw)
In-Reply-To: <20230627193738.19596-3-william.zhang@broadcom.com>
Hi William,
william.zhang@broadcom.com wrote on Tue, 27 Jun 2023 12:37:35 -0700:
> If system is busy during the command status polling function, the driver
> may not get the chance to poll the status register till the end of time
> out and return the premature status. Do a final check after time out
> happens to ensure reading the correct status.
>
> Fixes: 9d2ee0a60b8b ("mtd: nand: brcmnand: Check flash #WP pin status before nand erase/program")
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: stable here and in patch 1 as well.
> ---
>
> Changes in v3: None
> Changes in v2: None
>
> drivers/mtd/nand/raw/brcmnand/brcmnand.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/mtd/nand/raw/brcmnand/brcmnand.c b/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> index 69709419516a..37c2c7cfa00e 100644
> --- a/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> +++ b/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> @@ -1080,6 +1080,14 @@ static int bcmnand_ctrl_poll_status(struct brcmnand_controller *ctrl,
> cpu_relax();
> } while (time_after(limit, jiffies));
>
> + /*
> + * do a final check after time out in case CPU is busy and driver does
> + * not get the enough time to poll to avoid false alarm
Do a final... ...the CPU was busy and the driver did not get enough
time to perform the polling to avoid false alarms.
> + */
> + val = brcmnand_read_reg(ctrl, BRCMNAND_INTFC_STATUS);
> + if ((val & mask) == expected_val)
> + return 0;
> +
> dev_warn(ctrl->dev, "timeout on status poll (expected %x got %x)\n",
> expected_val, val & mask);
>
Otherwise looks good.
Thanks,
Miquèl
next prev parent reply other threads:[~2023-07-04 15:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 19:37 [PATCH v3 0/5] mtd: rawnand: brcmnand: driver and doc updates William Zhang
2023-06-27 19:37 ` William Zhang
2023-06-27 19:37 ` [PATCH v3 1/5] mtd: rawnand: brcmnand: Fix ECC level field setting for v7.2 controller William Zhang
2023-06-27 19:37 ` William Zhang
2023-07-04 15:18 ` Miquel Raynal
2023-07-04 15:18 ` Miquel Raynal
2023-06-27 19:37 ` [PATCH v3 2/5] mtd: rawnand: brcmnand: Fix potential false time out warning William Zhang
2023-06-27 19:37 ` William Zhang
2023-07-04 15:21 ` Miquel Raynal [this message]
2023-07-04 15:21 ` Miquel Raynal
2023-06-27 19:37 ` [PATCH v3 3/5] mtd: rawnand: brcmnand: Fix crash during the panic_write William Zhang
2023-06-27 19:37 ` William Zhang
2023-07-04 15:23 ` Miquel Raynal
2023-07-04 15:23 ` Miquel Raynal
2023-07-04 15:26 ` Miquel Raynal
2023-07-04 15:26 ` Miquel Raynal
2023-07-05 0:40 ` William Zhang
2023-07-05 0:40 ` William Zhang
2023-07-05 7:09 ` Miquel Raynal
2023-07-05 7:09 ` Miquel Raynal
2023-06-27 19:37 ` [PATCH v3 4/5] mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write William Zhang
2023-06-27 19:37 ` William Zhang
2023-07-04 15:28 ` Miquel Raynal
2023-07-04 15:28 ` Miquel Raynal
2023-07-05 0:43 ` William Zhang
2023-07-05 0:43 ` William Zhang
2023-06-27 19:37 ` [PATCH v3 5/5] mtd: rawnand: brcmnand: Fix mtd oobsize William Zhang
2023-06-27 19:37 ` William Zhang
2023-07-04 15:30 ` Miquel Raynal
2023-07-04 15:30 ` Miquel Raynal
2023-07-05 0:50 ` William Zhang
2023-07-05 0:50 ` William Zhang
2023-07-05 7:11 ` Miquel Raynal
2023-07-05 7: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=20230704172141.1369c9e8@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=anand.gore@broadcom.com \
--cc=bbrezillon@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=dan.beygelman@broadcom.com \
--cc=dregan@mail.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=joel.peshkin@broadcom.com \
--cc=kamal.dasu@broadcom.com \
--cc=kdasu.kdev@gmail.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=richard@nod.at \
--cc=tomer.yacoby@broadcom.com \
--cc=vigneshr@ti.com \
--cc=william.zhang@broadcom.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.