From: Guenter Roeck <linux@roeck-us.net>
To: Chen-Shi-Hong <eric039eric@gmail.com>
Cc: corbet@lwn.net, skhan@linuxfoundation.org,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Documentation: hwmon: lm75: document sysfs interface
Date: Sat, 16 May 2026 10:43:51 -0700 [thread overview]
Message-ID: <9882b9cf-7b10-411d-be41-2da298500db2@roeck-us.net> (raw)
In-Reply-To: <20260516170728.2066-1-eric039eric@gmail.com>
On Sun, May 17, 2026 at 01:07:27AM +0800, Chen-Shi-Hong wrote:
> Document the sysfs attributes supported by the lm75 driver.
>
> The driver exposes temp1_input, temp1_max, temp1_max_hyst, and the
> standard update_interval attribute. Some chips also expose temp1_alarm,
> and temp1_label is available if a label is provided for the device.
>
> Add a sysfs-Interface section to Documentation/hwmon/lm75.rst to
> describe the supported attributes and clarify that temp1_alarm,
> temp1_label, and the write permissions of update_interval depend on the
> chip.
>
> Signed-off-by: Chen-Shi-Hong <eric039eric@gmail.com>
When I tried to apply this patch, I noticed that a similar patch is
already queued in hwmon-next. Sorry that I didn't realize this earlier.
Guenter
> ---
> Changes in v2:
> - Document temp1_label as conditionally available when a device label is
> provided.
>
> Changes in v3:
> - Add changelog requested during review.
>
> Documentation/hwmon/lm75.rst | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/Documentation/hwmon/lm75.rst b/Documentation/hwmon/lm75.rst
> index 4269da04508e..fa8ddcaa0c2b 100644
> --- a/Documentation/hwmon/lm75.rst
> +++ b/Documentation/hwmon/lm75.rst
> @@ -181,3 +181,28 @@ is supported by this driver, other specific enhancements are not.
>
> The LM77 is not supported, contrary to what we pretended for a long time.
> Both chips are simply not compatible, value encoding differs.
> +
> +sysfs-Interface
> +---------------
> +
> +================ ============================================
> +temp1_input temperature input
> +temp1_max maximum temperature
> +temp1_max_hyst maximum temperature hysteresis
> +================ ============================================
> +
> +If a label is provided for the device, the following attribute is also
> +available:
> +
> +================ ============================================
> +temp1_label temperature channel label
> +================ ============================================
> +
> +If supported by the chip, the following attribute is also available:
> +
> +================ ============================================
> +temp1_alarm temperature alarm
> +================ ============================================
> +
> +The standard update_interval attribute is also supported. Its write
> +permissions depend on the chip.
prev parent reply other threads:[~2026-05-16 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260516160823.1461-1-eric039eric@gmail.com>
2026-05-16 16:40 ` [PATCH v2] " Chen-Shi-Hong
2026-05-16 16:48 ` Guenter Roeck
2026-05-16 17:07 ` [PATCH v3] " Chen-Shi-Hong
2026-05-16 17:43 ` Guenter Roeck [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=9882b9cf-7b10-411d-be41-2da298500db2@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=eric039eric@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®