Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: <Ariana.Lazar@microchip.com>
To: <conor@kernel.org>
Cc: <dlechner@baylibre.com>, <linux@roeck-us.net>,
	<linux-hwmon@vger.kernel.org>, <nuno.sa@analog.com>,
	<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<robh@kernel.org>, <jic23@kernel.org>, <andy@kernel.org>,
	<krzk+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
	<conor+dt@kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: adc: add support for PAC1711
Date: Thu, 10 Sep 2026 14:52:02 +0000	[thread overview]
Message-ID: <b706814686dedc5a640970ae83e5e845589f4163.camel@microchip.com> (raw)
In-Reply-To: <aqKauqCxYwo8_nxM@squawk>

Hi Conor,

> > +  The accumulation-source property aims to specify what kind of
> > hardware is
> > +  intended to be used/available for the user. There are two main
> > cases here:
> > +    - the user wants to measure also the current/power consumed
> > before the
> > +      driver insertion (e.g. from the boot to user control) and if
> > this is a
> > +      runtime setting, the hardware accumulator will be reset by
> > the default
> > +      configuration the driver starts with.
> > +    - the driver does not know what type of hardware it's dealing
> > with. In
> > +      case the part is monitoring the charge/discharge current it
> > does not
> > +      make sense in user-space to change the accumulator to
> > calculate energy.
> > +      Same if the hardware is intended to calculate energy it does
> > not make
> > +      sense in user-space to change to Coulomb counter. Changing
> > the setting
> > +      from one mode to another will reset the hardware accumulator
> > inside the
> > +      chip.
> 
> Why is this here, rather than with the property in question or the
> commit message? Anything justifying the property should just be in
> the
> commit message, this doc is user facing and just should explain when
> and
> why to use it.
> > 

Thanks for the review. I put the explanation in the binding description
as suggested in the V2 review here:
https://lore.kernel.org/all/a73ab4e3-520e-4515-adaf-ed5ec644e5f6@baylibre.com/

But if it's better, I will move it in the commit message instead in V4
of this patch series.

Best regards,
Ariana



  reply	other threads:[~2026-09-10 14:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 12:23 [PATCH v3 0/2] Add support for Microchip PAC1711 Power Monitor Ariana Lazar
2026-09-09 12:23 ` [PATCH v3 1/2] dt-bindings: iio: adc: add support for PAC1711 Ariana Lazar
2026-09-09 12:35   ` sashiko-bot
2026-09-10 11:55   ` Conor Dooley
2026-09-10 14:52     ` Ariana.Lazar [this message]
2026-09-12 10:17       ` Conor Dooley
2026-09-09 12:23 ` [PATCH v3 2/2] " Ariana Lazar
2026-09-09 12:35   ` sashiko-bot
2026-09-09 13:38   ` Andy Shevchenko
2026-09-09 14:22   ` Uwe Kleine-König

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=b706814686dedc5a640970ae83e5e845589f4163.camel@microchip.com \
    --to=ariana.lazar@microchip.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=nuno.sa@analog.com \
    --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