From: Conor Dooley <conor@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"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>,
"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: iio: adc: max1238: Add #io-channel-cells property
Date: Tue, 19 Aug 2025 19:12:10 +0100 [thread overview]
Message-ID: <20250819-astronomy-gladiator-21823768723a@spud> (raw)
In-Reply-To: <20250818200014.3700738-1-Frank.Li@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]
On Mon, Aug 18, 2025 at 04:00:13PM -0400, Frank Li wrote:
> Add #io-channel-cells property because it is multi-channel ADC.
As far as I understand it, that's not a correct statement. A single
channel ADC can have the property, but it would be set to 0 just as a
single clock provider has #clock-cells of 0.
I did check the devices and they do all appear to be multichannel (not
just the 1238) so the change you're making here looks correct, unless
some of them would actually require 2 cells for some reason - but you
should really state that in your commit message when there's about 30
compatibles so that I don't have to check them.
With an accurate commit message,
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Maybe Jonathan is willing to do that since it's just adding "of 1" to
the first sentence.
>
> Fix below CHECK_DTBS warnings:
> arch/arm/boot/dts/nxp/ls/ls1021a-iot.dtb: adc@35 (maxim,max1239): '#io-channel-cells' does not match any of the regexes: '^pinctrl-[0-9]+$'
> from schema $id: http://devicetree.org/schemas/iio/adc/maxim,max1238.yaml#
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> Documentation/devicetree/bindings/iio/adc/maxim,max1238.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/maxim,max1238.yaml b/Documentation/devicetree/bindings/iio/adc/maxim,max1238.yaml
> index 60d7b34e3286f..ae3c89393f1a3 100644
> --- a/Documentation/devicetree/bindings/iio/adc/maxim,max1238.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/maxim,max1238.yaml
> @@ -53,6 +53,9 @@ properties:
> reg:
> maxItems: 1
>
> + "#io-channel-cells":
> + const: 1
> +
> vcc-supply: true
> vref-supply:
> description: Optional external reference. If not supplied, internal
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-19 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 20:00 [PATCH 1/1] dt-bindings: iio: adc: max1238: Add #io-channel-cells property Frank Li
2025-08-19 18:12 ` Conor Dooley [this message]
2025-08-25 10:04 ` 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=20250819-astronomy-gladiator-21823768723a@spud \
--to=conor@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=imx@lists.linux.dev \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.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