public inbox for linux-aspeed@lists.ozlabs.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Anirudh Srinivasan <anirudhsriniv@gmail.com>,
	Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
	devicetree@vger.kernel.org,
		linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, 	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: aspeed: Add Asus IPMI card
Date: Tue, 13 Jan 2026 11:27:28 +1030	[thread overview]
Message-ID: <e97b7a193f8bbfca9ec00037808ad80a5baf9f00.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CAJ13v3RKydFK+sP_Cm-HnQjsOJSDyX_dsGs_Yy564V=Wc7tQFw@mail.gmail.com>

On Mon, 2026-01-12 at 15:21 -0600, Anirudh Srinivasan wrote:
> Hi Krzysztof,
> 
> On Mon, Jan 12, 2026 at 5:47 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> > 
> > > 
> > > It's a bit bike-sheddy, however: the pattern tends to be
> > > ${vendor},${platform}-bmc, but as the platform can't be specified and
> > > the card's function is the BMC itself, I'd go with "asus,ipmi-
> > > expansion-card" (I couldn't immediately find a useful identifier other
> > > than the product name).
> > 
> > This should include some model name or at least soc. What if you have
> > IPMI card for ast2600 and later completely different for ast2700?
> 
> Personally, I was okay with Andrew's suggestion of naming it
> "asus,ipmi-expansion-card" because that's the official product name
> and that exact term works well for online searches.
> 
> This seems like a pretty niche product Asus announced 4 years ago and
> made in very low volumes. I'm not sure if they'll make a new one with
> an ast2700, given how the modern trend is to have BMCs on
> motherboards. What do you think about the naming Andrew?

I agree that the product seems niche. There's practically nothing on
their website on the marketing side - from searching around the details
are pretty much limited to the support pages. I can't really speak to
future stuff like an AST2700-based design though, who knows.

A couple of numbers turned up that might be helpful:

   1. The Quick Start Guide[1] seems to use "E21524", which is also
      used by some random blog[2] to identify it. 
   2. There's "R1.04" on the silkscreen. 

Perhaps we could incorporate either of those?

 * asus,e21524-ipmi-expansion-card
 * asus,ipmi-expansion-card-r1-04

However, they're not without some risk:

   1. It's hard to tell whether E21524 is properly representative
   2. R1.04 may also problematic as an AST2700-based card will likely
      restart the numbering and risk a collision

Otherwise, I guess there's:

 * asus,ipmi-expansion-card-ast2600

Andrew

[1]: https://www.asus.com/us/supportonly/ipmi%20expansion%20card/helpdesk_manual/
[2]: https://blog.liaosirui.com/%E7%B3%BB%E7%BB%9F%E8%BF%90%E7%BB%B4/A.%E6%9C%8D%E5%8A%A1%E5%99%A8/%E5%B9%B3%E5%8F%B0%E7%AE%A1%E7%90%86/BMC%E5%BA%95%E6%9D%BF%E7%AE%A1%E7%90%86%E6%8E%A7%E5%88%B6%E5%99%A8/IPMI%E8%BF%9C%E7%A8%8B%E7%AE%A1%E7%90%86%E5%8D%A1.html


  reply	other threads:[~2026-01-13  0:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-11 20:10 [PATCH 0/2] Add device tree for Asus IPMI Card Anirudh Srinivasan
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 [this message]
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=e97b7a193f8bbfca9ec00037808ad80a5baf9f00.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=anirudhsriniv@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@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