Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: sashiko@lists.linux.dev,
	Colin Huang via B4 Relay <devnull+u8813345.gmail.com@kernel.org>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: hwmon: pmbus: add Delta E50SN12051 binding
Date: Thu, 30 Apr 2026 13:20:02 -0700	[thread overview]
Message-ID: <3ca6fa91-e338-48bf-9262-e5dc9e22d228@roeck-us.net> (raw)
In-Reply-To: <20260430065909.981EAC4AF09@smtp.kernel.org>

On 4/29/26 23:59, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [Low] The binding description violates Devicetree principles by describing software instead of hardware. It explicitly states 'The driver supports...', which is an OS-specific software description.
> - [Low] The Devicetree example uses the Linux-specific subsystem name 'hwmon@40' for the node name instead of a generic functional name.
> --
> 
> commit 8f686eaa80cf8986d09fe9ea7dca7debf1c51cb1
> Author: Colin Huang <u8813345@gmail.com>
> 
> dt-bindings: hwmon: pmbus: add Delta E50SN12051 binding
> 
> This commit introduces the devicetree binding schema for the Delta E50SN12051
> PMBus-compliant sensor.
> 
>> diff --git a/Documentation/devicetree/bindings/hwmon/pmbus/delta,e50sn12051.yaml b/Documentation/devicetree/bindings/hwmon/pmbus/delta,e50sn12051.yaml
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/hwmon/pmbus/delta,e50sn12051.yaml
> [ ... ]
>> +description: |
>> +  This binding describes the Delta E50SN12051 PMBus sensor.
>> +  The driver supports reading voltage, current, and temperature
>> +  using the PMBus interface.
> 
> This isn't a bug, but should the description focus purely on the hardware
> rather than mentioning what the driver supports? Devicetree bindings are
> generally expected to be OS-agnostic hardware descriptions.

I am not a devicetree maintainer, but I agree.

Guenter

> 
> [ ... ]
>> +examples:
>> +  - |
>> +    i2c {
>> +        #address-cells = <1>;
>> +        #size-cells = <0>;
>> +
>> +        hwmon@40 {
> 
> Is hwmon@40 the most appropriate node name here? The devicetree specification
> usually recommends using generic names that reflect the function of the
> hardware, such as sensor@40, rather than OS-specific subsystem names like
> hwmon.
> 
>> +            compatible = "delta,e50sn12051";
>> +            reg = <0x40>;
>> +        };
>> +    };
> 


  reply	other threads:[~2026-04-30 20:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30  6:16 [PATCH v3 0/3] add support for Delta E50SN12051 Colin Huang via B4 Relay
2026-04-30  6:16 ` [PATCH v3 1/3] dt-bindings: hwmon: pmbus: add Delta E50SN12051 binding Colin Huang via B4 Relay
2026-04-30  6:59   ` sashiko-bot
2026-04-30 20:20     ` Guenter Roeck [this message]
2026-04-30  6:16 ` [PATCH v3 2/3] Documentation/hwmon: add Delta E50SN12051 documentation Colin Huang via B4 Relay
2026-04-30 20:18   ` Guenter Roeck
2026-04-30  6:16 ` [PATCH v3 3/3] hwmon: (pmbus) add support for Delta E50SN12051 Colin Huang via B4 Relay
2026-04-30 20:17   ` Guenter Roeck

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=3ca6fa91-e338-48bf-9262-e5dc9e22d228@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=devnull+u8813345.gmail.com@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=sashiko@lists.linux.dev \
    /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