From: Anirudh Srinivasan <anirudhsriniv@gmail.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,
Zev Weiss <zev@bewilderbeest.net>,
Renze Nicolai <renze@rnplus.nl>,
Anirudh Srinivasan <anirudhsriniv@gmail.com>
Subject: [PATCH 0/2] Add device tree for Asrock Paul IPMI Card
Date: Sun, 25 Jan 2026 15:00:37 -0600 [thread overview]
Message-ID: <20260125-asrock-paul-v1-0-956085a4bd06@gmail.com> (raw)
Adds support for Asrock Paul IPMI Card [1], which is an AST2500 based
PCIe card that provides BMC functionality. The supported functionality
is similar to the Asus Kommando IPMI Card, support for which was sent
previously [2].
Supported functionality includes UART, Booting from Primary SPI,
Networking, KVM functionality (USB Gadget and Video Engine), LEDs and
GPIO Power control. Complete BMC functionality has been tested on an
OpenBMC build available here [3], relying on this kernel branch [4].
For some reason, the Video Engine isn't always
stable when the host PC's video output goes black/changes
resolution, resulting in a hang and a subsequent reset of the Aspeed.
Applying this patch [5] from the Aspeed vendor kernel seems to fix this
issue. This doesn't require any changes to the device tree for this
device though, so I think it shouldn't affect this patch series.
[1] https://www.asrockrack.com/general/productdetail.asp?Model=PAUL
[2] https://lore.kernel.org/linux-aspeed/20260114-asus-ipmi-expansion-card-v2-0-12b72d20a9b9@gmail.com/
[3] https://github.com/Genius1237/openbmc/commits/asrock-paul-ipmi-card/
[4] https://github.com/openbmc/linux/compare/dev-6.18...Genius1237:linux:asrock-paul-ipmi-card-6.18
[5] https://lore.kernel.org/linux-aspeed/20251124-video_dram_reset-v1-1-9d37229e4ec5@aspeedtech.com/
Signed-off-by: Anirudh Srinivasan <anirudhsriniv@gmail.com>
---
Anirudh Srinivasan (2):
dt-bindings: arm: aspeed: Add Asrock Paul IPMI card
ARM: dts: aspeed: Add Asrock Paul IPMI card
.../devicetree/bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../aspeed/aspeed-bmc-asrock-paul-ipmi-card.dts | 131 +++++++++++++++++++++
3 files changed, 133 insertions(+)
---
base-commit: 9448598b22c50c8a5bb77a9103e2d49f134c9578
change-id: 20260125-asrock-paul-5d0d4b15c8bc
Best regards,
--
Anirudh Srinivasan <anirudhsriniv@gmail.com>
next reply other threads:[~2026-01-25 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 21:00 Anirudh Srinivasan [this message]
2026-01-25 21:00 ` [PATCH 1/2] dt-bindings: arm: aspeed: Add Asrock Paul IPMI card Anirudh Srinivasan
2026-01-26 20:27 ` Conor Dooley
2026-01-25 21:00 ` [PATCH 2/2] ARM: dts: " Anirudh Srinivasan
2026-02-09 5:30 ` [PATCH 0/2] Add device tree for Asrock Paul IPMI Card Andrew Jeffery
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=20260125-asrock-paul-v1-0-956085a4bd06@gmail.com \
--to=anirudhsriniv@gmail.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=renze@rnplus.nl \
--cc=robh@kernel.org \
--cc=zev@bewilderbeest.net \
/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