From: Jonathan Cameron <jic23@kernel.org>
To: Roman Vivchar via B4 Relay <devnull+rva333.protonmail.com@kernel.org>
Cc: rva333@protonmail.com, "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Chen-Yu Tsai" <wenst@chromium.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 0/3] iio: adc: mt6359-auxadc: various fixes
Date: Sat, 21 Nov 2026 23:56:03 +0000 [thread overview]
Message-ID: <20261121235603.41ce1ec4@jic23-hlaptop> (raw)
In-Reply-To: <20261117-6768-6358-fixes-v2-0-1ffc3c2f3c80@protonmail.com>
On Tue, 17 Nov 2026 19:56:31 +0200
Roman Vivchar via B4 Relay <devnull+rva333.protonmail.com@kernel.org> wrote:
> This patch series fixes various bugs in the mt6359 auxadc driver. For
> some reason, the driver had channel types for temperature or resistance,
> while the ADC can report only voltage. There were also issues with
> battery channel ready bit masking and scale calculation.
>
> Changes were verified on the mt6358 (mt6768 platform). Compile-tested
> only for others.
>
> Signed-off-by: Roman Vivchar <rva333@protonmail.com>
Hi Roman,
The series looks fine to me, but as we have fairly active folk
who care about this driver (or at least did recently) I'm going
to wait a while for reviews to come in.
Thanks,
Jonathan
> ---
> Changes in v2:
> - Clarify bit number in the patch 2 commit message (Jonathan)
> - Link to v1: https://patch.msgid.link/20261103-6768-6358-fixes-v1-0-2a868a33152b@protonmail.com
>
> ---
> Roman Vivchar (3):
> iio: adc: mt6359-auxadc: correct channel types to IIO_VOLTAGE
> iio: adc: mt6359-auxadc: mask conversion ready bit in mt6358_read_imp
> iio: adc: mt6359-auxadc: fix scale calculation
>
> drivers/iio/adc/mt6359-auxadc.c | 88 ++++++++++++++++++++---------------------
> 1 file changed, 42 insertions(+), 46 deletions(-)
> ---
> base-commit: 7649ba73f9e7e1e04d0b46213e39c79ae09dd55c
> change-id: 20261103-6768-6358-fixes-fcdc79afae11
>
> Best regards,
> --
> rva3 <rva333@protonmail.com>
>
>
prev parent reply other threads:[~2026-11-21 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 17:56 [PATCH v2 0/3] iio: adc: mt6359-auxadc: various fixes Roman Vivchar via B4 Relay
2026-11-17 17:56 ` [PATCH v2 1/3] iio: adc: mt6359-auxadc: correct channel types to IIO_VOLTAGE Roman Vivchar via B4 Relay
2026-11-17 17:56 ` [PATCH v2 2/3] iio: adc: mt6359-auxadc: mask conversion ready bit in mt6358_read_imp Roman Vivchar via B4 Relay
2026-11-17 17:56 ` [PATCH v2 3/3] iio: adc: mt6359-auxadc: fix scale calculation Roman Vivchar via B4 Relay
2026-11-21 23:56 ` Jonathan Cameron [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=20261121235603.41ce1ec4@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devnull+rva333.protonmail.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=nuno.sa@analog.com \
--cc=rva333@protonmail.com \
--cc=wenst@chromium.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