From: Ninad Palsule <ninad@linux.ibm.com>
To: corey@minyard.net, Rob Herring <robh@kernel.org>
Cc: minyard@acm.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, ratbert@faraday-tech.com,
openipmi-developer@lists.sourceforge.net, netdev@vger.kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
devicetree@vger.kernel.org, eajames@linux.ibm.com,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 02/10] bindings: ipmi: Add binding for IPMB device intf
Date: Tue, 14 Jan 2025 08:21:08 -0600 [thread overview]
Message-ID: <9404bb02-0dc9-4d44-a07f-4a81faaa63d6@linux.ibm.com> (raw)
In-Reply-To: <Z4Fejhd_qPfuVLiw@mail.minyard.net>
Hello Cprey,
On 1/10/25 11:53, Corey Minyard wrote:
> On Fri, Jan 10, 2025 at 10:07:13AM -0600, Rob Herring wrote:
>> On Wed, Jan 08, 2025 at 10:36:30AM -0600, Ninad Palsule wrote:
>>> Add device tree binding document for the IPMB device interface.
>>> This device is already in use in both driver and .dts files.
>>>
>>> Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
>>> ---
>>> .../devicetree/bindings/ipmi/ipmb-dev.yaml | 44 +++++++++++++++++++
>>> 1 file changed, 44 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/ipmi/ipmb-dev.yaml
>>>
>>> diff --git a/Documentation/devicetree/bindings/ipmi/ipmb-dev.yaml b/Documentation/devicetree/bindings/ipmi/ipmb-dev.yaml
>>> new file mode 100644
>>> index 000000000000..a8f46f1b883e
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/ipmi/ipmb-dev.yaml
>>> @@ -0,0 +1,44 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/ipmi/ipmb-dev.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: IPMB Device
>>> +
>>> +description: IPMB Device interface to receive request and send response
> First, thank you, this does need to be documented.
>
>> IPMB is not defined anywhere.
> Indeed. At least reference the spec, but better do that and provide a
> basic description.
>
>> Which side of the interface does this apply to? How do I know if I have
>> an ipmb-dev?
>>
>> This document needs to stand on its own. Bindings exist in a standalone
>> tree without kernel drivers or docs.
> At least to someone who knows what IPMB is, it's pretty clear that you
> are saying "The i2c device this node is in is on an IPMB bus." However,
> to someone who is not, this is all a foreign language. This definitely
> needs better documentation.
>
> Why do you have a "reg" property? I don't see it referenced in the
> driver. I assume that's the I2C address, but that's going to be the
> same as what's in the containing I2C node. I don't think it's
> necessary.
Sorry forgot to answer this question. We are setting extra values for
reg for I2C slave.
I am not sure how it is used in the driver.
Regards,
Ninad
>
> -corey
>
>>> +
>>> +maintainers:
>>> + - Ninad Palsule <ninad@linux.ibm.com>
>>> +
>>> +properties:
>>> + compatible:
>>> + enum:
>>> + - ipmb-dev
>>> +
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + i2c-protocol:
>>> + description:
>>> + Use I2C block transfer instead of SMBUS block transfer.
>>> + type: boolean
>>> +
>>> +required:
>>> + - compatible
>>> + - reg
>>> +
>>> +additionalProperties: false
>>> +
>>> +examples:
>>> + - |
>>> + i2c {
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + ipmb-dev@10 {
>>> + compatible = "ipmb-dev";
>>> + reg = <0x10>;
>>> + i2c-protocol;
>>> + };
>>> + };
>>> --
>>> 2.43.0
>>>
next prev parent reply other threads:[~2025-01-14 14:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 16:36 [PATCH v3 00/10] DTS updates for system1 BMC Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 01/10] dt-bindings: net: faraday,ftgmac100: Add phys mode Ninad Palsule
2025-01-10 16:02 ` Rob Herring (Arm)
2025-01-13 19:49 ` Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 02/10] bindings: ipmi: Add binding for IPMB device intf Ninad Palsule
2025-01-10 16:07 ` Rob Herring
2025-01-10 17:53 ` Corey Minyard
2025-01-13 19:50 ` Ninad Palsule
2025-01-14 14:21 ` Ninad Palsule [this message]
2025-01-13 19:49 ` Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 03/10] ARM: dts: aspeed: system1: Add IPMB device Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 04/10] ARM: dts: aspeed: system1: Add GPIO line name Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 05/10] ARM: dts: aspeed: system1: Add RGMII support Ninad Palsule
2025-01-08 17:03 ` Andrew Lunn
2025-01-08 18:43 ` Ninad Palsule
2025-01-08 20:13 ` Andrew Lunn
2025-01-08 20:42 ` Ninad Palsule
2025-01-13 19:51 ` Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 06/10] ARM: dts: aspeed: system1: Reduce sgpio speed Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 07/10] ARM: dts: aspeed: system1: Update LED gpio name Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 08/10] ARM: dts: aspeed: system1: Remove VRs max8952 Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 09/10] ARM: dts: aspeed: system1: Mark GPIO line high/low Ninad Palsule
2025-01-08 16:36 ` [PATCH v3 10/10] ARM: dts: aspeed: system1: Disable gpio pull down Ninad Palsule
2025-01-08 22:34 ` [PATCH v3 00/10] DTS updates for system1 BMC Rob Herring (Arm)
2025-01-13 19:52 ` Ninad Palsule
2025-01-14 0:07 ` Rob Herring
2025-01-14 22:09 ` Ninad Palsule
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=9404bb02-0dc9-4d44-a07f-4a81faaa63d6@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=corey@minyard.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=edumazet@google.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=netdev@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=pabeni@redhat.com \
--cc=ratbert@faraday-tech.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;
as well as URLs for NNTP newsgroup(s).