From: sashiko-bot@kernel.org
To: "Ariana Lazar" <ariana.lazar@microchip.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v5 2/5] iio: core: add IIO_CHARGE channel type
Date: Tue, 03 Nov 2026 14:41:18 +0000 [thread overview]
Message-ID: <sashiko-outbox-195466@kernel.org> (raw)
In-Reply-To: <20261103-pac1711-v5-2-71c20101a52e@microchip.com>
> Add a new channel type for Coulomb counters, which accumulate current
> measurements over time. The sysfs attribute is in_chargeY_raw and after
> applying in_chargeY_scale, the value exposed is in milliCoulombs,
> following the SI convention used by the IIO subsystem.
>
> This new channel type will first be used by the pac1711 driver to report
> Coulomb counter measurements.
>
> Signed-off-by: Ariana Lazar <ariana.lazar@microchip.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103-pac1711-v5-0-71c20101a52e@microchip.com?part=2
next prev parent reply other threads:[~2026-11-03 14:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 14:37 [PATCH v5 0/5] Add support for Microchip PAC1711 Power Monitor Ariana Lazar
2026-11-03 14:37 ` [PATCH v5 1/5] unaligned: introduce be56 unaligned accessors Ariana Lazar
2026-11-03 14:41 ` sashiko-bot
2026-11-04 7:54 ` Joshua Crofts
2026-11-03 14:37 ` [PATCH v5 2/5] iio: core: add IIO_CHARGE channel type Ariana Lazar
2026-11-03 14:41 ` sashiko-bot [this message]
2026-11-03 16:13 ` Andy Shevchenko
2026-11-03 14:37 ` [PATCH v5 3/5] iio: core: add iio_fill_val_int_64() helper Ariana Lazar
2026-11-03 14:42 ` sashiko-bot
2026-11-03 16:14 ` Andy Shevchenko
2026-11-03 14:37 ` [PATCH v5 4/5] dt-bindings: iio: adc: add support for PAC1711 Ariana Lazar
2026-11-03 14:43 ` sashiko-bot
2026-11-03 14:37 ` [PATCH v5 5/5] " Ariana Lazar
2026-11-03 14:59 ` sashiko-bot
2026-11-03 16:40 ` Andy Shevchenko
2026-11-04 1:36 ` Jonathan Cameron
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=sashiko-outbox-195466@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ariana.lazar@microchip.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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