From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Dawid Glazik <dawid.glazik@linux.intel.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
maciej.lawniczak@intel.com, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v5 2/3] ARM: dts: aspeed: Add Intel AVCRP BMC
Date: Wed, 11 Nov 2026 12:19:46 +1030 [thread overview]
Message-ID: <a92395610d27fc0f97af3b27b150de61583c2197.camel@codeconstruct.com.au> (raw)
In-Reply-To: <599f1b31-f175-47df-b074-1915688eb390@linux.intel.com>
On Tue, 2026-11-10 at 17:42 +0100, Dawid Glazik wrote:
> On 11/10/2026 6:53 AM, Andrew Jeffery wrote:
> > On Mon, 2026-11-09 at 18:41 +0100, Dawid Glazik wrote:
> > > AVCRP is an Intel x86 server platform equipped with an ASPEED
> > > AST2600 BMC. The BMC is used for out-of-band management, platform
> > > monitoring, and system control.
> >
> > It's probably my fault to some degree for not providing a better
> > explanation of what I was after on v4, and for merging changes from
> > others in the past that were pretty lax on the description, but what I
> > was hoping for was something more like e.g:
> >
> > - f28674fab34f ("ARM: dts: aspeed: Add NVIDIA MSX4 HPM"), or
> > - bc83b7353d2b ("ARM: dts: aspeed: Add Facebook Anacapa platform")
> >
> > Are there more details you can provide? If there are, I'm fine if you
> > reply here with them, and if there are no further concerns I can update
> > the commit message while applying the patches.
> >
> > This also applies to the JNCRP patch that follows.
> >
> > Andrew
>
> Hi Andrew,
>
> Thanks, that helps. I also found one more issue in v5 (uart-routing
> issue), so I'll send a v6 with the fuller descriptions below
> instead of having you edit them. Please hold off applying v5.
>
> AVCRP is an Intel x86 server platform. The BMC is an ASPEED
> AST2600-based RunBMC module on the platform's DC-SCM. It supports the
> platform's out-of-band management and exposes board management I/O such
> as the system UARTs, status LEDs and control buttons, while integrating
> with the host's telemetry and management infrastructure.
Can you talk more about the division of duties around RunBMC vs DC-SCM?
Can you describe how components of each spec are used in the design?
What's the motivation for designing this module vs using another? Are
there any specific target platforms intended for it? If there are, then
some further details about those would be nice. If not, no problem.
>
> JNCRP is an Intel x86 server platform managed by an ASPEED AST2600 BMC.
> The BMC is the platform management controller for the host system and
> supports platform power and reset control, while participating in
> out-of-band monitoring and reporting for host faults during bring-up and
> normal operation.
You don't mention RunBMC/DC-SCM here, so I assume the BMC is integrated
into the platform? Can you describe the purpose of the platform itself
(beyond the purpose of the BMC, which tends to be the same for most
platforms)?
Cheers,
Andrew
next prev parent reply other threads:[~2026-11-11 1:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 17:41 [PATCH v5 0/3] arm: dts: aspeed: Add Intel AVCRP and JNCRP BMC platforms Dawid Glazik
2026-11-09 17:41 ` [PATCH v5 1/3] dt-bindings: arm: aspeed: Add Intel AVCRP and JNCRP boards Dawid Glazik
2026-11-09 17:41 ` [PATCH v5 2/3] ARM: dts: aspeed: Add Intel AVCRP BMC Dawid Glazik
2026-11-10 5:53 ` Andrew Jeffery
2026-11-10 16:42 ` Dawid Glazik
2026-11-11 1:49 ` Andrew Jeffery [this message]
2026-11-09 17:41 ` [PATCH v5 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=a92395610d27fc0f97af3b27b150de61583c2197.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=dawid.glazik@linux.intel.com \
--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®