public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: liudingyuan <liudingyuan@huawei.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: yangyicong <yangyicong@huawei.com>,
	"Fangjian (Jay)" <f.fangjian@huawei.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: 答复: [PATCH v2 1/2] i2c: hisi: Optimized the value setting of maxwrite limit to fifo depth - 1
Date: Thu, 1 Feb 2024 07:47:50 +0000	[thread overview]
Message-ID: <cfa3d4012c0a4f8fa31e320829b76cb5@huawei.com> (raw)
In-Reply-To: <wcodkjjrkd5ujfr3gdpqik2ioibnafatmkltrxezpdcr3twtcc@t7wxlnudcsge>

Hi Andi

Yes, this is the only code change in version 2 compared to version 1. In addition,
in the commit description of PATCH v2 1/2 :
v1->v2
the threshold for FIFO empty interrupt 
->
the threshold for FIFO almost empty interrupt. 

In v2 2/2, there is no change.

Thanks,
Devyn
-----邮件原件-----
发件人: Andi Shyti <andi.shyti@kernel.org> 
发送时间: 2024年2月1日 14:52
收件人: liudingyuan <liudingyuan@huawei.com>
抄送: yangyicong <yangyicong@huawei.com>; Fangjian (Jay) <f.fangjian@huawei.com>; Jonathan Cameron <jonathan.cameron@huawei.com>; linux-i2c@vger.kernel.org
主题: Re: [PATCH v2 1/2] i2c: hisi: Optimized the value setting of maxwrite limit to fifo depth - 1

Hi Devyn,

...

>  static void hisi_i2c_xfer_msg(struct hisi_i2c_controller *ctlr)  {
> -	int max_write = HISI_I2C_TX_FIFO_DEPTH;
> +	int max_write = HISI_I2C_TX_FIFO_DEPTH - HISI_I2C_TX_F_AE_THRESH;

this is one of the differences.

Reviewed-by: Yicong Yang <yangyicong@hisilicon.com>
Reviewed-by: Andi Shyti <andi.shyti@kernel.org> 

Thanks,
Andi

  reply	other threads:[~2024-02-01  7:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  6:13 [PATCH v2 0/2] i2c: hisi: Clear the interrupt status and optimize writing limitation Devyn Liu
2024-02-01  6:13 ` [PATCH v2 1/2] i2c: hisi: Optimized the value setting of maxwrite limit to fifo depth - 1 Devyn Liu
2024-02-01  6:51   ` Andi Shyti
2024-02-01  7:47     ` liudingyuan [this message]
2024-02-01  6:13 ` [PATCH v2 2/2] i2c: hisi: Add clearing tx aempty interrupt operation Devyn Liu
2024-02-01  6:52   ` Andi Shyti
2024-02-01  6:49 ` [PATCH v2 0/2] i2c: hisi: Clear the interrupt status and optimize writing limitation Andi Shyti
2024-02-01  7:48   ` 答复: " liudingyuan
2024-02-01 23:33 ` Andi Shyti

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=cfa3d4012c0a4f8fa31e320829b76cb5@huawei.com \
    --to=liudingyuan@huawei.com \
    --cc=andi.shyti@kernel.org \
    --cc=f.fangjian@huawei.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=yangyicong@huawei.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