From: Conor Dooley <conor@kernel.org>
To: Rustam Adilov <adilov@disroot.org>
Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/8] dt-bindings: i2c: realtek,rtl9301-i2c: extend for clocks and RTL9607C support
Date: Mon, 23 Mar 2026 19:41:45 +0000 [thread overview]
Message-ID: <20260323-stash-contend-ea5974195eac@spud> (raw)
In-Reply-To: <20260323071337.15410-6-adilov@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]
On Mon, Mar 23, 2026 at 12:13:34PM +0500, Rustam Adilov wrote:
> Add the "realtek,rtl9607-i2c" compatible for i2c controller on the
> RTL9607C SoC series.
>
> Add a clocks property to the properties to describe the i2c reference
> clock and make it available for all the compatibles. This i2c reference
Why? I can see that you're doing that, and it's good to know that that
is intentional, but why is it being done? Need to explain that all of
these devices actually do have this clock etc.
> clock is assumed to be coming from switchcore region via Lexra bus as
> the other SoC peripherals.
>
> RTL9607C requires the "realtek,scl" and "clocks" to be specified
> and so handle it under separate if check for "realtek,rtl9607-i2c".
>
> Signed-off-by: Rustam Adilov <adilov@disroot.org>
> ---
> .../bindings/i2c/realtek,rtl9301-i2c.yaml | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml b/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
> index f9a449fee2b0..5873cfdc5b3e 100644
> --- a/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
> +++ b/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
> @@ -15,6 +15,8 @@ description:
> assigned to either I2C controller.
> RTL9310 SoCs have equal capabilities but support 12 common SDA lines which
> can be assigned to either I2C controller.
> + RTL9607C SoCs have equal capabilities but each controller only supports 1
> + SCL/SDA line.
>
> properties:
> compatible:
> @@ -34,6 +36,7 @@ properties:
> - enum:
> - realtek,rtl9301-i2c
> - realtek,rtl9310-i2c
> + - realtek,rtl9607-i2c
>
> reg:
> items:
> @@ -51,6 +54,9 @@ properties:
> The SCL line number of this I2C controller.
> enum: [ 0, 1 ]
>
> + clocks:
> + maxItems: 1
> +
> patternProperties:
> '^i2c@[0-9ab]$':
> $ref: /schemas/i2c/i2c-controller.yaml
> @@ -81,6 +87,15 @@ allOf:
> then:
> patternProperties:
> '^i2c@[89ab]$': false
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: realtek,rtl9607-i2c
> + then:
> + required:
> + - realtek,scl
> + - clocks
>
> required:
> - compatible
> --
> 2.53.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-03-23 19:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 7:13 [PATCH v4 0/8] i2c: rtl9300: support for RTL9607C I2C controller Rustam Adilov
2026-03-23 7:13 ` [PATCH v4 1/8] i2c: rtl9300: split data_reg into read and write reg Rustam Adilov
2026-03-23 7:13 ` [PATCH v4 2/8] i2c: rtl9300: introduce max length property to driver data Rustam Adilov
2026-03-23 7:13 ` [PATCH v4 3/8] i2c: rtl9300: introduce F_BUSY to the reg_fields struct Rustam Adilov
2026-03-23 7:13 ` [PATCH v4 4/8] i2c: rtl9300: introduce a property for 8 bit width reg address Rustam Adilov
2026-03-23 7:13 ` [PATCH v4 5/8] dt-bindings: i2c: realtek,rtl9301-i2c: extend for clocks and RTL9607C support Rustam Adilov
2026-03-23 19:41 ` Conor Dooley [this message]
2026-03-24 15:30 ` Rustam Adilov
2026-03-24 17:48 ` Conor Dooley
2026-03-26 14:59 ` Rustam Adilov
2026-03-23 7:13 ` [PATCH v4 6/8] i2c: rtl9300: introduce clk struct for upcoming rtl9607 support Rustam Adilov
2026-03-23 7:13 ` [PATCH v4 7/8] i2c: rtl9300: intoduce new function properties to driver data Rustam Adilov
2026-03-23 7:13 ` [PATCH v4 8/8] i2c: rtl9300: add RTL9607C i2c controller support Rustam Adilov
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=20260323-stash-contend-ea5974195eac@spud \
--to=conor@kernel.org \
--cc=adilov@disroot.org \
--cc=andi.shyti@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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