From: "Rob Herring (Arm)" <robh@kernel.org>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: devicetree@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add I3C support to RZ/V2N and RZ/V2H(P) SoCs
Date: Thu, 04 Sep 2025 21:32:45 -0500 [thread overview]
Message-ID: <175703941904.745223.12563008293745270864.robh@kernel.org> (raw)
In-Reply-To: <20250904165909.281131-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
On Thu, 04 Sep 2025 17:59:07 +0100, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Hi All,
>
> This series adds I3C node to RZ/V2N and RZ/V2H(P) SoC DTSI files.
>
> I3C was tested on RZ/V2H(P) and RZ/V2N EVKs using P3T1085UK Arduino
> Shield Evaluation Board [0].
>
> Disable I2C2 on PMOD connector CN6 and enable I3C.
>
> Connect EVK TO P3T1085UK Arduino Shield Evaluation Board
> P3T1085UK <-> EVK PMOD CN6
> - J13[1] to CN6[3] (I3C_SCL)
> - J13[2] to CN6[4] (I3C_SDA)
> - J13[4] to CN6[5] (GND)
> - J9[7] to CN6[11] (GND)
> - J9[9] to CN6[6] (3.3V)
>
> On P3T1085UK,
> - JP2 pin1 to pin2 (I3C_SDA)
> - JP3 pin1 to pin2 (I3C_SCL)
> - JP1 pin2 to pin3 (VDD 3V3)
>
>
> [0] https://www.nxp.com/design/design-center/development-boards-and-designs/analog-toolbox/arduino-shields-solutions/p3t1085uk-arduino-shield-evaluation-board:P3T1085UK-ARD
>
> Test Logs:
> --- RZ/V2H(P) ---
> root@rzv2h-evk:~# cat /sys/kernel/debug/clk/clk_summary | grep i3c
> i3c_0_pclk 1 2 0 100000000 0 0 50000 Y 12400000.i3c pclk
> i3c_0_pclkrw 1 2 0 100000000 0 0 50000 Y 12400000.i3c pclkrw
> i3c_0_tclk 1 2 0 200000000 0 0 50000 Y 12400000.i3c tclk
> root@rzv2h-evk:~#
> root@rzv2h-evk:~# cat /sys/class/hwmon/*/temp1_input
> 26687
> 26812
> root@rzv2h-evk:~# cat /proc/interrupts | grep i3c
> 150: 38 0 0 0 GICv3 709 Edge i3c-resp
> 151: 2 0 0 0 GICv3 712 Edge i3c-rx
> 152: 0 0 0 0 GICv3 713 Edge i3c-tx
> 153: 0 0 0 0 GICv3 721 Level i3c-start
> 154: 0 0 0 0 GICv3 722 Level i3c-stop
> 155: 0 0 0 0 GICv3 724 Level i3c-tend
> 156: 0 0 0 0 GICv3 725 Level i3c-nack
> root@rzv2h-evk:~# cat /sys/class/hwmon/*/temp1_input
> 26687
> 26812
> root@rzv2h-evk:~# cat /proc/interrupts | grep i3c
> 150: 42 0 0 0 GICv3 709 Edge i3c-resp
> 151: 2 0 0 0 GICv3 712 Edge i3c-rx
> 152: 0 0 0 0 GICv3 713 Edge i3c-tx
> 153: 0 0 0 0 GICv3 721 Level i3c-start
> 154: 0 0 0 0 GICv3 722 Level i3c-stop
> 155: 0 0 0 0 GICv3 724 Level i3c-tend
> 156: 0 0 0 0 GICv3 725 Level i3c-nack
> root@rzv2h-evk:~#
>
> --- RZ/V2N ---
> root@rzv2n-evk:~# cat /sys/kernel/debug/clk/clk_summary | grep i3c
> i3c_0_pclk 1 2 0 100000000 0 0 50000 Y 12400000.i3c pclk
> i3c_0_pclkrw 1 2 0 100000000 0 0 50000 Y 12400000.i3c pclkrw
> i3c_0_tclk 1 2 0 200000000 0 0 50000 Y 12400000.i3c tclk
> root@rzv2n-evk:~# cat /proc/interrupts | grep i3c
> 65: 22 0 0 0 GICv3 709 Edge i3c-resp
> 66: 2 0 0 0 GICv3 712 Edge i3c-rx
> 67: 0 0 0 0 GICv3 713 Edge i3c-tx
> 68: 0 0 0 0 GICv3 721 Level i3c-start
> 69: 0 0 0 0 GICv3 722 Level i3c-stop
> 70: 0 0 0 0 GICv3 724 Level i3c-tend
> 71: 0 0 0 0 GICv3 725 Level i3c-nack
> root@rzv2n-evk:~# cat /sys/class/hwmon/*/temp1_input
> 27000
> 27125
> root@rzv2n-evk:~# cat /proc/interrupts | grep i3c
> 65: 26 0 0 0 GICv3 709 Edge i3c-resp
> 66: 2 0 0 0 GICv3 712 Edge i3c-rx
> 67: 0 0 0 0 GICv3 713 Edge i3c-tx
> 68: 0 0 0 0 GICv3 721 Level i3c-start
> 69: 0 0 0 0 GICv3 722 Level i3c-stop
> 70: 0 0 0 0 GICv3 724 Level i3c-tend
> 71: 0 0 0 0 GICv3 725 Level i3c-nack
> root@rzv2n-evk:~#
>
> Cheers,
> Prabhakar
>
> Lad Prabhakar (2):
> arm64: dts: renesas: r9a09g057: Add I3C node
> arm64: dts: renesas: r9a09g056: Add I3C node
>
> arch/arm64/boot/dts/renesas/r9a09g056.dtsi | 33 ++++++++++++++++++++++
> arch/arm64/boot/dts/renesas/r9a09g057.dtsi | 33 ++++++++++++++++++++++
> 2 files changed, 66 insertions(+)
>
> --
> 2.51.0
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
This patch series was applied (using b4) to base:
Base: attempting to guess base-commit...
Base: failed to guess base
If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/renesas/' for 20250904165909.281131-1-prabhakar.mahadev-lad.rj@bp.renesas.com:
arch/arm64/boot/dts/renesas/r9a09g056n48-rzv2n-evk.dtb: i3c@12400000 (renesas,r9a09g056-i3c): compatible:0: 'renesas,r9a09g056-i3c' is not one of ['renesas,r9a08g045-i3c', 'renesas,r9a09g047-i3c']
from schema $id: http://devicetree.org/schemas/i3c/renesas,i3c.yaml#
arch/arm64/boot/dts/renesas/r9a09g056n48-rzv2n-evk.dtb: i3c@12400000 (renesas,r9a09g056-i3c): compatible: ['renesas,r9a09g056-i3c', 'renesas,r9a09g047-i3c'] is too long
from schema $id: http://devicetree.org/schemas/i3c/renesas,i3c.yaml#
arch/arm64/boot/dts/renesas/r9a09g057h48-kakip.dtb: i3c@12400000 (renesas,r9a09g057-i3c): compatible:0: 'renesas,r9a09g057-i3c' is not one of ['renesas,r9a08g045-i3c', 'renesas,r9a09g047-i3c']
from schema $id: http://devicetree.org/schemas/i3c/renesas,i3c.yaml#
arch/arm64/boot/dts/renesas/r9a09g057h48-kakip.dtb: i3c@12400000 (renesas,r9a09g057-i3c): compatible: ['renesas,r9a09g057-i3c', 'renesas,r9a09g047-i3c'] is too long
from schema $id: http://devicetree.org/schemas/i3c/renesas,i3c.yaml#
arch/arm64/boot/dts/renesas/r9a09g057h44-rzv2h-evk.dtb: i3c@12400000 (renesas,r9a09g057-i3c): compatible:0: 'renesas,r9a09g057-i3c' is not one of ['renesas,r9a08g045-i3c', 'renesas,r9a09g047-i3c']
from schema $id: http://devicetree.org/schemas/i3c/renesas,i3c.yaml#
arch/arm64/boot/dts/renesas/r9a09g057h44-rzv2h-evk.dtb: i3c@12400000 (renesas,r9a09g057-i3c): compatible: ['renesas,r9a09g057-i3c', 'renesas,r9a09g047-i3c'] is too long
from schema $id: http://devicetree.org/schemas/i3c/renesas,i3c.yaml#
prev parent reply other threads:[~2025-09-05 2:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 16:59 Prabhakar
2025-09-04 16:59 ` [PATCH 1/2] arm64: dts: renesas: r9a09g057: Add I3C node Prabhakar
2025-09-11 15:51 ` Geert Uytterhoeven
2025-09-04 16:59 ` [PATCH 2/2] arm64: dts: renesas: r9a09g056: " Prabhakar
2025-09-11 15:51 ` Geert Uytterhoeven
2025-09-05 2:32 ` Rob Herring (Arm) [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=175703941904.745223.12563008293745270864.robh@kernel.org \
--to=robh@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=wsa+renesas@sang-engineering.com \
/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®