From: Michael Walle <michael@walle.cc> To: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Tudor Ambarus <tudor.ambarus@microchip.com>, Michael Walle <michael@walle.cc>, Pratyush Yadav <p.yadav@ti.com>, Miquel Raynal <miquel.raynal@bootlin.com>, Richard Weinberger <richard@nod.at>, Vignesh Raghavendra <vigneshr@ti.com> Subject: [PATCH v4 0/4] mtd: spi-nor: otp: 4 byte mode fix and erase support Date: Fri, 21 May 2021 21:40:30 +0200 [thread overview] Message-ID: <20210521194034.15249-1-michael@walle.cc> (raw) This series is the follow up on the single patch mtd: spi-nor: implement OTP erase for Winbond and similar flashes Pratyush Yadav discovered a likely problem with bigger flashes, the address to access the security registers is either 3 or 4 byte (at least for winbond flashes). Changes since v3: - new patch to check for read-only OTP regions before writing - clarify term "security register" - don't combine lock and erase functions anymore. there are now more difference than similarities. Changes since v2: - fix 3/4 byte mode access - use spi_nor_erase_sector() by swapping the nor->erase_opcode - use more consistent wording regarding the security registers Changes since v1: - fixed kernel doc Michael Walle (4): mtd: spi-nor: otp: fix access to security registers in 4 byte mode mtd: spi-nor: otp: use more consistent wording mtd: spi-nor: otp: return -EROFS if region is read-only mtd: spi-nor: otp: implement erase for Winbond and similar flashes drivers/mtd/spi-nor/core.c | 2 +- drivers/mtd/spi-nor/core.h | 4 + drivers/mtd/spi-nor/otp.c | 147 +++++++++++++++++++++++++++++++--- drivers/mtd/spi-nor/winbond.c | 1 + 4 files changed, 143 insertions(+), 11 deletions(-) -- 2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: Michael Walle <michael@walle.cc> To: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org Cc: Tudor Ambarus <tudor.ambarus@microchip.com>, Michael Walle <michael@walle.cc>, Pratyush Yadav <p.yadav@ti.com>, Miquel Raynal <miquel.raynal@bootlin.com>, Richard Weinberger <richard@nod.at>, Vignesh Raghavendra <vigneshr@ti.com> Subject: [PATCH v4 0/4] mtd: spi-nor: otp: 4 byte mode fix and erase support Date: Fri, 21 May 2021 21:40:30 +0200 [thread overview] Message-ID: <20210521194034.15249-1-michael@walle.cc> (raw) This series is the follow up on the single patch mtd: spi-nor: implement OTP erase for Winbond and similar flashes Pratyush Yadav discovered a likely problem with bigger flashes, the address to access the security registers is either 3 or 4 byte (at least for winbond flashes). Changes since v3: - new patch to check for read-only OTP regions before writing - clarify term "security register" - don't combine lock and erase functions anymore. there are now more difference than similarities. Changes since v2: - fix 3/4 byte mode access - use spi_nor_erase_sector() by swapping the nor->erase_opcode - use more consistent wording regarding the security registers Changes since v1: - fixed kernel doc Michael Walle (4): mtd: spi-nor: otp: fix access to security registers in 4 byte mode mtd: spi-nor: otp: use more consistent wording mtd: spi-nor: otp: return -EROFS if region is read-only mtd: spi-nor: otp: implement erase for Winbond and similar flashes drivers/mtd/spi-nor/core.c | 2 +- drivers/mtd/spi-nor/core.h | 4 + drivers/mtd/spi-nor/otp.c | 147 +++++++++++++++++++++++++++++++--- drivers/mtd/spi-nor/winbond.c | 1 + 4 files changed, 143 insertions(+), 11 deletions(-) -- 2.20.1 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2021-05-21 19:40 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-21 19:40 Michael Walle [this message] 2021-05-21 19:40 ` [PATCH v4 0/4] mtd: spi-nor: otp: 4 byte mode fix and erase support Michael Walle 2021-05-21 19:40 ` [PATCH v4 1/4] mtd: spi-nor: otp: fix access to security registers in 4 byte mode Michael Walle 2021-05-21 19:40 ` Michael Walle 2021-05-31 8:27 ` Tudor.Ambarus 2021-05-31 8:27 ` Tudor.Ambarus 2021-05-21 19:40 ` [PATCH v4 2/4] mtd: spi-nor: otp: use more consistent wording Michael Walle 2021-05-21 19:40 ` Michael Walle 2021-05-31 8:28 ` Tudor.Ambarus 2021-05-31 8:28 ` Tudor.Ambarus 2021-05-21 19:40 ` [PATCH v4 3/4] mtd: spi-nor: otp: return -EROFS if region is read-only Michael Walle 2021-05-21 19:40 ` Michael Walle 2021-05-25 19:33 ` Pratyush Yadav 2021-05-25 19:33 ` Pratyush Yadav 2021-05-26 10:41 ` Michael Walle 2021-05-26 10:41 ` Michael Walle 2021-05-26 11:13 ` Pratyush Yadav 2021-05-26 11:13 ` Pratyush Yadav 2021-05-31 8:52 ` Tudor.Ambarus 2021-05-31 8:52 ` Tudor.Ambarus 2021-06-01 13:02 ` Michael Walle 2021-06-01 13:02 ` Michael Walle 2021-06-03 5:22 ` Tudor.Ambarus 2021-06-03 5:22 ` Tudor.Ambarus 2021-05-21 19:40 ` [PATCH v4 4/4] mtd: spi-nor: otp: implement erase for Winbond and similar flashes Michael Walle 2021-05-21 19:40 ` Michael Walle 2021-05-25 19:37 ` Pratyush Yadav 2021-05-25 19:37 ` Pratyush Yadav 2021-05-31 8:56 ` Tudor.Ambarus 2021-05-31 8:56 ` Tudor.Ambarus 2021-06-01 13:30 ` Michael Walle 2021-06-01 13:30 ` Michael Walle 2021-06-03 5:08 ` Tudor.Ambarus 2021-06-03 5:08 ` Tudor.Ambarus 2021-06-03 5:30 ` Tudor.Ambarus 2021-06-03 5:30 ` 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=20210521194034.15249-1-michael@walle.cc \ --to=michael@walle.cc \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=miquel.raynal@bootlin.com \ --cc=p.yadav@ti.com \ --cc=richard@nod.at \ --cc=tudor.ambarus@microchip.com \ --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: linkBe 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.