From: Guenter Roeck <linux@roeck-us.net>
To: "Uwe Kleine-König" <ukleinek@kernel.org>,
"Petar Stepanovic" <pstepanovic@axiado.com>
Cc: Akhila Kavi <akavi@axiado.com>,
Prasad Bolisetty <pbolisetty@axiado.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Harshit Shah <hshah@axiado.com>, Tzu-Hao Wei <twei@axiado.com>,
Karthikeyan Mitran <kmitran@axiado.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] hwmon: add Axiado AX3000 and AX3005 PWM fan controller driver
Date: Thu, 6 Aug 2026 08:34:58 -0700 [thread overview]
Message-ID: <d027eec5-ca83-4aba-a3c1-4724c77df0dc@roeck-us.net> (raw)
In-Reply-To: <anRaB--HAHoWFkDo@monoceros>
On 8/6/26 03:04, Uwe Kleine-König wrote:
> If there is a hwmon lock that serializes calls to hwmon_ops::read and
> hwmon_ops::write, .pwm_lock isn't needed. (Unless I miss something,
> please double check. Also I'm unsure if there is such a hwmon
> serialization.)
>
In hwmon_attr_show(), hwmon_attr_show_string(), and hwmon_attr_store():
guard(mutex)(&hwdev->lock);
Guenter
prev parent reply other threads:[~2026-08-06 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 9:01 [PATCH 0/2] hwmon: add Axiado AX3000 and AX3005 PWM fan support Petar Stepanovic
2026-08-06 9:01 ` [PATCH 1/2] dt-bindings: hwmon: add Axiado AX3000 and AX3005 PWM fan controller Petar Stepanovic
2026-08-06 10:41 ` Rob Herring (Arm)
2026-08-06 13:16 ` Rob Herring
2026-08-06 9:01 ` [PATCH 2/2] hwmon: add Axiado AX3000 and AX3005 PWM fan controller driver Petar Stepanovic
2026-08-06 10:04 ` Uwe Kleine-König
2026-08-06 15:34 ` 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=d027eec5-ca83-4aba-a3c1-4724c77df0dc@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akavi@axiado.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=hshah@axiado.com \
--cc=kmitran@axiado.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pbolisetty@axiado.com \
--cc=pstepanovic@axiado.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=twei@axiado.com \
--cc=ukleinek@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