From: Jonas Jelonek <jelonek.jonas@gmail.com>
To: linux-i2c@vger.kernel.org,
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>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Markus Stockhausen <markus.stockhausen@gmx.de>,
Jonas Jelonek <jelonek.jonas@gmail.com>
Subject: [PATCH v3 2/3] dt-bindings: i2c: realtek,rtl9301-i2c: extend for RTL9310 support
Date: Sun, 27 Jul 2025 11:47:59 +0000 [thread overview]
Message-ID: <20250727114800.3046-3-jelonek.jonas@gmail.com> (raw)
In-Reply-To: <20250727114800.3046-1-jelonek.jonas@gmail.com>
Add dt-bindings for RTL9310 series I2C controller.
Adjust the regex for child-node address to account for the fact that
RTL9310 supports 12 instead of only 8 SDA lines. Also, narrow this per
variant.
Add a vendor-specific property to explicitly specify the
Realtek-internal ID of the defined I2C controller/master. This is
required, in particular for RTL9310, to describe the correct I2C
master. Require this property for RTL9310.
Add compatibles for known SoC variants RTL9311, RTL9312 and RTL9313.
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
---
.../bindings/i2c/realtek,rtl9301-i2c.yaml | 58 +++++++++++++++++--
1 file changed, 53 insertions(+), 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml b/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
index 69ac5db8b914..29676e99a8c3 100644
--- a/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
+++ b/Documentation/devicetree/bindings/i2c/realtek,rtl9301-i2c.yaml
@@ -10,9 +10,11 @@ maintainers:
- Chris Packham <chris.packham@alliedtelesis.co.nz>
description:
- The RTL9300 SoC has two I2C controllers. Each of these has an SCL line (which
- if not-used for SCL can be a GPIO). There are 8 common SDA lines that can be
- assigned to either I2C controller.
+ The RTL9300 SoCs have two I2C controllers. Each of these has an SCL line
+ (which if not-used for SCL can be a GPIO). There are 8 common SDA lines
+ that can be assigned to either I2C controller.
+ The RTL9310 SoCs have equal capabilities but support 12 common SDA lines
+ which can be assigned to either I2C controller.
properties:
compatible:
@@ -23,7 +25,15 @@ properties:
- realtek,rtl9302c-i2c
- realtek,rtl9303-i2c
- const: realtek,rtl9301-i2c
- - const: realtek,rtl9301-i2c
+ - items:
+ - enum:
+ - realtek,rtl9311-i2c
+ - realtek,rtl9312-i2c
+ - realtek,rtl9313-i2c
+ - const: realtek,rtl9310-i2c
+ - enum:
+ - realtek,rtl9301-i2c
+ - realtek,rtl9310-i2c
reg:
items:
@@ -35,8 +45,15 @@ properties:
"#size-cells":
const: 0
+ realtek,mst-id:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ Realtek-internal ID of the I2C controller/master.
+ minimum: 1
+ maximum: 2
+
patternProperties:
- '^i2c@[0-7]$':
+ '^i2c@([0-9]|1[0-1])$':
$ref: /schemas/i2c/i2c-controller.yaml
unevaluatedProperties: false
@@ -48,6 +65,25 @@ patternProperties:
required:
- reg
+
+allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: realtek,rtl9310-i2c
+ then:
+ required:
+ - realtek,mst-id
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: realtek,rtl9301-i2c
+ then:
+ patternProperties:
+ '^i2c@([8-9]|1[0-1])$': false
+
required:
- compatible
- reg
@@ -68,3 +104,15 @@ examples:
#size-cells = <0>;
};
};
+ - |
+ i2c@100c {
+ compatible = "realtek,rtl9310-i2c";
+ reg = <0x100c 0x18>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ realtek,mst-id = <1>;
+
+ i2c@0 {
+ reg = <0>;
+ };
+ };
--
2.48.1
next prev parent reply other threads:[~2025-07-27 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 11:47 [PATCH v3 0/3] i2c: rework and extend RTL9300 I2C driver Jonas Jelonek
2025-07-27 11:47 ` [PATCH v3 1/3] i2c: rework RTL9300 I2C controller driver Jonas Jelonek
2025-08-02 14:33 ` Sven Eckelmann
2025-07-27 11:47 ` Jonas Jelonek [this message]
2025-07-27 11:48 ` [PATCH v3 3/3] i2c: add RTL9310 support to " Jonas Jelonek
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=20250727114800.3046-3-jelonek.jonas@gmail.com \
--to=jelonek.jonas@gmail.com \
--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=markus.stockhausen@gmx.de \
--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 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.