mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 04/17] i3c: renesas: Reconfigure the DATBAS register on re-attach
Date: Tue, 2 Jun 2026 16:05:30 -0400	[thread overview]
Message-ID: <ah83iknpm9uhdi4S@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260602132824.3541151-5-claudiu.beznea@kernel.org>

On Tue, Jun 02, 2026 at 04:28:11PM +0300, Claudiu Beznea wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> During re-attach, the device may change its position in the i3c->addrs[]
> array. As a result, it may use a different Device Address Table Basic
> Register (DATBAS), which needs to be reconfigured.
>
> Reconfigure the DATBAS register on re-attach. Along with it update
> software caches.
>
> Fixes: d028219a9f14 ("i3c: master: Add basic driver for the Renesas I3C controller")
> Cc: stable@vger.kernel.org
> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> ---

Reviewed-by: Frank Li <Frank.Li@nxp.com>

>
> Changes in v2:
> - dropped the "if (pos < 0)" check in renesas_i3c_reattach_i3c_dev() to allow
>   re-attaching in case of a full bus; along with it the condition to update
>   the DATBAS register and software caches was updated to
>   if (data->index != pos && pos >= 0)
> - adjusted the patch title
>
>  drivers/i3c/master/renesas-i3c.c | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
>
> diff --git a/drivers/i3c/master/renesas-i3c.c b/drivers/i3c/master/renesas-i3c.c
> index 4c86e7257804..76a4831098c9 100644
> --- a/drivers/i3c/master/renesas-i3c.c
> +++ b/drivers/i3c/master/renesas-i3c.c
> @@ -892,10 +892,26 @@ static int renesas_i3c_reattach_i3c_dev(struct i3c_dev_desc *dev,
>  	struct i3c_master_controller *m = i3c_dev_get_master(dev);
>  	struct renesas_i3c *i3c = to_renesas_i3c(m);
>  	struct renesas_i3c_i2c_dev_data *data = i3c_dev_get_master_data(dev);
> +	int pos;
> +
> +	pos = renesas_i3c_get_free_pos(i3c);
> +
> +	if (data->index != pos && pos >= 0) {
> +		renesas_writel(i3c->regs, DATBAS(data->index), 0);
> +		i3c->addrs[data->index] = 0;
> +		i3c->free_pos |= BIT(data->index);
> +
> +		data->index = pos;
> +		i3c->free_pos &= ~BIT(data->index);
> +	}
>
>  	i3c->addrs[data->index] = dev->info.dyn_addr ? dev->info.dyn_addr :
>  							dev->info.static_addr;
>
> +	renesas_writel(i3c->regs, DATBAS(data->index),
> +		       DATBAS_DVSTAD(dev->info.static_addr) |
> +		       datbas_dvdyad_with_parity(i3c->addrs[data->index]));
> +
>  	return 0;
>  }
>
> --
> 2.43.0
>

  reply	other threads:[~2026-06-02 20:05 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 [this message]
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
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=ah83iknpm9uhdi4S@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

all inboxes | Powered by JetHome®