From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chi-Wen Weng <cwweng.linux@gmail.com>
Cc: jic23@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, dlechner@baylibre.com, 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 v3 1/2] dt-bindings: iio: adc: Add Nuvoton MA35D1 EADC
Date: Mon, 2 Nov 2026 11:03:15 +0100 [thread overview]
Message-ID: <20261102-bald-mysterious-alpaca-13b8fa@quoll> (raw)
In-Reply-To: <20261030031501.130290-2-cwweng.linux@gmail.com>
On Fri, Oct 30, 2026 at 11:15:00AM +0800, Chi-Wen Weng wrote:
> From: Chi-Wen Weng <cwweng@nuvoton.com>
>
> Add a devicetree binding for the Enhanced Analog-to-Digital Converter
> (EADC) found on Nuvoton MA35D1 SoCs.
>
> The controller provides eight external analog inputs which can be used
> as single-ended channels or as four fixed differential pairs: 0-4,
> 1-5, 2-6 and 3-7.
>
> Describe the four hardware interrupt outputs, ADINT0 through ADINT3.
> ADINT0 through ADINT2 are associated with the corresponding conversion
> interrupt flags, while ADINT3 is shared by the ADIF3 conversion
> interrupt and the ADCMPF0 through ADCMPF3 result-compare interrupt
> sources.
>
> Also describe the functional clock, optional reset, optional external
> reference supply and optional DMA request.
Don't repeat the patch contents.
>
> Expose the controller as an IIO channel provider through the
> DT #io-channel-cells property. The cell identifies the logical EADC
> channel selected by the reg value of the corresponding channel child
> node.
>
> Restrict the channel binding to features supported by the MA35D1 EADC
> hardware and use the common single-channel representation for
> single-ended inputs.
And here even more.
>
> Signed-off-by: Chi-Wen Weng <cwweng@nuvoton.com>
> ---
> .../bindings/iio/adc/nuvoton,ma35d1-eadc.yaml | 175 ++++++++++++++++++
> 1 file changed, 175 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/adc/nuvoton,ma35d1-eadc.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/nuvoton,ma35d1-eadc.yaml b/Documentation/devicetree/bindings/iio/adc/nuvoton,ma35d1-eadc.yaml
> new file mode 100644
> index 000000000000..97144a8eeb5c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/nuvoton,ma35d1-eadc.yaml
> @@ -0,0 +1,175 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/adc/nuvoton,ma35d1-eadc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Nuvoton MA35D1 Enhanced Analog-to-Digital Converter
> +
> +maintainers:
> + - Chi-Wen Weng <cwweng@nuvoton.com>
> +
> +description: |
> + The Nuvoton MA35D1 Enhanced Analog-to-Digital Converter (EADC) is a
> + 12-bit successive approximation converter with eight external analog
> + inputs and one internally connected VBAT input.
> +
> + The external inputs can be used as eight single-ended channels or as
> + four fixed differential pairs: 0-4, 1-5, 2-6 and 3-7. The internally
> + connected VBAT input is not described by a channel child node.
> +
> + The controller provides four interrupt outputs, ADINT0 through ADINT3.
> + ADINT0, ADINT1 and ADINT2 are generated by the corresponding ADIF0,
> + ADIF1 and ADIF2 conversion interrupt flags. ADINT3 is shared by the
> + ADIF3 conversion interrupt flag and the ADCMPF0 through ADCMPF3 result
> + compare flags.
> +
> +properties:
> + compatible:
> + const: nuvoton,ma35d1-eadc
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + items:
> + - description: ADINT0 conversion interrupt output generated by ADIF0
> + - description: ADINT1 conversion interrupt output generated by ADIF1
> + - description: ADINT2 conversion interrupt output generated by ADIF2
> + - description: >
Drop >
> + ADINT3 shared interrupt output generated by ADIF3 or by the
> + ADCMPF0 through ADCMPF3 result compare flags
> +
> + interrupt-names:
> + items:
> + - const: adint0
> + - const: adint1
> + - const: adint2
> + - const: adint3
"int" is redundant, so honestly names should rather go away completely.
> +
> + clocks:
> + maxItems: 1
> +
> + resets:
> + maxItems: 1
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-02 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 3:14 [PATCH v3 0/2] iio: adc: Add Nuvoton MA35D1 EADC support Chi-Wen Weng
2026-10-30 3:15 ` [PATCH v3 1/2] dt-bindings: iio: adc: Add Nuvoton MA35D1 EADC Chi-Wen Weng
2026-11-01 0:19 ` Jonathan Cameron
2026-11-02 2:38 ` Chi-Wen Weng
2026-11-02 10:03 ` Krzysztof Kozlowski [this message]
2026-11-02 10:20 ` Chi-Wen Weng
2026-11-04 11:08 ` Krzysztof Kozlowski
2026-10-30 3:15 ` [PATCH v3 2/2] iio: adc: Add Nuvoton MA35D1 EADC driver Chi-Wen Weng
2026-11-01 0:53 ` Jonathan Cameron
2026-11-02 4:22 ` Chi-Wen Weng
2026-11-02 22:17 ` Jonathan Cameron
2026-11-03 11:00 ` Andy Shevchenko
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=20261102-bald-mysterious-alpaca-13b8fa@quoll \
--to=krzk@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cwweng.linux@gmail.com \
--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
all inboxes | Powered by JetHome®