From: Dawid Glazik <dawid.glazik@linux.intel.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
dawid.glazik@linux.intel.com, maciej.lawniczak@intel.com
Subject: [PATCH v4 0/3] arm: dts: aspeed: add Intel AVCRP and JNCRP BMC platforms
Date: Mon, 26 Oct 2026 17:40:27 +0100 [thread overview]
Message-ID: <cover.1792749922.git.dawid.glazik@linux.intel.com> (raw)
This series adds initial upstream support for the Intel AVCRP and JNCRP
BMC platforms based on the ASPEED AST2600.
The first patch adds the board compatibles to the ASPEED binding. The
remaining two patches add the board DTS files and register them in the
ASPEED DTB build list.
Changes in v4:
- Rebased onto aspeed/arm/dt of bmc/linux.git. No other changes.
Dawid Glazik (3):
dt-bindings: arm: aspeed: Add Intel AVCRP and JNCRP boards
ARM: dts: aspeed: add Intel AVCRP BMC
ARM: dts: aspeed: add Intel JNCRP BMC
.../bindings/arm/aspeed/aspeed.yaml | 2 +
arch/arm/boot/dts/aspeed/Makefile | 2 +
.../dts/aspeed/aspeed-bmc-intel-avcrp.dts | 322 ++++++++++++++++++
.../dts/aspeed/aspeed-bmc-intel-jncrp.dts | 276 +++++++++++++++
4 files changed, 602 insertions(+)
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-intel-avcrp.dts
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-intel-jncrp.dts
base-commit: 8db593481c8669eddb8b4e21ea44f3fa11d9f030
--
2.43.0
next reply other threads:[~2026-10-26 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 16:40 Dawid Glazik [this message]
2026-10-26 16:40 ` [PATCH v4 1/3] dt-bindings: arm: aspeed: Add Intel AVCRP and JNCRP boards Dawid Glazik
2026-10-26 16:40 ` [PATCH v4 2/3] ARM: dts: aspeed: add Intel AVCRP BMC Dawid Glazik
2026-10-26 16:40 ` [PATCH v4 3/3] ARM: dts: aspeed: add Intel JNCRP BMC Dawid Glazik
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=cover.1792749922.git.dawid.glazik@linux.intel.com \
--to=dawid.glazik@linux.intel.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.lawniczak@intel.com \
--cc=robh@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
all inboxes | Powered by JetHome®