From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: Marek Vasut <marek.vasut+renesas@mailbox.org>,
linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: renesas: r8a779g3: Add Argon40 fan HAT DTO to Retronix R-Car V4H Sparrow Hawk
Date: Fri, 5 Sep 2025 22:04:34 +0200 [thread overview]
Message-ID: <aLtCUoIPSFfYb-k7@shikoro> (raw)
In-Reply-To: <273d5067-4c9d-4c8c-8633-7f2d7c708216@mailbox.org>
Hi Marek,
> > > + * r8a779g3-sparrow-hawk$ grep -H . /sys/class/hwmon/hwmon?/name
> > > + * /sys/class/hwmon/hwmon0/name:sensor1_thermal
> > > + * /sys/class/hwmon/hwmon1/name:sensor2_thermal
> > > + * /sys/class/hwmon/hwmon2/name:sensor3_thermal
> > > + * /sys/class/hwmon/hwmon3/name:sensor4_thermal
> > > + * /sys/class/hwmon/hwmon4/name:pwmfan
> > > + * ^ ^^^^^^
> >
> > For me, the output looks different, though:
> >
> > /sys/class/hwmon/hwmon0/name:pwmfan
> > /sys/class/hwmon/hwmon1/name:sensor1_thermal
> > /sys/class/hwmon/hwmon2/name:sensor2_thermal
> > /sys/class/hwmon/hwmon3/name:sensor3_thermal
> > /sys/class/hwmon/hwmon4/name:sensor4_thermal
> > /sys/class/hwmon/hwmon5/name:pwmfan
> >
> > hwmon0 is the Argon, hwmon5 the (unpopulated) on board connector.
> >
> > I hope the naming is stable, but in any case, the docs need to be
> > reworked a little, I guess?
>
> The hwmon devices are allocated first come first served, so the list can
> look different for you. You need to look up the fan you want to control, of
> course. Look up by name is simplest, if there are more fans, it might be a
> bit more involved to find the right one.
Exactly. This is why I would suggest to drop the '^^^^^' line from
above. We definitely have two pwmfans with the above dtso. So finding
the right one needs a second look anyhow. And while I think it is quite
likely that the list of hwmon devices will look the same (I don't see a
race condition which would make hwmon0 and hwmon5 swap), I agree we
shouldn't rely on it. I would also think that we then maybe should
change
echo 2 > /sys/class/hwmon/hwmon4/pwm1_enable
to
echo 2 > /sys/class/hwmon/hwmon<X>/pwm1_enable
or something? What do you think? Just suggestions, I am not really
insisting. Well, maybe, about dropping the "^^^^" line ;)
Happy hacking,
Wolfram
next prev parent reply other threads:[~2025-09-05 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 2:00 [PATCH v2] arm64: dts: renesas: r8a779g3: Add Argon40 fan HAT DTO to Retronix R-Car V4H Sparrow Hawk Marek Vasut
2025-09-05 12:30 ` Wolfram Sang
2025-09-05 18:35 ` Marek Vasut
2025-09-05 20:04 ` Wolfram Sang [this message]
2025-09-07 16:14 ` Marek Vasut
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=aLtCUoIPSFfYb-k7@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=marek.vasut@mailbox.org \
--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).