public inbox for linux-i3c@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Joshua Yeong <joshua.yeong@starfivetech.com>
Cc: <alexandre.belloni@bootlin.com>, <linux-i3c@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] i3c: Add fallback method for GETMXDS CCC
Date: Tue, 14 Nov 2023 09:19:56 +0100	[thread overview]
Message-ID: <20231114091956.0b8dd6c5@xps-13> (raw)
In-Reply-To: <20231114033430.9623-2-joshua.yeong@starfivetech.com>

Hi Joshua,

joshua.yeong@starfivetech.com wrote on Tue, 14 Nov 2023 11:34:30 +0800:

> Some I3C hardware will report error when incorrect length is received from

					an

> device. GETMXDS CCC are availble in 2 formats; without turnaround time (format

			  available		:

> 1) and with turnaround time (format 2). There is no mechanics to determine which
> format is supported by device. In case sending GETMXDS CCC format 2 resulted

				So in case?

> failure, try sending GETMXDS CCC format 1 instead.

in a

> 
> Signed-off-by: Joshua Yeong <joshua.yeong@starfivetech.com>
> ---
>  drivers/i3c/master.c | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
> index 0cdc94e4cb77..2fc04d97f07e 100644
> --- a/drivers/i3c/master.c
> +++ b/drivers/i3c/master.c
> @@ -1099,8 +1099,16 @@ static int i3c_master_getmxds_locked(struct i3c_master_controller *master,
>  
>  	i3c_ccc_cmd_init(&cmd, true, I3C_CCC_GETMXDS, &dest, 1);
>  	ret = i3c_master_send_ccc_cmd_locked(master, &cmd);
> -	if (ret)
> -		goto out;
> +	if (ret) {
> +		/*
		 ^
Wrong alignment of the starts below
		v
> +		* Retry when the device does not support max read turnaround
> +		* while expecting shorter length from this CCC command

period?

> +		*/
> +		dest->payload.len -= 3;
> +		ret = i3c_master_send_ccc_cmd_locked(master, &cmd);
> +		if (ret)
> +			goto out;
> +	}

I believe this is a per-device configuration and we should save this in
order to only fail once, no?

>  
>  	if (dest.payload.len != 2 && dest.payload.len != 5) {
>  		ret = -EIO;


Thanks,
Miquèl

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2023-11-14  8:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  3:34 [PATCH v2 0/1] Fallback mechanism for GETMXDS CCC Joshua Yeong
2023-11-14  3:34 ` [PATCH v2 1/1] i3c: Add fallback method " Joshua Yeong
2023-11-14  8:19   ` Miquel Raynal [this message]
2023-11-14  8:42     ` Joshua Yeong
2023-11-14  8:56       ` 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=20231114091956.0b8dd6c5@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=joshua.yeong@starfivetech.com \
    --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