From: Krzysztof Kozlowski <krzk@kernel.org>
To: zain_zhou@realsil.com.cn, linux-staging@lists.linux.dev,
linux-i3c@lists.infradead.org, devicetree@vger.kernel.org
Cc: gregkh@linuxfoundation.org, alexandre.belloni@bootlin.com,
Frank.Li@nxp.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linusw@kernel.org, brgl@kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
wei_wang@realsil.com.cn
Subject: Re: [PATCH v2 1/2] dt-bindings: i3c: add Realtek RTS490x I3C HUB
Date: Mon, 25 May 2026 15:58:52 +0200 [thread overview]
Message-ID: <64a8ba7e-f044-4f51-8619-9419ec7dfc27@kernel.org> (raw)
In-Reply-To: <20260525125128.297-1-zain_zhou@realsil.com.cn>
On 25/05/2026 14:51, zain_zhou@realsil.com.cn wrote:
> From: Yin Zhou <zain_zhou@realsil.com.cn>
>
> Add DT binding schema for Realtek RTS490x series I3C HUB devices.
>
> The binding describes configuration properties for:
> - LDO enable/disable and voltage level per port group
> - Pull-up resistance per port group
> - IO driver strength per port
> - Per target-port mode (I3C/SMBus/GPIO/disabled), pull-up,
> IO mode, SMBus clock frequency and polling interval
> - Hub network always-I3C mode
> - Hardware identification via CSEL pin (id) and CP1 pins (id-cp1)
>
> Signed-off-by: Yin Zhou <zain_zhou@realsil.com.cn>
>
> Changes in v2:
Messed patch. DCO is always the last. And this should tell you that
changelog does not belong here - goes under ---.
Anyway, did you test the binding this time or we expect another failures?
> - Rework binding per Krzysztof Kozlowski's review:
> add realtek, vendor prefix to all custom properties; use boolean
> for enable flags; use u32 with unit suffixes (-microvolt, -ohms)
> for voltage/resistance; change to unevaluatedProperties: false;
> fix title, maintainer name, description, $nodename pattern
> - Consolidate examples; add dt-bindings/i2c/i2c.h include
> ---
> .../bindings/i3c/realtek,rts490x-i3c-hub.yaml | 263 ++++++++++++++++++
> 1 file changed, 263 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/i3c/realtek,rts490x-i3c-hub.yaml
>
> diff --git a/Documentation/devicetree/bindings/i3c/realtek,rts490x-i3c-hub.yaml b/Documentation/devicetree/bindings/i3c/realtek,rts490x-i3c-hub.yaml
> new file mode 100644
> index 000000000000..851a433abcd3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i3c/realtek,rts490x-i3c-hub.yaml
> @@ -0,0 +1,263 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i3c/realtek,rts490x-i3c-hub.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Realtek RTS490x I3C HUB
> +
> +maintainers:
> + - Yin Zhou <zain_zhou@realsil.com.cn>
> +
> +description:
> + The Realtek RTS490x is an I3C HUB device that provides voltage level
> + translation between I3C controller and target devices, bus capacitance
> + isolation, address conflict isolation, I3C port expansion (up to 8
> + target ports), simultaneous dual-controller port support, and per-port
> + mode selection (I3C, SMBus, GPIO, or disabled).
> +
> +properties:
> + $nodename:
> + pattern: "^hub@[0-9a-f]+(,[0-9a-f]+)*$"
> +
> + compatible:
> + const: realtek,rts490x-i3c-hub
> +
> + reg:
> + maxItems: 1
> + description:
> + Encodes the static I2C address, manufacturer ID, and part/instance ID
> + as defined by the I3C specification.
> +
> + assigned-address:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + minimum: 0x1
> + maximum: 0xff
> + description:
> + Dynamic I3C address to assign to this device.
> +
> + dcr:
Where is the property defined?
Read carefully writing bindings doc and DTS101 slides. I finished review
here. You still did not implement things we asked - to follow other
bindings style.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-25 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 12:51 zain_zhou
2026-05-25 12:51 ` [PATCH v2 2/2] staging: i3c: add Realtek RTS490x I3C HUB driver zain_zhou
2026-05-25 13:25 ` Alexandre Belloni
2026-05-25 14:00 ` Krzysztof Kozlowski
2026-05-25 19:11 ` Greg KH
2026-05-25 13:58 ` Krzysztof Kozlowski [this message]
2026-05-25 18:45 ` [PATCH v2 1/2] dt-bindings: i3c: add Realtek RTS490x I3C HUB Rob Herring (Arm)
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=64a8ba7e-f044-4f51-8619-9419ec7dfc27@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=robh@kernel.org \
--cc=wei_wang@realsil.com.cn \
--cc=zain_zhou@realsil.com.cn \
/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
all inboxes | Powered by JetHome®