[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <af35a533-2126-4a61-a6cd-31ed1e615f2b@linux.intel.com>
Date: Tue, 17 Oct 2023 11:33:34 +0300
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: Frank Li <Frank.Li@....com>, alexandre.belloni@...tlin.com,
miquel.raynal@...tlin.com, conor.culhane@...vaco.com,
joe@...ches.com, linux-i3c@...ts.infradead.org,
linux-kernel@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH 4/5] i3c: master: svc return actual transfer data len
Hi
On 10/16/23 18:46, Frank Li wrote:
> I3C allow devices early terminate data transfer. So set "actual" to
> indicate how much data get by i3c_priv_xfer.
>
> Signed-off-by: Frank Li <Frank.Li@....com>
> ---
> drivers/i3c/master/svc-i3c-master.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/i3c/master/svc-i3c-master.c b/drivers/i3c/master/svc-i3c-master.c
> index 3570b709cf60..444825aafa6f 100644
> --- a/drivers/i3c/master/svc-i3c-master.c
> +++ b/drivers/i3c/master/svc-i3c-master.c
> @@ -138,6 +138,7 @@ struct svc_i3c_cmd {
> const void *out;
> unsigned int len;
> unsigned int actual_len;
> + struct i3c_priv_xfer *xfer;
> bool continued;
> };
>
I'm thinking would it make sense to combine this and previous patch by
removing the read_len/actual_len variable from this structure and use
the added one (by the patch 2/5) from "struct i3c_priv_xfer" directly?
Powered by blists - more mailing lists