Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: nick.hawkins@hpe.com
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jean-Marie Verdun <verdun@hpe.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Nick Hawkins <nick.hawkins@hpe.com>
Subject: [PATCH v2 0/3] arm64: Add HPE GSC platform support
Date: Mon, 23 Mar 2026 14:42:20 -0500	[thread overview]
Message-ID: <20260323194223.683487-1-nick.hawkins@hpe.com> (raw)

From: Nick Hawkins <nick.hawkins@hpe.com>

This series adds base platform support for the HPE GSC ARM64
BMC SoC used on HPE servers.

Patch 1 extends the existing hpe,gxp.yaml DT binding to cover GSC-based
boards (per DT maintainer guidance: one binding file per vendor).

Patch 2 adds the ARCH_HPE_GSC Kconfig entry to arm64/Kconfig.platforms.

Patch 3 adds the minimal SoC DTSI and DL340 Gen12 board DTS.  The
full peripheral set (i3c, ethernet, etc.) will follow in a later
series after the relevant subsystem drivers are accepted upstream.

v1 was submitted as a single patch containing only the DT binding.
Based on review feedback from Krzysztof Kozlowski, this v2 expands to
a proper series covering the full base platform introduction.

Changes in v2:
  - Drop hpe,gsc.yaml; extend existing hpe,gxp.yaml instead
    (per Krzysztof Kozlowski review: one binding per vendor)
  - Split into three patches: binding, Kconfig, and DTS
  - Add gsc.dtsi + gsc-dl340gen12.dts
  - Add ARCH_HPE_GSC to arm64/Kconfig.platforms

Nick Hawkins (3):
  dt-bindings: arm: hpe,gxp: Add HPE GSC platform compatible
  arm64: Kconfig: Add ARCH_HPE_GSC platform
  arm64: dts: hpe: Add HPE GSC SoC and DL340 Gen12 board DTS

 .../devicetree/bindings/arm/hpe,gxp.yaml      | 11 ++-
 MAINTAINERS                                   |  5 ++
 arch/arm64/Kconfig.platforms                  | 18 +++++
 arch/arm64/boot/dts/hpe/Makefile              |  2 +
 arch/arm64/boot/dts/hpe/gsc-dl340gen12.dts    | 18 +++++
 arch/arm64/boot/dts/hpe/gsc.dtsi              | 73 +++++++++++++++++++
 6 files changed, 126 insertions(+), 1 deletion(-)
 create mode 100644 arch/arm64/boot/dts/hpe/Makefile
 create mode 100644 arch/arm64/boot/dts/hpe/gsc-dl340gen12.dts
 create mode 100644 arch/arm64/boot/dts/hpe/gsc.dtsi


base-commit: 3f4a08e64442340f4807de63e30aef22cc308830
-- 
2.34.1



             reply	other threads:[~2026-03-23 19:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 19:42 nick.hawkins [this message]
2026-03-23 19:42 ` [PATCH v2 1/3] dt-bindings: arm: hpe,gxp: Add HPE GSC platform compatible nick.hawkins
2026-03-23 19:48   ` Conor Dooley
2026-03-23 19:42 ` [PATCH v2 2/3] arm64: Kconfig: Add ARCH_HPE_GSC platform nick.hawkins
2026-03-24  9:18   ` Krzysztof Kozlowski
2026-03-23 19:42 ` [PATCH v2 3/3] arm64: dts: hpe: Add HPE GSC SoC and DL340 Gen12 board DTS nick.hawkins
2026-03-24  9:20   ` Krzysztof Kozlowski

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=20260323194223.683487-1-nick.hawkins@hpe.com \
    --to=nick.hawkins@hpe.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=verdun@hpe.com \
    --cc=will@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