Linux SOC development
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: soc@kernel.org
Cc: conor@kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Microchip RISC-V devicetrees for v7.2
Date: Mon, 8 Jun 2026 11:14:42 +0100	[thread overview]
Message-ID: <20260608-grumbling-gigantic-b0bb128634f2@spud> (raw)

[-- Attachment #1: Type: text/plain, Size: 2662 bytes --]

Hey folks,

Please pull my changes for 7.2, all of which are cleanup/low priority
fixes written by yours truly.

It's probable that I will have a second PR, because I am waiting for
Stephen to hopefully merge my Canaan clock driver series that is a
pre-requisite for the addition of the Canaan k230 SoC. I'd have sent
this earlier, but I was hoping that k230 support would be ready in time.

Cheers,
Conor.

The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:

  Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-dt-for-v7.2

for you to fetch changes up to 3869417f8996fb076998342d0db560fdd795a3a6:

  riscv: dts: microchip: remove redudant enabling of syscontroller (2026-05-15 17:51:09 +0100)

----------------------------------------------------------------
Microchip RISC-V devicetrees for v7.2

This time around, there's nothing other than patches for Microchip
boards. All of this is low priority fixes and cleanup, centred on the
pic64gx and beaglev-fire boards. There is no new support added.

Signed-off-by: Conor Dooley <conor.dooley@microchip.com>

----------------------------------------------------------------
Conor Dooley (10):
      riscv: dts: microchip: add tsu clock to macb on pic64gx
      riscv: dts: microchip: update pic64gx gpio interrupts to better match the SoC
      riscv: dts: microchip: sort pic64gx i2c nodes alphanumerically
      riscv: dts: microchip: gpio controllers on mpfs need 2 interrupt cells
      riscv: dts: microchip: remove gpio hogs from beaglev-fire
      riscv: dts: microchip: clean up beaglev-fire regulator node names
      riscv: dts: microchip: add adc interrupt on beaglev-fire
      riscv: dts: microchip: add gpio line names on beaglev-fire
      riscv: dts: microchip: fix pic64gx gpio interrupt-cells
      riscv: dts: microchip: remove redudant enabling of syscontroller

 .../riscv/boot/dts/microchip/mpfs-beaglev-fire.dts | 37 ++++++------
 arch/riscv/boot/dts/microchip/mpfs-disco-kit.dts   |  4 --
 .../boot/dts/microchip/mpfs-icicle-kit-common.dtsi |  4 --
 arch/riscv/boot/dts/microchip/mpfs-m100pfsevp.dts  |  4 --
 arch/riscv/boot/dts/microchip/mpfs-polarberry.dts  |  4 --
 arch/riscv/boot/dts/microchip/mpfs-sev-kit.dts     |  4 --
 arch/riscv/boot/dts/microchip/mpfs-tysom-m.dts     |  4 --
 arch/riscv/boot/dts/microchip/mpfs.dtsi            |  6 +-
 .../boot/dts/microchip/pic64gx-curiosity-kit.dts   | 67 ++++++++++++----------
 arch/riscv/boot/dts/microchip/pic64gx.dtsi         | 46 +++++++++++----
 10 files changed, 95 insertions(+), 85 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2026-06-08 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 10:14 Conor Dooley [this message]
2026-06-09 16:40 ` [GIT PULL] Microchip RISC-V devicetrees for v7.2 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=20260608-grumbling-gigantic-b0bb128634f2@spud \
    --to=conor@kernel.org \
    --cc=linux-kernel@vger.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