public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Flaviu Nistor" <flaviu.nistor@gmail.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] docs: hwmon: (lm75) Add section for sysfs interface
Date: Fri, 17 Apr 2026 05:49:25 +0000	[thread overview]
Message-ID: <20260417054926.16CE3C19425@smtp.kernel.org> (raw)
In-Reply-To: <20260417054511.5432-1-flaviu.nistor@gmail.com>

Sashiko AI review found 3 potential issue(s):
- [Low] Missing `temp1_alarm` sysfs attribute in the documentation.
- [Low] Inaccurate permissions documented for `update_interval`.
- [Low] Extraneous trailing colons in sysfs attribute names.
--

commit c1dce0b929df71ecb8a78067d9800bb8e1c93d8f
Author: Flaviu Nistor <flaviu.nistor@gmail.com>

docs: hwmon: (lm75) Add section for sysfs interface

This commit adds a new section to the lm75 documentation detailing the
sysfs attributes, their permissions, and brief descriptions.

> diff --git a/Documentation/hwmon/lm75.rst b/Documentation/hwmon/lm75.rst
> index 4269da04508ef..288cf8485ea61 100644
> --- a/Documentation/hwmon/lm75.rst
> +++ b/Documentation/hwmon/lm75.rst

[ ... ]

> +sysfs-Interface
> +---------------
> +
> +The following list includes the sysfs attributes that the driver provides, their
> +permissions and a short description:
> +
> +=============================== ======= ===========================================
> +Name                            Perm    Description
> +=============================== ======= ===========================================
> +temp1_input:                    RO      Temperature input
> +temp1_label:                    RO      Descriptive name for the sensor
> +temp1_max:                      RW      Maximum temperature
> +temp1_max_hyst:                 RW      Maximum hysteresis temperature

This isn't a bug, but should the trailing colons on these attribute names
be removed? Sysfs filenames do not contain colons, and the update_interval
attribute below correctly omits it.

> +update_interval                 RW      Update conversions interval in milliseconds

Is update_interval always read/write? Looking at lm75_is_visible() in the
driver, it appears to only grant write permissions (0644) if the device
supports multiple sample times. For chips with a single fixed sample time,
the attribute is restricted to read-only (0444). Could the documentation
reflect this conditional permission?

> +=============================== ======= ===========================================

Should temp1_alarm be included in this list? The driver code exposes
HWMON_T_ALARM as read-only for chips that support it (such as the as6200
and tmp112), so the current documentation seems slightly incomplete without
it.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260417054511.5432-1-flaviu.nistor@gmail.com?part=1

      reply	other threads:[~2026-04-17  5:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  5:45 [PATCH] docs: hwmon: (lm75) Add section for sysfs interface Flaviu Nistor
2026-04-17  5:49 ` sashiko-bot [this message]

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=20260417054926.16CE3C19425@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=flaviu.nistor@gmail.com \
    --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