From: Chi-Wen Weng <cwweng.linux@gmail.com>
To: David Lechner <dlechner@baylibre.com>,
jic23@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: nuno.sa@analog.com, andy@kernel.org,
linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
cwweng@nuvoton.com
Subject: Re: [PATCH 1/2] dt-bindings: iio: adc: Add Nuvoton MA35D1 EADC
Date: Tue, 30 Jun 2026 12:21:48 +0800 [thread overview]
Message-ID: <5c788984-1bf7-422d-a808-e05112615966@gmail.com> (raw)
In-Reply-To: <2f01a3a0-3698-41e6-8fee-1d2e1629726c@baylibre.com>
Hi David,
Thanks for the clarification.
> We always want the devicetree to be as complete as possible even
> if the drier doesn't use all of the information.
>
> So for trivial/well-known bindings like dmas, we should be able to
> add it now.
Understood. I will add optional DMA properties in v2.
The hardware supports PDMA for EADC transfers, so I will describe it in
the binding even though the initial driver does not use DMA yet.
I plan to add:
dmas:
maxItems: 1
dma-names:
const: rx
These properties will not be required.
> Same reasoning as above, we want the binding to be as complete as
> possible, so we should not omit diff-channels since we know what
> the bindings should look like already.
Understood. I will keep diff-channels in the binding.
I will still limit the DT child channel nodes to the external ADC input
channels 0 to 7, since channel 8 is the fixed internal VBAT input and
does not describe board wiring.
For differential inputs, I will keep diff-channels in the channel child
node schema and restrict it to valid external ADC input channels. I will
also check the hardware-supported differential pair constraints and
encode them in the schema if the hardware only supports fixed pairs.
For v2, I will update the binding to:
- allow up to four interrupt entries for ADINT0 to ADINT3,
- add optional vref-supply,
- add optional dmas and dma-names,
- keep diff-channels,
- limit DT child channel nodes to external channels 0 to 7,
- keep the internal VBAT channel out of the DT child nodes.
Thanks,
Chi-Wen
next prev parent reply other threads:[~2026-06-30 4:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 11:06 [PATCH 0/2] iio: adc: Add Nuvoton MA35D1 EADC support Chi-Wen Weng
2026-06-25 11:06 ` [PATCH 1/2] dt-bindings: iio: adc: Add Nuvoton MA35D1 EADC Chi-Wen Weng
2026-06-25 16:24 ` Conor Dooley
2026-06-27 20:05 ` David Lechner
2026-06-29 7:11 ` Chi-Wen Weng
2026-06-29 15:04 ` David Lechner
2026-06-30 4:21 ` Chi-Wen Weng [this message]
2026-06-25 11:06 ` [PATCH 2/2] iio: adc: Add Nuvoton MA35D1 EADC driver Chi-Wen Weng
2026-06-26 12:54 ` Andy Shevchenko
2026-06-29 7:06 ` Chi-Wen Weng
2026-06-27 20:52 ` David Lechner
2026-06-29 7:32 ` Chi-Wen Weng
2026-06-29 15:09 ` David Lechner
2026-06-30 4:28 ` Chi-Wen Weng
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=5c788984-1bf7-422d-a808-e05112615966@gmail.com \
--to=cwweng.linux@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cwweng@nuvoton.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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