From: sashiko-bot@kernel.org
To: "Omer PALA" <palaomer100@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: iio: adc: Add dt binding to xlnx,xadc
Date: Fri, 18 Sep 2026 18:02:12 +0000 [thread overview]
Message-ID: <20260918180212.78E901F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918174809.17502-1-palaomer100@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: iio: conflicting constraints when xlnx,external-mux is omitted
--
commit 650a4d99eb23987562466c53ef3d4d648db29eba
Author: Omer PALA <palaomer100@gmail.com>
dt-bindings: iio: adc: Add dt binding to xlnx,xadc
Add yaml devicetree binding for xlnx,zynq-xadc-1.00.a,
xlnx,axi-xadc-1.00.a and xlnx,system-management-wiz-1.3 from
xilinx-xadc.txt file.
> diff --git a/Documentation/devicetree/bindings/iio/adc/xlnx,xadc.yaml b/Documentation/devicetree/bindings/iio/adc/xlnx,xadc.yaml
> new file mode 100644
> index 0000000000000..f9b717c297158
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/xlnx,xadc.yaml
[ ... ]
> +allOf:
> + - if:
> + properties:
> + xlnx,external-mux:
> + const: none
> + then:
> + properties:
> + xlnx,external-mux-channel: false
> +
> + - if:
> + properties:
> + xlnx,external-mux:
> + const: single
[Severity: Low]
Is there a potential conflict here if the xlnx,external-mux property is
omitted?
Looking at JSON schema semantics, missing properties evaluate to true when
checked against a const. Because the if block doesn't specify
required: [xlnx,external-mux], all three of the conditional branches (none,
single, and dual) might trigger simultaneously if a valid device tree
omits the property.
> + then:
> + properties:
> + xlnx,external-mux-channel:
> + minimum: 0
> + maximum: 16
> + required:
> + - xlnx,external-mux-channel
[Severity: Low]
When the xlnx,external-mux property is omitted, will this 'then' block
trigger alongside the 'none' block?
If both trigger, this block explicitly requires xlnx,external-mux-channel
while the 'none' block simultaneously forbids it. This could cause valid
device trees that rely on the default value to fail dtbs_check validation.
Should these 'if' blocks include a required list for the xlnx,external-mux
property to prevent them from evaluating to true when the property is
missing?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260918174809.17502-1-palaomer100@gmail.com?part=1
next prev parent reply other threads:[~2026-09-18 18:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 14:58 [PATCH] dt-bindings: iio: adc: Add dt binding to xlnx,xadc Omer PALA
2026-09-18 15:03 ` sashiko-bot
2026-09-18 17:48 ` [PATCH v2] " Omer PALA
2026-09-18 18:02 ` sashiko-bot [this message]
2026-09-18 18:58 ` [PATCH v3] " Omer PALA
2026-09-18 19:07 ` sashiko-bot
2026-09-18 19:44 ` [PATCH v4] " Omer PALA
2026-09-18 19:53 ` sashiko-bot
2026-09-18 20:32 ` [PATCH v5] " Omer PALA
2026-09-19 7:25 ` Krzysztof Kozlowski
2026-09-19 8:07 ` Omer PALA
2026-09-19 8:30 ` Krzysztof Kozlowski
2026-09-19 7:32 ` [PATCH v2] " Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2026-09-18 17:44 Omer PALA
2026-09-18 17:53 ` sashiko-bot
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=20260918180212.78E901F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=palaomer100@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.