From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: Conor Culhane <conor.culhane@silvaco.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-i3c@lists.infradead.org (moderated list:SILVACO I3C
DUAL-ROLE MASTER), linux-kernel@vger.kernel.org (open list),
imx@lists.linux.dev
Subject: Re: [PATCH 2/2] i3c: master: svc: fix probe failure when no i3c device exist
Date: Tue, 29 Aug 2023 11:16:11 +0200 [thread overview]
Message-ID: <20230829111611.12f91348@xps-13> (raw)
In-Reply-To: <20230828192502.3525418-2-Frank.Li@nxp.com>
Hi Frank,
Frank.Li@nxp.com wrote on Mon, 28 Aug 2023 15:25:02 -0400:
> If there are not i3c device, all ccc command will get NACK. Set
no NACKed?
> i3c_ccc_cmd::err as I3C_ERROR_M2.
This sentence should come last and be slightly more explicit.
> Return success when no i3c device found at svc_i3c_master_do_daa_locked().
Please explain why this is important/useful.
> Fixes: dd3c52846d59 ("i3c: master: svc: Add Silvaco I3C master driver")
Shall we consider a backport into stable kernels?
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> drivers/i3c/master/svc-i3c-master.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/i3c/master/svc-i3c-master.c b/drivers/i3c/master/svc-i3c-master.c
> index 770b40e28015e..a5620103acb73 100644
> --- a/drivers/i3c/master/svc-i3c-master.c
> +++ b/drivers/i3c/master/svc-i3c-master.c
> @@ -789,6 +789,9 @@ static int svc_i3c_master_do_daa_locked(struct svc_i3c_master *master,
> */
> break;
> } else if (SVC_I3C_MSTATUS_NACKED(reg)) {
> + /* No I3C devices attached */
> + if (dev_nb == 0)
> + break;
\n ?
> /*
> * A slave device nacked the address, this is
> * allowed only once, DAA will be stopped and
> @@ -1263,11 +1266,17 @@ static int svc_i3c_master_send_ccc_cmd(struct i3c_master_controller *m,
> {
> struct svc_i3c_master *master = to_svc_i3c_master(m);
> bool broadcast = cmd->id < 0x80;
> + int ret;
>
> if (broadcast)
> - return svc_i3c_master_send_bdcast_ccc_cmd(master, cmd);
> + ret = svc_i3c_master_send_bdcast_ccc_cmd(master, cmd);
> else
> - return svc_i3c_master_send_direct_ccc_cmd(master, cmd);
> + ret = svc_i3c_master_send_direct_ccc_cmd(master, cmd);
> +
> + if (ret)
> + cmd->err = I3C_ERROR_M2;
> +
> + return ret;
> }
>
> static int svc_i3c_master_priv_xfers(struct i3c_dev_desc *dev,
Thanks,
Miquèl
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2023-08-29 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 19:25 [PATCH 1/2] i3c: master: fixes i3c bus driver probe failure if no i3c device attached Frank Li
2023-08-28 19:25 ` [PATCH 2/2] i3c: master: svc: fix probe failure when no i3c device exist Frank Li
2023-08-29 9:16 ` Miquel Raynal [this message]
2023-08-29 15:26 ` Frank Li
2023-08-30 8:52 ` Miquel Raynal
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=20230829111611.12f91348@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=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 \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).