From: David Lechner <dlechner@baylibre.com>
To: "Roman Vivchar" <rva333@protonmail.com>,
"Nuno Sá" <noname.nuno@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Lee Jones" <lee@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
"Ben Grisdale" <bengris32@protonmail.ch>
Subject: Re: [PATCH 2/4] iio: adc: mt6323-auxadc: add mt6323 PMIC AUXADC driver
Date: Sat, 13 Jun 2026 11:42:11 -0500 [thread overview]
Message-ID: <8ddb4c1e-d105-49be-a6e0-30c220af98c3@baylibre.com> (raw)
In-Reply-To: <RRvh9UBBrqdfKoCLaqgfcQ06UY-BSM2hQ0F6F1YkdB2k2RXYMQmlCG4phXk72oGY03t1g1kDI4z-SDeKlYkUv84-AjNLaWK7tDQlpEFQVKk=@protonmail.com>
On 6/3/26 6:24 AM, Roman Vivchar wrote:
> Hi Nuno,
>
> On Tuesday, June 2nd, 2026 at 7:42 PM, Nuno Sá <noname.nuno@gmail.com> wrote:
>
>> On Tue, 2026-06-02 at 15:46 +0300, Roman Vivchar via B4 Relay wrote:
>
> ...
>
>>>
>>> +MEDIATEK MT6323 PMIC AUXADC DRIVER
>>> +M: Roman Vivchar <rva333@protonmail.com>
>>> +L: linux-iio@vger.kernel.org
>>> +L: linux-mediatek@lists.infradead.org (moderated for non-subscribers)
>>> +S: Maintained
>>> +F: drivers/iio/adc/mt6323-auxadc.c
>>> +F: include/dt-bindings/iio/adc/mediatek,mt6323-auxadc.h
>>
>> The above file was not added in this patch
>
> The header file is added in patch 1 (dt-bindings). Following Krzysztof's
> feedback on the previous version, I squashed the MAINTAINERS into this patch.
> Please let me know if I misunderstood anything.
Usually, we want the MAINTAINERS entry in the same patch that
the file was added. It is fine to include MAINTAINERS changes
in the dt-bindings patch.
>>> + case IIO_CHAN_INFO_RAW:
>>> + scoped_guard(mutex, &auxadc->lock) {
We can avoid extra indent by making this:
case IIO_CHAN_INFO_RAW: {
guard(mutex)(&auxadc->lock);
...
return IIO_VAL_INT;
}
>>> + ret = mt6323_auxadc_prepare_channel(auxadc);
>>> + if (ret)
>>> + return ret;
>>> +
>>> + ret = mt6323_auxadc_request(auxadc, chan->channel);
>>> + if (ret)
>>> + return ret;
>>> +
>>> + /* Hardware limitation: the AUXADC needs a delay to become
>>> ready. */
>>> + fsleep(300);
>>> +
>>> + ret = mt6323_auxadc_read(auxadc, chan, val);
>>> + if (ret)
>>> + return ret;
>>
>> Could be return mt6323_auxadc_read(...)
>
> The mt6323_auxadc_read returns 0, while IIO expects IIO_VAL_INT (defined as 1).
> Should the mt6323_auxadc_read function return 1 for success?
mt6323_auxadc_read() would need to return IIO_VAL_INT.
next prev parent reply other threads:[~2026-06-13 16:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 12:46 [PATCH 0/4] AUXADC driver for the MediaTek mt6323 PMIC Roman Vivchar via B4 Relay
2026-06-02 12:46 ` [PATCH 1/4] dt-bindings: iio: adc: mediatek,mt6359-auxadc: add mt6323 PMIC AUXADC Roman Vivchar via B4 Relay
2026-06-02 16:21 ` Conor Dooley
2026-06-02 12:46 ` [PATCH 2/4] iio: adc: mt6323-auxadc: add mt6323 PMIC AUXADC driver Roman Vivchar via B4 Relay
2026-06-02 16:43 ` Nuno Sá
2026-06-03 11:24 ` Roman Vivchar
2026-06-13 16:42 ` David Lechner [this message]
2026-06-03 1:11 ` Sanjay Chitroda
2026-06-03 5:51 ` Andy Shevchenko
2026-06-03 13:41 ` Jonathan Cameron
2026-06-02 12:46 ` [PATCH 3/4] mfd: mt6397-core: add mt6323 AUXADC support Roman Vivchar via B4 Relay
2026-06-11 16:37 ` Lee Jones
2026-06-15 23:10 ` Roman Vivchar
2026-06-16 7:18 ` Andy Shevchenko
2026-06-02 12:46 ` [PATCH 4/4] ARM: dts: mediatek: mt6323: add " Roman Vivchar via B4 Relay
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=8ddb4c1e-d105-49be-a6e0-30c220af98c3@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bengris32@protonmail.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--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=noname.nuno@gmail.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=rva333@protonmail.com \
/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
all inboxes | Powered by JetHome®