public inbox for linux-aspeed@lists.ozlabs.org
 help / color / mirror / Atom feed
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: anirudhsriniv@gmail.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Add device tree for Asus IPMI Card
Date: Sun, 11 Jan 2026 14:10:30 -0600	[thread overview]
Message-ID: <20260111201040.162880-1-anirudhsriniv@gmail.com> (raw)

Adds support for Asus IPMI Card [1], which is a PCIe card with an
AST2600 on it that provides BMC functionality to any host without an
onboard BMC as long as it has a PCIe slot.

Currently supported functionality includes UART, NIC, booting from SPI,
KVM functionality(usb gadget for host, reading VGA framebuffer from
host) and LED/Power Control via GPIOs. This functionality has been
tested on an OpenBMC build available here [2]. This requires a modified
u-boot device tree [3], which I can also submit if needed.

The card supports some additional functionality in it's stock firmware
like fan headers with fan speed control, host bios flashing via SPI, PSU
monitoring via an SMBUS connector, a custom ASUS SMBUS connector to talk
to select ASUS motherboards that support it and exposing a IPMI device
via PCIe to the host. These are unsupported at the moment.


[1] https://www.asus.com/supportonly/ipmi%20expansion%20card/helpdesk_manual/
[2] https://github.com/openbmc/openbmc/compare/master...Genius1237:openbmc:asus-ipmi-card
[3] https://github.com/Genius1237/u-boot/commit/1b1b7daa85f6c998e5f404296b3da43077a2758e


Anirudh Srinivasan (2):
  dt-bindings: arm: aspeed: Add Asus IPMI card
  ARM: dts: aspeed: Add Asus IPMI card BMC

 .../bindings/arm/aspeed/aspeed.yaml           |   1 +
 arch/arm/boot/dts/aspeed/Makefile             |   1 +
 .../dts/aspeed/aspeed-bmc-asus-ipmi-card.dts  | 137 ++++++++++++++++++
 3 files changed, 139 insertions(+)
 create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-asus-ipmi-card.dts

-- 
2.52.0



             reply	other threads:[~2026-01-11 23:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-11 20:10 Anirudh Srinivasan [this message]
2026-01-11 20:10 ` [PATCH 1/2] dt-bindings: arm: aspeed: Add Asus IPMI card Anirudh Srinivasan
2026-01-12  1:31   ` Andrew Jeffery
2026-01-12 11:47     ` Krzysztof Kozlowski
2026-01-12 21:21       ` Anirudh Srinivasan
2026-01-13  0:57         ` Andrew Jeffery
2026-01-13 22:28           ` Anirudh Srinivasan
2026-01-15  1:03             ` Andrew Jeffery
2026-01-15  4:38               ` Anirudh Srinivasan
2026-01-11 20:10 ` [PATCH 2/2] ARM: dts: " Anirudh Srinivasan
2026-01-11 21:09   ` Andrew Lunn
2026-01-11 21:26     ` Anirudh Srinivasan
2026-01-12  1:47   ` Andrew Jeffery
2026-01-12  2:35     ` Anirudh Srinivasan
2026-01-12 11:48   ` Krzysztof Kozlowski
2026-01-12 21:16     ` Anirudh Srinivasan

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=20260111201040.162880-1-anirudhsriniv@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=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