From: Frank Li <Frank.li@nxp.com>
To: Claudiu Beznea <claudiu.beznea@kernel.org>
Cc: wsa+renesas@sang-engineering.com,
tommaso.merciai.xr@bp.renesas.com, alexandre.belloni@bootlin.com,
p.zabel@pengutronix.de, claudiu.beznea@tuxon.dev,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 06/17] i3c: renesas: Perform Dynamic Address Assignment on resume
Date: Tue, 2 Jun 2026 16:12:53 -0400 [thread overview]
Message-ID: <ah85RaUXmaBVFkYk@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260602132824.3541151-7-claudiu.beznea@kernel.org>
On Tue, Jun 02, 2026 at 04:28:13PM +0300, Claudiu Beznea wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> The Renesas RZ/G3S SoC supports a power saving mode where power to most
> SoC components, including I3C, is turned off.
>
> On systems where the I3C devices also loses power during suspend (e.g. NXP
> P3T1085UK-ARD connected to the PMOD1_6A connector of the RZ SMARC Carrier
> 2 + Renesas RZ/G3S SMARC SOM), the devices becomes unreachable after
> resume.
>
> Running DAA in the controller resume path restores communication. However,
> DAA relies on interrupts for TX/RX, which are not available in the noirq
> suspend/resume phase (unless they are wakeup interrupts). For this, the
> suspend/resume callbacks were moved out of the noirq phase. Currently,
> there is no identified use case on either the Renesas RZ/G3S or Renesas
> RZ/G3E SoCs that requires the controller suspend/resume hooks to be part of
> the noirq suspend/resume phase.
>
> Since renesas_i3c_reset() is not called anymore in atomic context
> update it to use read_poll_timeout().
>
> To cover the case where the controller had already attached all the
> i3c->maxdevs devices before a suspend/resume cycle and i3c->free_pos is
> zero, struct renesas_i3c::resuming flag was introduced.
>
> The flag is set in renesas_i3c_resume() before calling
> i3c_master_do_daa_ext() and checked in renesas_i3c_daa(). In case it is
> set the previous saved DATBAS register values are used for the slots
> already occupied before suspend. This allows keeping alive the connection
> to the I3C devices when all the supported slots are occupied before
> suspend.
>
> When resuming from suspend, renesas_i3c_daa() re-runs DAA for al
> slots except those used by I2C devices. I2C devices are attached during
> probe, at bus initialization time, and always occupy the first positions in
> i3c->free_pos. In addition, there are no DATBAS register settings
> associated with them.
>
> Fixes: e7218986319b ("i3c: renesas: Add suspend/resume support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> ---
Please check sashiko review result
https://sashiko.dev/#/patchset/20260602132824.3541151-1-claudiu.beznea%40kernel.org
Frank
>
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2026-06-02 20:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 13:28 [PATCH v2 00/17] i3c: renesas: Suspend to RAM with power loss and runtime PM Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 01/17] i3c: renesas: Check that the transfer is valid before accessing it Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 02/17] i3c: renesas: Restore STDBR and EXTBR registers on resume Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 03/17] i3c: renesas: Follow the reset deassert order used in probe Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 04/17] i3c: renesas: Reconfigure the DATBAS register on re-attach Claudiu Beznea
2026-06-02 20:05 ` Frank Li
2026-06-02 13:28 ` [PATCH v2 05/17] i3c: renesas: Reset the controller on resume Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 06/17] i3c: renesas: Perform Dynamic Address Assignment " Claudiu Beznea
2026-06-02 20:12 ` Frank Li [this message]
2026-06-03 14:23 ` Claudiu Beznea
2026-06-03 19:26 ` Frank Li
2026-06-04 13:04 ` Claudiu Beznea
2026-06-04 18:49 ` Frank Li
2026-06-02 13:28 ` [PATCH v2 07/17] i3c: renesas: Do not attach devices if xfer failed Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 08/17] i3c: renesas: Clean DATBAS register on detach Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 09/17] i3c: renesas: Use reset_control_bulk_{assert, deassert}() Claudiu Beznea
2026-06-02 15:09 ` Philipp Zabel
2026-06-02 13:28 ` [PATCH v2 10/17] i3c: renesas: Return immediately if there is no transfer Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 11/17] i3c: renesas: Follow a unified pattern for transfer and command initialization Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 12/17] i3c: renesas: Drop the explicit memset() call Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 13/17] i3c: renesas: Update HW registers after SW computations are done Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 14/17] i3c: renesas: Organize structures to avoid unnecessary padding Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 15/17] i3c: renesas: Use the "dev_name:irq_name" format for the interrupt name Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 16/17] i3c: renesas: Drop unnecessary tab Claudiu Beznea
2026-06-02 13:28 ` [PATCH v2 17/17] i3c: renesas: Add runtime PM support Claudiu Beznea
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=ah85RaUXmaBVFkYk@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=stable@vger.kernel.org \
--cc=tommaso.merciai.xr@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