From: Pratyush Yadav <pratyush@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org
Subject: [GIT PULL] mtd: spi-nor: changes for v6.11
Date: Fri, 05 Jul 2024 16:21:51 +0200 [thread overview]
Message-ID: <mafs0bk3bor5s.fsf@kernel.org> (raw)
Hi,
Here are the SPI NOR changes for v6.11.
Regards,
Pratyush Yadav
The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:
Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git tags/spi-nor/for-6.11
for you to fetch changes up to d35df77707bf5ae1221b5ba1c8a88cf4fcdd4901:
mtd: spi-nor: winbond: fix w25q128 regression (2024-06-21 17:49:36 +0200)
----------------------------------------------------------------
SPI NOR changes for 6.11
Notable changes:
- Drop support for Xilinx S3AN flashes. These flashes are for the very
old Xilinx Spartan 3 FPGAs and they need some awkward code in the core
to support. Drop support for these flashes, along with the special
handling we needed for them in the core like non-power-of-2 page size
handling and the .setup() callback.
- Fix regression for old w25q128 flashes without SFDP tables. Commit
83e824a4a595 ("mtd: spi-nor: Correct flags for Winbond w25q128")
dropped support for such devices under the assumption that they aren't
being used anymore. Users have now surfaced [0] so fix the regression
by supporting both kind of devices.
- Core cleanups including removal of SPI_NOR_NO_FR flag and
simplification of spi_nor_get_flash_info().
[0] https://lore.kernel.org/r/CALxbwRo_-9CaJmt7r7ELgu+vOcgk=xZcGHobnKf=oT2=u4d4aA@mail.gmail.com/
----------------------------------------------------------------
Michael Walle (6):
mtd: spi-nor: Remove support for Xilinx S3AN flashes
mtd: spi-nor: get rid of non-power-of-2 page size handling
mtd: spi-nor: remove .setup() callback
mtd: spi-nor: get rid of SPI_NOR_NO_FR
mtd: spi-nor: simplify spi_nor_get_flash_info()
mtd: spi-nor: winbond: fix w25q128 regression
drivers/mtd/spi-nor/Makefile | 1 -
drivers/mtd/spi-nor/core.c | 206 ++++++++++++++++-------------------------
drivers/mtd/spi-nor/core.h | 12 ---
drivers/mtd/spi-nor/everspin.c | 19 +++-
drivers/mtd/spi-nor/winbond.c | 2 +
drivers/mtd/spi-nor/xilinx.c | 169 ---------------------------------
6 files changed, 98 insertions(+), 311 deletions(-)
delete mode 100644 drivers/mtd/spi-nor/xilinx.c
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2024-07-05 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 14:21 Pratyush Yadav [this message]
2024-07-20 12:34 ` [GIT PULL] mtd: spi-nor: changes for v6.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=mafs0bk3bor5s.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@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;
as well as URLs for NNTP newsgroup(s).