From: Jan Kiszka <jan.kiszka@siemens.com>
To: chaochao2021666 <chaochao2021666@163.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Tom Rini <trini@konsulko.com>
Cc: U-Boot-Denx <u-boot@lists.denx.de>, Vignesh R <vigneshr@ti.com>,
Chao Zeng <chao.zeng@siemens.com>
Subject: Re: [PATCH] sf: Querying write-protect status before operating the flash
Date: Wed, 3 Nov 2021 13:18:42 +0100 [thread overview]
Message-ID: <a75ad456-6ee8-6cd1-a84f-889d35ca5709@siemens.com> (raw)
In-Reply-To: <e47a05cf-42a9-48d0-0e64-bd53dadafd5a@siemens.com>
On 04.10.21 15:36, Jan Kiszka wrote:
> On 13.09.21 09:48, Jan Kiszka wrote:
>> Hi all,
>>
>> Chao, please no top-post on mailing list. Also check your mail client,
>> it seems to inject a lot of bogus newlines.
>>
>> On 08.09.21 06:55, chaochao2021666 wrote:
>>>
>>>
>>>
>>> HI Jagan
>>>
>>>
>>>
>>> sorry for the delay response.
>>>
>>>
>>> And I have checked the maser. There is still a problem with this feature。
>>>
>>>
>>> reproduce steps:
>>> 1. enable the flash protect function
>>> 2. using sf cmd to erase the flash. I can get the erase "OK",not the "error".
>>>
>>>
>>>
>>> I think the root cause is that the detection mechanism is missing and to judge the permissions of the action
>>>
>>> So pull this PR to improve the erase flow
>>>
>>>
>>> another question:
>>> how can I visit the u-boot-spi/next? do there any link?
>>>
>>
>> See MAINTAINERS: https://source.denx.de/u-boot/custodians/u-boot-spi.git
>>
>> But also that tree contains no usage of the flash_is_locked callback.
>> That was once evaluated by drivers/mtd/spi/spi_flash.c but then
>> forgotten in the new SPI NOR framework it seems.
>>
>> Chao's patch makes sense to me to restore this feature.
>>
>> Jan
>>
>>>
>>>
>>>
>>>
>>> BRs
>>> Chao
>>>
>>>
>>>
>>> At 2021-06-29 21:50:28, "Jagan Teki" <jagan@amarulasolutions.com> wrote:
>>>> On Tue, Jun 22, 2021 at 10:51 AM chao zeng <chaochao2021666@163.com> 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>
>>>>> ---
>>>>
>>>> Does it broken on master? if yes can you check in u-boot-spi/next?
>>>>
>>>> Jagan.
>>
>
> Ping - how do we proceed here?
>
> Jan
>
Ping² - who can help to move this forward?
Thanks,
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-11-03 12:18 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 [this message]
2021-11-04 16:06 ` Tom Rini
2021-11-05 17:17 ` Tudor.Ambarus
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=a75ad456-6ee8-6cd1-a84f-889d35ca5709@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=chao.zeng@siemens.com \
--cc=chaochao2021666@163.com \
--cc=jagan@amarulasolutions.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).