From: Frank Li <Frank.li@nxp.com>
To: Stanley Chu <stanley.chuys@gmail.com>
Cc: miquel.raynal@bootlin.com, alexandre.belloni@bootlin.com,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, tomer.maimon@nuvoton.com,
kwliu@nuvoton.com, yschu@nuvoton.com
Subject: Re: [PATCH RESEND v2 3/4] i3c: master: svc: Fix npcm845 FIFO empty issue
Date: Thu, 20 Feb 2025 12:56:04 -0500 [thread overview]
Message-ID: <Z7dstL6FBYh3/cz7@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250220061107.1718239-4-yschu@nuvoton.com>
On Thu, Feb 20, 2025 at 02:11:06PM +0800, Stanley Chu wrote:
> From: Stanley Chu <yschu@nuvoton.com>
>
> I3C HW stalls the write transfer if the transmit FIFO becomes empty,
> when new data is written to FIFO, I3C HW resumes the transfer but the
> first transmitted data bit may have the wrong value.
> Fill the FIFO in advance to prevent FIFO from becoming empty.
>
> Signed-off-by: Stanley Chu <yschu@nuvoton.com>
> ---
You missed do_daa part.
> drivers/i3c/master/svc-i3c-master.c | 22 ++++++++++++++++++----
> 1 file changed, 18 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i3c/master/svc-i3c-master.c b/drivers/i3c/master/svc-i3c-master.c
> index c58440061d5a..2140da3f5187 100644
> --- a/drivers/i3c/master/svc-i3c-master.c
> +++ b/drivers/i3c/master/svc-i3c-master.c
> @@ -1196,8 +1196,8 @@ static int svc_i3c_master_read(struct svc_i3c_master *master,
> return offset;
> }
>
> -static int svc_i3c_master_write(struct svc_i3c_master *master,
> - const u8 *out, unsigned int len)
> +static int svc_i3c_master_write(struct svc_i3c_master *master, const u8 *out,
> + unsigned int len, bool last)
> {
> int offset = 0, ret;
> u32 mdctrl;
> @@ -1214,7 +1214,7 @@ static int svc_i3c_master_write(struct svc_i3c_master *master,
> * The last byte to be sent over the bus must either have the
> * "end" bit set or be written in MWDATABE.
> */
> - if (likely(offset < (len - 1)))
> + if (likely(offset < (len - 1)) || !last)
> writel(out[offset++], master->regs + SVC_I3C_MWDATAB);
> else
> writel(out[offset++], master->regs + SVC_I3C_MWDATABE);
> @@ -1245,6 +1245,19 @@ static int svc_i3c_master_xfer(struct svc_i3c_master *master,
> SVC_I3C_MCTRL_RDTERM(*actual_len),
> master->regs + SVC_I3C_MCTRL);
>
> + if ((master->quirks & SVC_I3C_QUIRK_FIFO_EMPTY) && !rnw && xfer_len) {
> + unsigned int len = xfer_len;
len = max_t(u32, xfer_len, SVC_I3C_FIFO_SIZE);
> +
> + if (xfer_len > SVC_I3C_FIFO_SIZE)
> + len = SVC_I3C_FIFO_SIZE;
> + ret = svc_i3c_master_write(master, out, len,
> + xfer_len <= SVC_I3C_FIFO_SIZE);
> + if (ret < 0)
> + goto emit_stop;
> + xfer_len -= len;
> + out += len;
> + }
> +
> ret = readl_poll_timeout(master->regs + SVC_I3C_MSTATUS, reg,
> SVC_I3C_MSTATUS_MCTRLDONE(reg), 0, 1000);
> if (ret)
> @@ -1306,7 +1319,7 @@ static int svc_i3c_master_xfer(struct svc_i3c_master *master,
> if (rnw)
> ret = svc_i3c_master_read(master, in, xfer_len);
> else
> - ret = svc_i3c_master_write(master, out, xfer_len);
> + ret = svc_i3c_master_write(master, out, xfer_len, true);
> if (ret < 0)
> goto emit_stop;
>
> @@ -1333,6 +1346,7 @@ static int svc_i3c_master_xfer(struct svc_i3c_master *master,
> emit_stop:
> svc_i3c_master_emit_stop(master);
> svc_i3c_master_clear_merrwarn(master);
> + svc_i3c_master_flush_fifo(master);
>
> return ret;
> }
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-02-20 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 6:11 [PATCH RESEND v2 0/4] Add support for Nuvoton npcm845 i3c controller Stanley Chu
2025-02-20 6:11 ` [PATCH RESEND v2 1/4] dt-bindings: i3c: silvaco: Add npcm845 compatible string Stanley Chu
2025-02-20 8:19 ` Krzysztof Kozlowski
2025-02-20 6:11 ` [PATCH RESEND v2 2/4] i3c: master: svc: Add support for Nuvoton npcm845 i3c Stanley Chu
2025-02-20 17:40 ` Frank Li
2025-02-20 6:11 ` [PATCH RESEND v2 3/4] i3c: master: svc: Fix npcm845 FIFO empty issue Stanley Chu
2025-02-20 17:56 ` Frank Li [this message]
2025-02-20 6:11 ` [PATCH RESEND v2 4/4] i3c: master: svc: Fix npcm845 invalid slvstart event Stanley Chu
2025-02-20 17:43 ` Frank Li
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=Z7dstL6FBYh3/cz7@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=kwliu@nuvoton.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=stanley.chuys@gmail.com \
--cc=tomer.maimon@nuvoton.com \
--cc=yschu@nuvoton.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