Re: 回覆: [PATCH 3/4] dt-bindings: ipmi: Add optional LPC properties to ASPEED BT devices
Krzysztof Kozlowski <[email protected]> Mon, 13 Jul 2026 07:56:06 +0200
| Newsgroups | org.ozlabs.lists.linux-aspeed,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 13/07/2026 07:34, YC Hsieh wrote: > 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? I don't understand what you are referring to, entire context is gone because essentially you top-posted. Best regards, Krzysztof