From: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Frank Li <Frank.Li@nxp.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kees Cook <kees@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-hardening@vger.kernel.org, linux-i3c@lists.infradead.org,
Magnus Damm <magnus.damm@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v4 0/4] i3c: add support for the Renesas controller
Date: Wed, 23 Jul 2025 11:35:44 +0200 [thread overview]
Message-ID: <aICs8JmAUbxFxizc@tom-desktop> (raw)
In-Reply-To: <20250722190749.6264-1-wsa+renesas@sang-engineering.com>
Hi Wolfram,
Thanks for your series!
On Tue, Jul 22, 2025 at 09:07:42PM +0200, Wolfram Sang wrote:
> Detailed changes since v3 are described in the individual patches. A
> branch with enablement patches for RZ/G3S+G3E can be found here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/g3s/i3c
>
> Old coverletter:
>
> Here is a basic driver for the I3C IP found in various Renesas SoCs like
> RZ/G3S and G3E. Missing features to be added incrementally are IBI,
> HotJoin and maybe target support. Other than that, this driver has been
> tested with I3C pure busses (2 targets) and mixed busses (2 I3C +
> various I2C targets). DAA and reading/writing to the temperature sensors
> worked reliably at different speeds. Scoping the bus, the output from
> the protocol analyzer seems reasonable, too. It was created by merging
> two versions of it from two different BSPs. Then, improved according to
> code analyzers, cleaned up with regard to coding style, and then
> refactored to hopefully match I3C subsystem standards.
>
> Looking forward to comments,
>
> Wolfram
>
>
> Tommaso Merciai (1):
> dt-bindings: i3c: Add Renesas I3C controller
>
> Wolfram Sang (3):
> i3c: Standardize defines for specification parameters
> i3c: Add more parameters for controllers to the header
> i3c: master: Add basic driver for the Renesas I3C controller
Tested this series on top of [1], using RZ/G3E SMARC EVK board +
SMARC BREAKOUT board connected to P3T1085UK-ARD, using i3c pure bus and
I'm able to read the i3c temperature sensor:
root@smarc-rzg3e:~# cat /sys/class/hwmon/*/temp1_input
25875
For all the series:
Tested-by: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
[1] https://lkml.org/lkml/2025/6/24/581
Thanks & Regards,
Tommaso
>
> .../devicetree/bindings/i3c/renesas,i3c.yaml | 179 +++
> MAINTAINERS | 7 +
> drivers/i3c/master.c | 12 +-
> drivers/i3c/master/Kconfig | 10 +
> drivers/i3c/master/Makefile | 1 +
> drivers/i3c/master/dw-i3c-master.c | 4 +-
> drivers/i3c/master/renesas-i3c.c | 1404 +++++++++++++++++
> include/linux/i3c/master.h | 16 +-
> 8 files changed, 1621 insertions(+), 12 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/i3c/renesas,i3c.yaml
> create mode 100644 drivers/i3c/master/renesas-i3c.c
>
> --
> 2.47.2
>
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2025-07-23 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 19:07 [PATCH v4 0/4] i3c: add support for the Renesas controller Wolfram Sang
2025-07-22 19:07 ` [PATCH v4 1/4] i3c: Standardize defines for specification parameters Wolfram Sang
2025-07-23 15:30 ` Frank Li
2025-07-22 19:07 ` [PATCH v4 2/4] i3c: Add more parameters for controllers to the header Wolfram Sang
2025-07-23 15:32 ` Frank Li
2025-07-23 17:50 ` Wolfram Sang
2025-07-24 9:09 ` Wolfram Sang
2025-07-22 19:07 ` [PATCH v4 3/4] dt-bindings: i3c: Add Renesas I3C controller Wolfram Sang
2025-07-22 19:07 ` [PATCH v4 4/4] i3c: master: Add basic driver for the " Wolfram Sang
2025-07-23 15:33 ` Frank Li
2025-07-23 9:35 ` Tommaso Merciai [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=aICs8JmAUbxFxizc@tom-desktop \
--to=tommaso.merciai.xr@bp.renesas.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).