From: <Tudor.Ambarus@microchip.com>
To: <chaochao2021666@163.com>, <u-boot@lists.denx.de>,
<trini@konsulko.com>, <jan.kiszka@siemens.com>
Cc: <jagan@amarulasolutions.com>, <vigneshr@ti.com>, <chao.zeng@siemens.com>
Subject: Re: [PATCH] sf: Querying write-protect status before operating the flash
Date: Fri, 5 Nov 2021 17:17:34 +0000 [thread overview]
Message-ID: <11982722-ce48-9d67-c68d-ad25146aeb2e@microchip.com> (raw)
In-Reply-To: <20210622052126.49853-1-chaochao2021666@163.com>
Hi,
On 6/22/21 8:21 AM, chao zeng wrote:
> From: Chao Zeng <chao.zeng@siemens.com>
>
> When operating the write-protection flash,spi_flash_std_write() and
> spi_flash_std_erase() would return wrong result.The flash is protected,
> but write or erase the flash would show "OK".
>
> Check the flash write protection state if the write-protection has enbale
> before operating the flash.
>
> Signed-off-by: Chao Zeng <chao.zeng@siemens.com>
> ---
>
> drivers/mtd/spi/sf_probe.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/mtd/spi/sf_probe.c b/drivers/mtd/spi/sf_probe.c
> index 3befbe91ca..f06e6b88bd 100644
> --- a/drivers/mtd/spi/sf_probe.c
> +++ b/drivers/mtd/spi/sf_probe.c
> @@ -109,6 +109,11 @@ static int spi_flash_std_write(struct udevice *dev, u32 offset, size_t len,
> struct mtd_info *mtd = &flash->mtd;
> size_t retlen;
>
> + if (flash->flash_is_locked && flash->flash_is_locked(flash, offset, len)) {
> + debug("SF: Flash is locked\n");
> + return -ENOPROTOOPT;
Keep a debug message, but return 0 please. Writes or erases on protected areas
are ignored by the flash, we should reflect that in the code.
Cheers,
ta
next prev parent reply other threads:[~2021-11-05 22:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 5:21 [PATCH] sf: Querying write-protect status before operating the flash chao zeng
2021-06-29 13:50 ` Jagan Teki
2021-09-08 4:55 ` chaochao2021666
2021-09-13 7:48 ` Jan Kiszka
2021-10-04 13:36 ` Jan Kiszka
2021-11-03 12:18 ` Jan Kiszka
2021-11-04 16:06 ` Tom Rini
2021-11-05 17:17 ` Tudor.Ambarus [this message]
2021-11-05 18:08 ` Jagan Teki
2021-11-08 9:50 ` [PATCH] sf: Querying write-protect status before operating the Michael Walle
2021-11-08 11:01 ` Tudor.Ambarus
2021-11-09 1:52 ` Re:Re: [PATCH] sf: Querying write-protect status before operating the flash chaochao2021666
2021-11-09 8:14 ` Tudor.Ambarus
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=11982722-ce48-9d67-c68d-ad25146aeb2e@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=chao.zeng@siemens.com \
--cc=chaochao2021666@163.com \
--cc=jagan@amarulasolutions.com \
--cc=jan.kiszka@siemens.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--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;
as well as URLs for NNTP newsgroup(s).