From: Krzysztof Kozlowski <krzk@kernel.org>
To: YC Hsieh <yc_hsieh@aspeedtech.com>,
Corey Minyard <corey@minyard.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: "openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>
Subject: Re: 回覆: [PATCH 3/4] dt-bindings: ipmi: Add optional LPC properties to ASPEED BT devices
Date: Mon, 13 Jul 2026 07:56:06 +0200 [thread overview]
Message-ID: <31df2c13-9c31-4a78-975f-b0152ad3356d@kernel.org> (raw)
In-Reply-To: <TY0PR06MB6855F4F499246CD5C44DB23893FA2@TY0PR06MB6855.apcprd06.prod.outlook.com>
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
next prev parent reply other threads:[~2026-07-13 5:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 6:48 [PATCH 0/4] ipmi: bt-bmc: Add configurable LPC host interface Yu-Che Hsieh via B4 Relay
2026-06-29 6:48 ` [PATCH 1/4] ipmi: bt-bmc: Use bitfield helpers for register definitions Yu-Che Hsieh via B4 Relay
2026-06-29 6:48 ` [PATCH 2/4] ipmi: bt-bmc: Track open state per device Yu-Che Hsieh via B4 Relay
2026-06-29 7:04 ` sashiko-bot
2026-06-29 6:49 ` [PATCH 3/4] dt-bindings: ipmi: Add optional LPC properties to ASPEED BT devices Yu-Che Hsieh via B4 Relay
2026-06-29 15:26 ` Conor Dooley
2026-06-30 2:24 ` YC Hsieh
2026-06-30 17:15 ` Conor Dooley
2026-06-30 6:11 ` Krzysztof Kozlowski
2026-06-30 17:51 ` Rob Herring
[not found] ` <TY0PR06MB6855F4F499246CD5C44DB23893FA2@TY0PR06MB6855.apcprd06.prod.outlook.com>
2026-07-13 5:56 ` Krzysztof Kozlowski [this message]
2026-07-13 7:09 ` 回覆: 回覆: " YC Hsieh
2026-06-29 6:49 ` [PATCH 4/4] ipmi: bt-bmc: Read LPC address and SerIRQ from device tree Yu-Che Hsieh via B4 Relay
2026-06-29 7:16 ` sashiko-bot
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=31df2c13-9c31-4a78-975f-b0152ad3356d@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=corey@minyard.net \
--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=openipmi-developer@lists.sourceforge.net \
--cc=robh@kernel.org \
--cc=yc_hsieh@aspeedtech.com \
/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