Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev
Cc: dinguyen@kernel.org, devicetree@vger.kernel.org
Subject: [GIT PULL] arm64: dts: socfpga: updates for v7.3
Date: Tue, 28 Jul 2026 22:23:08 -0500	[thread overview]
Message-ID: <20260729032308.1359743-1-dinguyen@kernel.org> (raw)

The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:

  Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_dts_updates_for_v7.3

for you to fetch changes up to ff98c9832fd430ba7b3158b8521002c8eb8aa16c:

  arm64: dts: socfpga: use consistent QSPI boot partition label (2026-07-27 22:09:15 -0500)

----------------------------------------------------------------
SoCFPGA DTS updates for v7.3
- dt-bindings updates:
	- Document compatible for Agilex72
	- Document additional interrupts for Agilex5

- Add the additional interrupts for the gmac on Agilex5
- Use decimal number for interrupts, not hexadecimal
- Enable the SMMU on Agilex5
- Add dma-coherent on XGMAC nodes
- Add initial support for the Agilex72 SoCDK
- Correct indentation on Arria10
- Update QSPI boot partition label

----------------------------------------------------------------
Dinh Nguyen (2):
      dt-bindings: net: altr,socfpga-stmmac: add more interrupts for Agilex5
      arm64: dts: socfpga: agilex5: update channel interrupts for gmac1 and gmac2

Geert Uytterhoeven (1):
      arm64: dts: intel: keembay: Always use decimal interrupts

Krzysztof Kozlowski (1):
      ARM: dts: intel: arria10: Correct indentation

Nazim Amirul (5):
      arm64: dts: socfpga: agilex5: Add per-channel interrupts to gmac0
      arm64: dts: socfpga: agilex5: Enable the SMMU
      arm64: dts: socfpga: agilex5: Add dma-coherent to XGMAC nodes
      dt-bindings: arm: altera: Add Agilex72 SoCFPGA compatible strings
      arm64: dts: socfpga: agilex72: Add initial device tree

Tze Yee Ng (1):
      arm64: dts: socfpga: use consistent QSPI boot partition label

 Documentation/devicetree/bindings/arm/altera.yaml  |   6 +
 .../bindings/net/altr,socfpga-stmmac.yaml          |  46 +++++-
 .../boot/dts/intel/socfpga/socfpga_arria10.dtsi    |   2 +-
 arch/arm64/boot/dts/intel/Makefile                 |   1 +
 arch/arm64/boot/dts/intel/keembay-soc.dtsi         |   2 +-
 .../arm64/boot/dts/intel/socfpga_agilex3_socdk.dts |   2 +-
 arch/arm64/boot/dts/intel/socfpga_agilex5.dtsi     | 112 ++++++++++++++-
 .../arm64/boot/dts/intel/socfpga_agilex5_socdk.dts |   2 +-
 .../boot/dts/intel/socfpga_agilex5_socdk_013b.dts  |   2 +-
 .../dts/intel/socfpga_agilex5_socdk_modular.dts    |   2 +-
 arch/arm64/boot/dts/intel/socfpga_agilex72.dtsi    | 156 +++++++++++++++++++++
 .../boot/dts/intel/socfpga_agilex72_socdk.dts      |  27 ++++
 12 files changed, 346 insertions(+), 14 deletions(-)
 create mode 100644 arch/arm64/boot/dts/intel/socfpga_agilex72.dtsi
 create mode 100644 arch/arm64/boot/dts/intel/socfpga_agilex72_socdk.dts


                 reply	other threads:[~2026-07-29  3:23 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=20260729032308.1359743-1-dinguyen@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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