From: "Michael Walle" <mwalle@kernel.org>
To: "Marek Vasut" <marek.vasut@mailbox.org>,
"Marek Vasut" <marek.vasut+renesas@mailbox.org>
Cc: <linux-mtd@lists.infradead.org>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Pratyush Yadav" <pratyush@kernel.org>,
"Richard Weinberger" <richard@nod.at>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] mtd: spi-nor: winbond: Add support for W77Q51NW
Date: Mon, 28 Jul 2025 08:32:55 +0200 [thread overview]
Message-ID: <DBNH88949QTH.3I3MSOA019UJL@kernel.org> (raw)
In-Reply-To: <0d0cd3cb-61e5-4ec6-958b-ec48b82429bf@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
> >> I have limited supply of these devices, so OTP is untested. The flash
> >> does have OTP registers, that's why the .otp entry is there. Why should
> >> I remove it if the OTP registers are in the chip ?
> >
> > We only add tested features. I'm just the messenger here :o. Anyway,
> > OTP is not really one-time-programmable here, you can write and
> > erase it again as long as you don't lock it, if that was your
> > concern.
>
> So how do I test the OTP without locking it ?
flash_otp_{write,info,dump,erase}, just don't use flash_otp_lock.
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-07-28 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 20:22 Marek Vasut
2025-07-22 8:25 ` Tudor Ambarus
2025-07-22 8:43 ` Michael Walle
2025-07-22 9:37 ` Tudor Ambarus
2025-07-22 13:51 ` Michael Walle
2025-07-22 14:28 ` Marek Vasut
2025-07-23 6:36 ` Michael Walle
2025-07-27 20:26 ` Marek Vasut
2025-07-28 6:32 ` Michael Walle [this message]
2025-07-29 3:51 ` Marek Vasut
2025-07-29 8:48 ` Michael Walle
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=DBNH88949QTH.3I3MSOA019UJL@kernel.org \
--to=mwalle@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=marek.vasut@mailbox.org \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--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
all inboxes | Powered by JetHome®