public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Pratyush Yadav <pratyush@kernel.org>,
	Michael Walle <mwalle@kernel.org>,
	linux-mtd@lists.infradead.org
Subject: [GIT PULL] mtd: spi-nor: changes for v6.14
Date: Mon, 20 Jan 2025 11:14:20 +0000	[thread overview]
Message-ID: <mafs0sepd4u0j.fsf@kernel.org> (raw)

Hi Miquel,

Here are the SPI NOR changes for v6.14.

Regards,
Pratyush Yadav

The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

  Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git tags/spi-nor/for-6.14

for you to fetch changes up to 943e5f85600708c348f7b23d3c1cff1cf9763032:

  mtd: spi-nor: sysfs: constify 'struct bin_attribute' (2025-01-13 17:47:03 +0000)

----------------------------------------------------------------
SPI NOR changes for 6.14

Notable changes:

- Add flash entries for Atmel AT25SF321, Spansion S28HL256T, S28HL02GT.

- Add support for vcc-supply regulators and their DT bindings.

- Drop mx25u25635f entry. The flash shares its ID with mx25u25645g and
  both parts have an SFDP table. Removing their entry lets them be
  driven by the generic SFDP-based driver.

----------------------------------------------------------------
Marcus Folkesson (1):
      mtd: spi-nor: atmel: add at25sf321 entry

Parth Pancholi (1):
      mtd: spi-nor: macronix: remove mx25u25635f from parts list to enable SFDP

Peng Fan (2):
      dt-bindings: mtd: jedec,spi-nor: add optional vcc-supply
      mtd: spi-nor: support vcc-supply regulator

Takahiro Kuwano (2):
      mtd: spi-nor: spansion: Add support for S28HL256T
      mtd: spi-nor: spansion: Add support for S28HL02GT

Thomas Weißschuh (1):
      mtd: spi-nor: sysfs: constify 'struct bin_attribute'

Tudor Ambarus (3):
      mtd: spi-nor: macronix: use nor->addr_nbytes
      mtd: spi-nor: use local variable for struct device
      mtd: spi-nor: extend description of size member of struct flash_info

 .../devicetree/bindings/mtd/jedec,spi-nor.yaml        |  4 ++++
 drivers/mtd/spi-nor/atmel.c                           |  4 ++++
 drivers/mtd/spi-nor/core.c                            | 19 ++++++++++++-------
 drivers/mtd/spi-nor/core.h                            |  6 +++++-
 drivers/mtd/spi-nor/macronix.c                        |  9 ++-------
 drivers/mtd/spi-nor/spansion.c                        | 10 ++++++++++
 drivers/mtd/spi-nor/sysfs.c                           |  8 ++++----
 7 files changed, 41 insertions(+), 19 deletions(-)

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

             reply	other threads:[~2025-01-20 11:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 11:14 Pratyush Yadav [this message]
2025-01-24 10:04 ` [GIT PULL] mtd: spi-nor: changes for v6.14 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=mafs0sepd4u0j.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