Linux Documentation
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, Lars Randers <lranders@mail.dk>,
	Conor Dooley <conor.dooley@microchip.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Daire McNamara <daire.mcnamara@microchip.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org,
	Valentina.FernandezAlanis@microchip.com
Subject: Re: [RFC] hwmon: add a driver for the temp/voltage sensor on PolarFire SoC
Date: Thu, 28 May 2026 23:34:40 +0100	[thread overview]
Message-ID: <20260528-defog-lasso-84891a72775a@spud> (raw)
In-Reply-To: <b49d4781-0827-4f26-9ca2-ccd177f90237@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]

On Wed, May 27, 2026 at 09:07:20PM -0700, Guenter Roeck wrote:
> On Wed, May 27, 2026 at 10:06:11AM +0100, Conor Dooley wrote:
> > From: Lars Randers <lranders@mail.dk>
> > 
> > Add a driver for the temperature and voltage sensors on PolarFire SoC.
> > The temperature reports how hot the die is, and the voltages are the
> > SoC's 1.05, 1.8 and 2.5 volt rails respectively.
> > 
> > The hardware supports alarms in theory, but there is an unconfirmed
> > erratum that prevents clearing them once triggered, so no support is
> > added.
> > 
> > The hardware measures voltage with 16 bits, of which 1 is a sign bit and
> > the remainder holds the voltage as a fixed point integer value. It's
> > improbable that the hardware will work if the voltages are negative, so
> > the driver ignores the sign bits.
> > 
> > There's no dt support etc here because this is the child of a simple-mfd
> > syscon.
> > 
> > Signed-off-by: Lars Randers <lranders@mail.dk>
> > Co-developed-by: Conor Dooley <conor.dooley@microchip.com>
> > Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> > ---
> > Guenter, there's one question here about the unit that update_interval
> > is in, I didn't see anyone else using us, but I assume that's okay since
> > the resolution that ms would give would be 8 steps only?
> > RFC cos the question is also in the driver as a comment.
> > 
> 
> That just came up in a different context. We'll add a new standard attribute
> update_interval_us. The existing attribute MUST use ms. Everything else
> would be an ABI violation.

Cool. Sounds like Ferdinand is working on that based on the other
thread.

Do you think I should support both update_interval and update_interval_us in
this driver?

If yes, should I do the ms version now and add the us version later once
Ferdinand's work is complete?

Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-05-28 22:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27  9:06 [RFC] hwmon: add a driver for the temp/voltage sensor on PolarFire SoC Conor Dooley
2026-05-28  4:07 ` Guenter Roeck
2026-05-28 22:34   ` Conor Dooley [this message]
2026-06-07 23:56     ` 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=20260528-defog-lasso-84891a72775a@spud \
    --to=conor@kernel.org \
    --cc=Valentina.FernandezAlanis@microchip.com \
    --cc=conor.dooley@microchip.com \
    --cc=corbet@lwn.net \
    --cc=daire.mcnamara@microchip.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@roeck-us.net \
    --cc=lranders@mail.dk \
    --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