From: Conor Dooley <conor@kernel.org>
To: soc@kernel.org
Cc: conor@kernel.org, jonathan.cameron@huawei.com, soc@kernel.org
Subject: [GIT PULL] standalone cache drivers for v6.19
Date: Thu, 27 Nov 2025 17:10:11 +0000 [thread overview]
Message-ID: <20251127-facelift-revisable-772b117a799b@spud> (raw)
[-- Attachment #1: Type: text/plain, Size: 3209 bytes --]
Hey folks,
Please pull my standalone cache driver 6.19 update.
The base here is a wee bit odd, I forgot to fast-forward this cycle and
didn't want to do a last-minute rebase when I noticed this today.
Cheers,
Conor.
The following changes since commit 941327ca5ddd45cfc4dd960cbbabed9e2b5cb1b0:
cache: sifive_ccache: Optimize cache flushes (2025-09-11 19:13:21 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ cache-for-v6.19
for you to fetch changes up to 055bcc552b5181da208038c1de9437e9cca69380:
MAINTAINERS: refer to intended file in STANDALONE CACHE CONTROLLER DRIVERS (2025-11-21 18:42:02 +0000)
----------------------------------------------------------------
standalone cache drivers for v6.19
ccache:
Add a compatible for the pic64gx SoC. No driver change needed, as it
falls back to the PolarFire SoC.
hisi hha/generic cpu cache maintenance:
Add support for a non-architectural mechanism for invalidating memory
regions, needed for some cxl implementations on arm64 (and probably
elsewhere in the future). The HiSilicon Hydra Home Agent is the first
driver to provide this support.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
----------------------------------------------------------------
Jonathan Cameron (4):
memregion: Drop unused IORES_DESC_* parameter from cpu_cache_invalidate_memregion()
arm64: Select GENERIC_CPU_CACHE_MAINTENANCE
MAINTAINERS: Add Jonathan Cameron to drivers/cache and add lib/cache_maint.c + header
cache: Make top level Kconfig menu a boolean dependent on RISCV
Lukas Bulwahn (1):
MAINTAINERS: refer to intended file in STANDALONE CACHE CONTROLLER DRIVERS
Pierre-Henry Moussay (1):
dt-bindings: cache: sifive,ccache0: add a pic64gx compatible
Yicong Yang (2):
memregion: Support fine grained invalidate by cpu_cache_invalidate_memregion()
lib: Support ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION
Yushan Wang (1):
cache: Support cache maintenance for HiSilicon SoC Hydra Home Agent
.../devicetree/bindings/cache/sifive,ccache0.yaml | 5 +
MAINTAINERS | 3 +
arch/arm64/Kconfig | 2 +
arch/x86/mm/pat/set_memory.c | 2 +-
drivers/cache/Kconfig | 37 +++-
drivers/cache/Makefile | 2 +
drivers/cache/hisi_soc_hha.c | 194 +++++++++++++++++++++
drivers/cxl/core/region.c | 5 +-
drivers/nvdimm/region.c | 2 +-
drivers/nvdimm/region_devs.c | 2 +-
include/linux/cache_coherency.h | 61 +++++++
include/linux/memregion.h | 16 +-
lib/Kconfig | 3 +
lib/Makefile | 2 +
lib/cache_maint.c | 138 +++++++++++++++
15 files changed, 462 insertions(+), 12 deletions(-)
create mode 100644 drivers/cache/hisi_soc_hha.c
create mode 100644 include/linux/cache_coherency.h
create mode 100644 lib/cache_maint.c
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2025-11-27 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 17:10 Conor Dooley [this message]
2025-11-27 22:10 ` [GIT PULL] standalone cache drivers for v6.19 patchwork-bot+linux-soc
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=20251127-facelift-revisable-772b117a799b@spud \
--to=conor@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=soc@kernel.org \
/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