[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <16281e86d3cf5c97fcb59e73472dc8edca50c484.camel@codeconstruct.com.au>
Date: Mon, 22 Sep 2025 13:16:48 +0930
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: Leo Wang <leo.jt.wang@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski
<krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Joel Stanley
<joel@....id.au>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
george.kw.lee@...-foxconn.com, bruce.jy.hung@...-foxconn.com,
leo.jt.wang@...-foxconn.com
Subject: Re: [PATCH] ARM: dts: aspeed: clemente: add MCTP over I2C support
Hi Leo,
On Thu, 2025-09-18 at 17:43 +0800, Leo Wang wrote:
> Enable MCTP communication on the Meta Clemente BMC board:
>
> - Add an MCTP I2C controller node at address 0x10 on I2C0
> - Mark selected I2C mux channels as MCTP controllers
> - Remove unused "i2c-mux-idle-disconnect" properties
>
> This allows MCTP devices to be discovered and used for
> management communication on the Clemente platform.
This description covers details we can see in the patch itself. Can you
please rather describe the motivation and any related considerations,
e.g. answer:
* What devices will you be managing via MCTP?
* How do they affect the function of the platform?
- Alternatively, how does _not_ having the MCTP capability to manage
them impact the function of the platform?
The general advice provided here might be helpful:
https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
Andrew
Powered by blists - more mailing lists