From: Conor Dooley <conor@kernel.org>
To: soc@kernel.org
Cc: conor@kernel.org, linux-riscv@lists.infradead.org
Subject: [GIT PULL] RISC-V soc-drivers for v6.19
Date: Thu, 27 Nov 2025 16:07:07 +0000 [thread overview]
Message-ID: <20251127-wish-shining-300e8fb80599@spud> (raw)
[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]
Hey folks,
Please pull my 6.19 soc driver changes.
Cheers,
Conor.
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ soc-drivers-for-v6.19
for you to fetch changes up to 66c6ceb41ed375773491c5d024167a2cbe6fe944:
MAINTAINERS: rename Microchip RISC-V entry (2025-11-11 16:52:30 +0000)
----------------------------------------------------------------
RISC-V soc-drivers for v6.19
Microchip:
Add bindings and mfd drivers for two syscon regions on PolarFire SoC,
needed as part of a rework of the devicetree to permit supporting,
among other things, pinctrl sanely and avoiding the "new" pic64gx SoC
ever using the original incorrect clock nodes. Fiddle with the Microchip
RISC-V MAINTAINERS entry to add these drivers and avoid branding it FPGA
only.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
----------------------------------------------------------------
Conor Dooley (4):
dt-bindings: soc: microchip: document the simple-mfd syscon on PolarFire SoC
soc: microchip: add mfd drivers for two syscon regions on PolarFire SoC
MAINTAINERS: add new soc drivers to Microchip RISC-V entry
MAINTAINERS: rename Microchip RISC-V entry
.../microchip/microchip,mpfs-mss-top-sysreg.yaml | 47 ++++++++++++++++++++++
MAINTAINERS | 4 +-
drivers/soc/microchip/Kconfig | 12 ++++++
drivers/soc/microchip/Makefile | 1 +
drivers/soc/microchip/mpfs-control-scb.c | 38 +++++++++++++++++
drivers/soc/microchip/mpfs-mss-top-sysreg.c | 44 ++++++++++++++++++++
6 files changed, 145 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/soc/microchip/microchip,mpfs-mss-top-sysreg.yaml
create mode 100644 drivers/soc/microchip/mpfs-control-scb.c
create mode 100644 drivers/soc/microchip/mpfs-mss-top-sysreg.c
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2025-11-27 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 16:07 Conor Dooley [this message]
2025-11-27 22:10 ` [GIT PULL] RISC-V soc-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-wish-shining-300e8fb80599@spud \
--to=conor@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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