From: sashiko-bot@kernel.org
To: "Michael Zavertkin" <misha.zavertkin@mail.ru>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: i2c: rtl9300: add 'rtl9607c-i2c'
Date: Sun, 15 Nov 2026 08:20:23 +0000 [thread overview]
Message-ID: <sashiko-outbox-215290@kernel.org> (raw)
In-Reply-To: <c7b57529342608c59468aef247250aa8f017d5cf.1794728344.git.misha.zavertkin@mail.ru>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] dt-bindings: i2c: rtl9301: per-compatible conditional pile-up
for rtl9607c
--
commit 43c34d3c3c011204c713fd4d1ed08c55685b830d
Author: Michael Zavertkin <misha.zavertkin@mail.ru>
dt-bindings: i2c: rtl9300: add 'rtl9607c-i2c'
This commit adds the realtek,rtl9607c-i2c compatible string with required
clocks and pinctrl properties, and deprecates realtek,rtl9607-i2c.
> diff --git a/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml b/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
> index 5873cfdc5b3e0..7c00918f33c8d 100644
> --- a/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
> +++ b/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
[ ... ]
> @@ -57,6 +61,10 @@ properties:
> clocks:
> maxItems: 1
>
> + pinctrl-0: true
> +
> + pinctrl-names: true
> +
> patternProperties:
> '^i2c@[0-9ab]$':
> $ref: /schemas/i2c/i2c-controller.yaml
> @@ -96,6 +104,16 @@ allOf:
> required:
> - realtek,scl
> - clocks
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: realtek,rtl9607c-i2c
> + then:
> + required:
> + - clocks
> + - pinctrl-0
> + - pinctrl-names
>
> required:
> - compatible
[Severity: Low]
Would it be cleaner to split realtek,rtl9607c-i2c into a separate schema
document rather than adding a fourth per-compatible if-then block to
allOf?
Unlike RTL9300 and RTL9310, which multiplex 8 or 12 shared SDA lines across
controllers and select the SCL line via realtek,scl, RTL9607C has a single
SCL/SDA pair per controller and uses pinctrl instead of realtek,scl.
Keeping realtek,rtl9607c-i2c in this shared schema also leaves the unused
realtek,scl property and multi-channel i2c@[0-9ab] child nodes permitted
for it.
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794728344.git.misha.zavertkin@mail.ru?part=2
prev parent reply other threads:[~2026-11-15 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 8:08 [PATCH v3 0/2] i2c: rtl9300: remove IO_MODE configuration Michael Zavertkin
2026-11-15 8:08 ` [PATCH v3 1/2] i2c: rtl9300: add realtek,rtl9607c-i2c compatible Michael Zavertkin
2026-11-15 8:08 ` [PATCH v3 2/2] dt-bindings: i2c: rtl9300: add 'rtl9607c-i2c' Michael Zavertkin
2026-11-15 8:20 ` sashiko-bot [this message]
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=sashiko-outbox-215290@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=misha.zavertkin@mail.ru \
--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