From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Frank Li <Frank.li@nxp.com>,
linux-renesas-soc@vger.kernel.org,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-i3c@lists.infradead.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH RFC 4/7] i3c: add driver for Renesas I3C IP
Date: Tue, 24 Jun 2025 22:34:38 +0200 [thread overview]
Message-ID: <aFsL3pJBT6IpYD5M@shikoro> (raw)
In-Reply-To: <aEvyfM42WTKENbFO@shikoro>
> > > There is a specified timeout? I couldn't find one in the specs, can you
> > > kindly point me to it? So, the solution is to use 100us as timeout?
> >
> > See: 5.1.2.5 Controller Clock Stalling
>
> Ah, I missed this one so far. Thanks!
>
> > The spec have not defined what exactly happen if stall clock more than
> > 100us.
>
> I am going to the I3C Plugfest in Warszaw in 10 days. I could ask people
> there...
Well, I also couldn't get an answer here. It seems that part of the
spec has not been excercised a lot so far. The best recommendation was
also to use a timeout < 100us, so that you have a bit of time for
cancelling.
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Frank Li <Frank.li@nxp.com>,
linux-renesas-soc@vger.kernel.org,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-i3c@lists.infradead.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH RFC 4/7] i3c: add driver for Renesas I3C IP
Date: Tue, 24 Jun 2025 22:34:38 +0200 [thread overview]
Message-ID: <aFsL3pJBT6IpYD5M@shikoro> (raw)
In-Reply-To: <aEvyfM42WTKENbFO@shikoro>
> > > There is a specified timeout? I couldn't find one in the specs, can you
> > > kindly point me to it? So, the solution is to use 100us as timeout?
> >
> > See: 5.1.2.5 Controller Clock Stalling
>
> Ah, I missed this one so far. Thanks!
>
> > The spec have not defined what exactly happen if stall clock more than
> > 100us.
>
> I am going to the I3C Plugfest in Warszaw in 10 days. I could ask people
> there...
Well, I also couldn't get an answer here. It seems that part of the
spec has not been excercised a lot so far. The best recommendation was
also to use a timeout < 100us, so that you have a bit of time for
cancelling.
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2025-06-24 20:34 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 9:39 [PATCH RFC 0/7] i3c: add driver for the Renesas IP and support RZ/G3S+G3E Wolfram Sang
2025-06-11 9:39 ` Wolfram Sang
2025-06-11 9:39 ` [PATCH RFC 1/7] clk: renesas: r9a08g045: Add I3C clocks, resets and power domain Wolfram Sang
2025-06-19 12:09 ` Geert Uytterhoeven
2025-06-11 9:39 ` [PATCH RFC 2/7] clk: renesas: r9a09g047: Add I3C0 clocks and resets Wolfram Sang
2025-06-19 12:16 ` Geert Uytterhoeven
2025-06-11 9:39 ` [PATCH RFC 3/7] dt-bindings: i3c: renesas,i3c: Add binding for Renesas I3C controller Wolfram Sang
2025-06-11 9:39 ` Wolfram Sang
2025-06-11 15:40 ` Frank Li
2025-06-11 15:40 ` Frank Li
2025-06-12 14:31 ` Wolfram Sang
2025-06-12 14:31 ` Wolfram Sang
2025-06-12 14:51 ` Tommaso Merciai
2025-06-12 14:51 ` Tommaso Merciai
2025-06-12 15:35 ` Frank Li
2025-06-12 15:35 ` Frank Li
2025-06-25 20:04 ` Rob Herring
2025-06-25 20:04 ` Rob Herring
2025-06-26 1:37 ` Frank Li
2025-06-26 1:37 ` Frank Li
2025-06-25 20:07 ` Rob Herring
2025-06-25 20:07 ` Rob Herring
2025-06-30 19:43 ` Wolfram Sang
2025-06-30 19:43 ` Wolfram Sang
2025-07-01 9:09 ` Tommaso Merciai
2025-07-01 9:09 ` Tommaso Merciai
2025-07-03 7:18 ` Wolfram Sang
2025-07-03 7:18 ` Wolfram Sang
2025-06-11 9:39 ` [PATCH RFC 4/7] i3c: add driver for Renesas I3C IP Wolfram Sang
2025-06-11 9:39 ` Wolfram Sang
2025-06-11 16:37 ` Frank Li
2025-06-11 16:37 ` Frank Li
2025-06-12 14:55 ` Wolfram Sang
2025-06-12 14:55 ` Wolfram Sang
2025-06-12 16:42 ` Frank Li
2025-06-12 16:42 ` Frank Li
2025-06-13 9:42 ` Wolfram Sang
2025-06-13 9:42 ` Wolfram Sang
2025-06-13 12:23 ` Geert Uytterhoeven
2025-06-13 12:23 ` Geert Uytterhoeven
2025-06-13 13:10 ` Wolfram Sang
2025-06-13 13:10 ` Wolfram Sang
2025-06-17 7:12 ` Geert Uytterhoeven
2025-06-17 7:12 ` Geert Uytterhoeven
2025-06-17 11:22 ` Wolfram Sang
2025-06-17 11:22 ` Wolfram Sang
2025-06-25 10:00 ` Wolfram Sang
2025-06-25 10:00 ` Wolfram Sang
2025-06-24 20:34 ` Wolfram Sang [this message]
2025-06-24 20:34 ` Wolfram Sang
2025-06-13 14:41 ` Frank Li
2025-06-13 14:41 ` Frank Li
2025-06-17 9:42 ` Wolfram Sang
2025-06-17 9:42 ` Wolfram Sang
2025-07-24 8:58 ` Wolfram Sang
2025-07-24 8:58 ` Wolfram Sang
2025-06-11 9:39 ` [PATCH RFC 5/7] arm64: dts: renesas: r9a08g045: Add I3C node Wolfram Sang
2025-06-11 9:39 ` [PATCH RFC 6/7] arm64: dts: renesas: r9a09g047: " Wolfram Sang
2025-06-11 9:39 ` [PATCH RFC 7/7] WIP: arm64: dts: renesas: rzg3s-smarc-som: Enable I3C Wolfram Sang
2025-06-11 13:11 ` [PATCH RFC 0/7] i3c: add driver for the Renesas IP and support RZ/G3S+G3E Rob Herring (Arm)
2025-06-11 13:11 ` Rob Herring (Arm)
2025-06-11 18:56 ` Wolfram Sang
2025-06-11 18:56 ` Wolfram Sang
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=aFsL3pJBT6IpYD5M@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=geert+renesas@glider.be \
--cc=gustavoars@kernel.org \
--cc=kees@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=tommaso.merciai.xr@bp.renesas.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 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.