From: Joshua Yeong <joshua.yeong@starfivetech.com>
To: Frank Li <Frank.Li@nxp.com>, <miquel.raynal@bootlin.com>
Cc: <alexandre.belloni@bootlin.com>, <conor.culhane@silvaco.com>,
<imx@lists.linux.dev>, <joe@perches.com>,
<linux-i3c@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<zbigniew.lukwinski@linux.intel.com>
Subject: Re: [v5 resend 3/6] i3c: add actual_len in i3c_priv_xfer
Date: Wed, 20 Dec 2023 09:55:26 +0800 [thread overview]
Message-ID: <2cfc670f-56ad-4453-82f3-d72dcfd05840@starfivetech.com> (raw)
In-Reply-To: <20231201222532.2431484-4-Frank.Li@nxp.com>
On 02/12/2023 6:25 AM, Frank Li wrote:
> In MIPI I3C Specification:
>
> "Ninth Bit of SDR Target Returned (Read) Data as End-of-Data: In I2C, the
> ninth Data bit from Target to Controller is an ACK by the Controller. By
> contrast, in I3C this bit allows the Target to end a Read, and allows the
> Controller to Abort a Read. In SDR terms, the ninth bit of Read data is
> referred to as the T-Bit (for ‘Transition’)"
>
> I3C allow devices early terminate data transfer. So need "actual_len" field
> to indicate how much get by i3c_priv_xfer.
>
> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
>
> Notes:
> change from v4 to v5
> - Add Miquel review tag
>
> include/linux/i3c/device.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/i3c/device.h b/include/linux/i3c/device.h
> index 90fa83464f003..ef6217da8253b 100644
> --- a/include/linux/i3c/device.h
> +++ b/include/linux/i3c/device.h
> @@ -54,6 +54,7 @@ enum i3c_hdr_mode {
> * struct i3c_priv_xfer - I3C SDR private transfer
> * @rnw: encodes the transfer direction. true for a read, false for a write
> * @len: transfer length in bytes of the transfer
> + * @actual_len: actual length in bytes are transferred by the controller
> * @data: input/output buffer
> * @data.in: input buffer. Must point to a DMA-able buffer
> * @data.out: output buffer. Must point to a DMA-able buffer
> @@ -62,6 +63,7 @@ enum i3c_hdr_mode {
> struct i3c_priv_xfer {
> u8 rnw;
> u16 len;
What happens if I3C device does not terminate the T-Bit because it
expects extra length from master?
> + u16 actual_len;
> union {
> void *in;
> const void *out;
next prev parent reply other threads:[~2023-12-20 1:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 22:25 [v5 resend 0/6] i3c: master: some improvment for i3c master Frank Li
2023-12-01 22:25 ` [v5 resend 1/6] i3c: master: add enable(disable) hot join in sys entry Frank Li
2023-12-01 22:25 ` [v5 resend 2/6] i3c: master: svc: add hot join support Frank Li
2023-12-01 22:25 ` [v5 resend 3/6] i3c: add actual_len in i3c_priv_xfer Frank Li
2023-12-20 1:55 ` Joshua Yeong [this message]
2023-12-20 20:55 ` Frank Li
2023-12-01 22:25 ` [v5 resend 4/6] i3c: master: svc: rename read_len as actual_len Frank Li
2023-12-01 22:25 ` [v5 resend 5/6] i3c: master: svc: return actual transfer data len Frank Li
2023-12-01 22:25 ` [v5 resend 6/6] i3c: add API i3c_dev_gettstatus_format1() to get target device status Frank Li
2023-12-19 16:29 ` [v5 resend 0/6] i3c: master: some improvment for i3c master Frank Li
2024-01-08 0:03 ` (subset) " Alexandre Belloni
2024-01-09 1:19 ` Frank Li
2024-01-09 7:35 ` Alexandre Belloni
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=2cfc670f-56ad-4453-82f3-d72dcfd05840@starfivetech.com \
--to=joshua.yeong@starfivetech.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.culhane@silvaco.com \
--cc=imx@lists.linux.dev \
--cc=joe@perches.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=zbigniew.lukwinski@linux.intel.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