linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: soc <soc@lists.linux.dev>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org,  linux-kernel@vger.kernel.org,
	Joel Stanley <joel@jms.id.au>
Subject: [GIT PULL] nuvoton arm64: early devicetree changes for 6.18
Date: Mon, 25 Aug 2025 14:05:03 +0930	[thread overview]
Message-ID: <bf3734aab62a5fcc8959261551bb4b1fa636efbd.camel@codeconstruct.com.au> (raw)

Hello SoC maintainers,

The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/bmc/linux.git tags/nuvoton-arm64-6.18-devicetree-0

for you to fetch changes up to 13587befb34ffa5d605196494c243420e045f28e:

  arm64: dts: nuvoton: add refclk and update peripheral clocks for NPCM845 (2025-08-11 09:38:08 +0930)

----------------------------------------------------------------
Early Nuvoton arm64 devicetree updates for 6.18

Integrate changes from Tomer reworking devicetree pinctrl, reset, and clk nodes
for NPCM845-based platforms.

----------------------------------------------------------------
Tomer Maimon (3):
      arm64: dts: nuvoton: npcm845: Add pinctrl groups
      arm64: dts: nuvoton: combine NPCM845 reset and clk nodes
      arm64: dts: nuvoton: add refclk and update peripheral clocks for NPCM845

 arch/arm64/boot/dts/nuvoton/nuvoton-common-npcm8xx.dtsi | 669 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--
 arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dts     |   6 +
 2 files changed, 663 insertions(+), 12 deletions(-)


                 reply	other threads:[~2025-08-25  4:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bf3734aab62a5fcc8959261551bb4b1fa636efbd.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@lists.linux.dev \
    /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).