Re: [PATCH v2 3/7] dt-bindings: i3c: renesas,i3c: Add RZ/G3L support

[Krzysztof Kozlowski]

On Mon, Oct 26, 2026 at 11:35:46AM +0000, Diogo Ivo wrote:
> Add device tree binding support for I3C on the Renesas RZ/G3L
> (R9A08G046) SoC.
> 
> The I3C IP on the RZ/G3L is a subset of the one on the RZ/G3S, as the
> RZ/G3L has no HDR Exit Pattern detection interrupt. The resources are
> consumed by name (the tclk clock, the presetn and tresetn resets and
> seven of the named interrupts), all of which the RZ/G3L provides, so
> software can match and bind a RZ/G3L node through the RZ/G3S
> compatible. Add the RZ/G3L-specific "renesas,r9a08g046-i3c" compatible
> with a fallback to the RZ/G3S "renesas,r9a08g045-i3c" compatible.
> 
> The RZ/G3L is not compatible with the RZ/G3E, which has no input analog
> filters and supports high-speed mode (up to 3.4 Mbps).
> 
> Split the clock and interrupt constraints into separate if/else blocks
> so that RZ/G3L nodes inherit the 2-clock limit from the RZ/G3S fallback
> while being constrained to 16 interrupts alongside the RZ/G3E.
> 
> Signed-off-by: Diogo Ivo <diogo.ivo.sx@xxxxxxxxxxx>
> ---
> Changes in v2:
> - Describe the RZ/G3L by a SoC-specific compatible with a fallback to
>   the renesas,r9a08g045-i3c compatible of the RZ/G3S, instead of a
>   plain compatible, and drop the corresponding driver patch.
> - Split the clock and interrupt constraints into separate if/else
>   blocks to handle the RZ/G3S fallback on RZ/G3L nodes.
> - Explain in the commit message why the RZ/G3L is not made compatible
>   with the RZ/G3E.
> ---
>  .../devicetree/bindings/i3c/renesas,i3c.yaml       | 27 ++++++++++++++--------
>  1 file changed, 18 insertions(+), 9 deletions(-)

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxxxxxxxx>

Best regards,
Krzysztof