From: Frank Li <Frank.li@nxp.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
Conor Culhane <conor.culhane@silvaco.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, stable@kernel.org
Subject: Re: [PATCH v5 0/6] I3C: master: svc: collect all patches to improve hotjoin stability
Date: Tue, 1 Oct 2024 12:54:08 -0400 [thread overview]
Message-ID: <ZvwpMBWzNjTXpPZF@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20241001-svc-i3c-hj-v5-0-480ab8aed849@nxp.com>
On Tue, Oct 01, 2024 at 12:02:49PM -0400, Frank Li wrote:
> This patches is splited from
> https://lore.kernel.org/linux-i3c/ZvrAuOBLgi+HtrPD@lizhi-Precision-Tower-5810/T/#t
>
> It needs more discussion about dt assign address issue about i3c framework.
>
> This series is svc driver improvement and bug fixes for hotjoin. It fixes
> all kinds hotjoin problem when 2 devices random hotjoin and A normal data
> transfer is on going.
>
> This patch version start from v5, which exact the same as old series's v4.
>
> See each patches for detail issue.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> Frank Li (6):
> i3c: master: svc: use repeat start when IBI WIN happens
> i3c: master: svc: manually emit NACK/ACK for hotjoin
> i3c: master: svc: need check IBIWON for dynamtica address assign
Alex:
I am not sure why linux-i3c mail list truncate above 3 patches
https://lore.kernel.org/linux-i3c/
but other mail list include all patches.
https://lore.kernel.org/imx/20241001-svc-i3c-hj-v5-0-480ab8aed849@nxp.com/T/#t
Frank
> i3c: master: svc: use spin_lock_irqsave at svc_i3c_master_ibi_work()
> i3c: master: svc: wait for Manual ACK/NACK Done before next step
> i3c: master: svc: fix possible assignment of the same address to two devices
>
> drivers/i3c/master/svc-i3c-master.c | 122 +++++++++++++++++++++++++++---------
> 1 file changed, 93 insertions(+), 29 deletions(-)
> ---
> base-commit: 77df9e4bb2224d8ffbddec04c333a9d7965dad6c
> change-id: 20241001-svc-i3c-hj-bbaba68cf1ea
>
> Best regards,
> ---
> Frank Li <Frank.Li@nxp.com>
>
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2024-10-01 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 16:02 [PATCH v5 0/6] I3C: master: svc: collect all patches to improve hotjoin stability Frank Li
2024-10-01 16:02 ` [PATCH v5 1/6] i3c: master: svc: use repeat start when IBI WIN happens Frank Li
2024-10-01 16:02 ` [PATCH v5 2/6] i3c: master: svc: manually emit NACK/ACK for hotjoin Frank Li
2024-10-01 16:02 ` [PATCH v5 3/6] i3c: master: svc: need check IBIWON for dynamtica address assign Frank Li
2024-10-01 20:13 ` Miquel Raynal
2024-10-01 16:02 ` [PATCH v5 4/6] i3c: master: svc: use spin_lock_irqsave at svc_i3c_master_ibi_work() Frank Li
2024-10-01 20:15 ` Miquel Raynal
2024-10-01 20:28 ` Frank Li
2024-10-01 16:02 ` [PATCH v5 5/6] i3c: master: svc: wait for Manual ACK/NACK Done before next step Frank Li
2024-10-01 20:15 ` Miquel Raynal
2024-10-01 16:02 ` [PATCH v5 6/6] i3c: master: svc: fix possible assignment of the same address to two devices Frank Li
2024-10-01 16:54 ` Frank Li [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=ZvwpMBWzNjTXpPZF@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.culhane@silvaco.com \
--cc=imx@lists.linux.dev \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=stable@kernel.org \
/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