From: sashiko-bot@kernel.org
To: "Michal Piekos" <michal.piekos@mmpsystems.pl>
Cc: robh@kernel.org, devicetree@vger.kernel.org, krzk+dt@kernel.org,
linux-sunxi@lists.linux.dev, conor+dt@kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: iio: adc: Add GPADC for Allwinner A523
Date: Sat, 16 May 2026 05:50:02 +0000 [thread overview]
Message-ID: <20260516055003.3F014C19425@smtp.kernel.org> (raw)
In-Reply-To: <20260516-sunxi-a523-gpadc-v3-1-a3a04cff2620@mmpsystems.pl>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] Brittle schema conditional matching for compatible string
- [Low] Missing device tree example for the newly added A523 variant
--
commit 8ef795d51c1bc739366c917fc7bb2c4c8c5c937c
Author: Michal Piekos <michal.piekos@mmpsystems.pl>
dt-bindings: iio: adc: Add GPADC for Allwinner A523
Add support for the GPADC for the Allwinner A523, which introduces a
second clock compared to previous generations.
> diff --git a/Documentation/devicetree/bindings/iio/adc/allwinner,sun20i-d1-gpadc.yaml b/Documentation/devicetree/bindings/iio/adc/allwinner,sun20i-d1-gpadc.yaml
> index da605a051b949..6467800d30e27 100644
> --- a/Documentation/devicetree/bindings/iio/adc/allwinner,sun20i-d1-gpadc.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/allwinner,sun20i-d1-gpadc.yaml
[ ... ]
> +allOf:
> + - if:
> + properties:
> + compatible:
> + enum:
> + - allwinner,sun55i-a523-gpadc
Could this conditional matching be brittle?
Using a strict enum instead of contains: enum will fail if a future
hardware variant uses allwinner,sun55i-a523-gpadc as a fallback string
in an array. Would it be better to use contains: enum here to ensure
standard extensibility?
> + then:
> + properties:
> + clocks:
> + items:
> + - description: Bus clock
> + - description: Module clock
> + clock-names:
> + items:
> + - const: bus
> + - const: mod
> + required:
> + - clock-names
Should an example be added for the allwinner,sun55i-a523-gpadc variant
in the examples section?
Without an example, it appears the new constraints for the two clocks
and the clock-names property will not be tested during dt_binding_check.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260516-sunxi-a523-gpadc-v3-0-a3a04cff2620@mmpsystems.pl?part=1
next prev parent reply other threads:[~2026-05-16 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 5:34 [PATCH v3 0/3] Add GPADC support for A523 Michal Piekos
2026-05-16 5:34 ` [PATCH v3 1/3] dt-bindings: iio: adc: Add GPADC for Allwinner A523 Michal Piekos
2026-05-16 5:50 ` sashiko-bot [this message]
2026-05-16 5:34 ` [PATCH v3 2/3] iio: adc: sun20i-gpadc: add A523 gpadc support Michal Piekos
2026-05-16 15:02 ` Jonathan Cameron
2026-05-16 5:34 ` [PATCH v3 3/3] arm64: dts: allwinner: a523: add gpadc node Michal Piekos
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=20260516055003.3F014C19425@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=michal.piekos@mmpsystems.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox