On Tue, Jun 30, 2026 at 08:11:34AM +0200, Krzysztof Kozlowski wrote: > What > > is > > with > > this > > line breaks?
Apologies for the broken formatting in the commit message. I will fix it in the next revision. > No, you do not get second reg property. > > No, you do not get second interrupts property. Understood. These values are not addressable resources of the BMC node itself; rather, they describe how the BMC's LPC engine is exposed on the host LPC bus. I am not sure how they should be represented in DT, since they do not seem to fit the usual semantics of either "reg" or "interrupts". Do you have a preferred way to represent this kind of host-facing LPC configuration in the binding? Thanks, Yu-Che ________________________________ 寄件者: Krzysztof Kozlowski <[email protected]> 已傳送: 星期二, 2026 年 6 月 30 日 下午 02:11 收件者: YC Hsieh <[email protected]>; Corey Minyard <[email protected]>; Rob Herring <[email protected]>; Krzysztof Kozlowski <[email protected]>; Conor Dooley <[email protected]>; Joel Stanley <[email protected]>; Andrew Jeffery <[email protected]> 副本: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> 主旨: Re: [PATCH 3/4] dt-bindings: ipmi: Add optional LPC properties to ASPEED BT devices On 29/06/2026 08:49, Yu-Che Hsieh via B4 Relay wrote: > From: Yu-Che Hsieh <[email protected]> > > Allocating IO and IRQ resources to LPC devices is in-theory an operation > > for the host, however ASPEED systems describe these resources through > > BMC-internal configuration, as already supported by the ASPEED KCS BMC What is with this line breaks? > > binding. > > Add aspeed,lpc-io-reg and aspeed,lpc-interrupts to the ASPEED BT BMC > > binding so firmware can describe the host LPC IO address and SerIRQ > > configuration using the same properties as KCS devices. > > Signed-off-by: Yu-Che Hsieh <[email protected]> > --- > .../bindings/ipmi/aspeed,ast2400-ibt-bmc.yaml | 21 +++++++++++++++++++++ > 1 file changed, 21 insertions(+) > > diff --git > a/Documentation/devicetree/bindings/ipmi/aspeed,ast2400-ibt-bmc.yaml > b/Documentation/devicetree/bindings/ipmi/aspeed,ast2400-ibt-bmc.yaml > index c4f7cdbbe16b..1803c6bbae93 100644 > --- a/Documentation/devicetree/bindings/ipmi/aspeed,ast2400-ibt-bmc.yaml > +++ b/Documentation/devicetree/bindings/ipmi/aspeed,ast2400-ibt-bmc.yaml > @@ -25,6 +25,24 @@ properties: > interrupts: > maxItems: 1 > > + aspeed,lpc-io-reg: > + $ref: /schemas/types.yaml#/definitions/uint32-array > + maxItems: 1 > + description: | > + The host CPU LPC IO address for the BT device. No, you do not get second reg property. > + > + aspeed,lpc-interrupts: > + $ref: /schemas/types.yaml#/definitions/uint32-array > + minItems: 2 > + maxItems: 2 > + description: | > + A 2-cell property expressing the LPC SerIRQ number and the interrupt > + level/sense encoding (specified in the standard fashion). > + > + Note that the generated interrupt is issued from the BMC to the host, > and > + thus the target interrupt controller is not captured by the BMC's > + devicetree. No, you do not get second interrupts property. > Best regards, Krzysztof
_______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
