public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: "Leilk Liu (刘磊)" <Leilk.Liu@mediatek.com>
To: "andi.shyti@kernel.org" <andi.shyti@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"wsa@kernel.org" <wsa@kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"Liguo Zhang (张立国)" <Liguo.Zhang@mediatek.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"Qii Wang (王琪)" <Qii.Wang@mediatek.com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH] i2c: mediatek: fix potential incorrect use of I2C_MASTER_WRRD
Date: Mon, 1 Sep 2025 09:25:20 +0000	[thread overview]
Message-ID: <008e347509c5f2e9a6ec9d2343be85a7838ac9d5.camel@mediatek.com> (raw)
In-Reply-To: <cf5wxalhd2536cxnj7zn2jngly5dmvoknjnb2gbq6mzqff4tgp@4syhblgi35yu>

On Tue, 2025-08-19 at 20:09 -0100, Andi Shyti wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
Hi Andi, sorry for late reply.

> Hi Leilk,
> 
> On Sat, Aug 16, 2025 at 03:53:54PM +0800, Leilk Liu wrote:
> > From: "Leilk.Liu" <leilk.liu@mediatek.com>
> > 
> > The old IC does not support the I2C_MASTER_WRRD (write-then-read)
> > function, but the current code’s handling of i2c->auto_restart may
> > potentially lead to entering the I2C_MASTER_WRRD software flow,
> > resulting in unexpected bugs.
> 
> do you mean unexpected behaviour?
sure.

> 
> > Instead of repurposing the auto_restart flag, add a separate flag
> > to signal I2C_MASTER_WRRD operations.
> > 
> > Also fix handling of msgs. If the operation (i2c->op) is
> > I2C_MASTER_WRRD, then the msgs pointer is incremented by 2.
> > For all other operations, msgs is simply incremented by 1.
> > 
> > Fixes: 173b77e8d8fe ("i2c: mediatek: add i2c first write then read
> > optimization")
> > 
> 
> No need for blank line here. BTW, this doesn't look the commit
> that is introducing the issue.
> 
OK.
Fixes:b2ed11e224a2 ("I2C: mediatek: Add driver for MediaTek MT8173 I2C
controller")

> > Signed-off-by: Leilk.Liu <leilk.liu@mediatek.com>
> > ---
> >  drivers/i2c/busses/i2c-mt65xx.c | 17 ++++++++++-------
> >  1 file changed, 10 insertions(+), 7 deletions(-)
> > 
> > diff --git a/drivers/i2c/busses/i2c-mt65xx.c
> > b/drivers/i2c/busses/i2c-mt65xx.c
> > index ab456c3717db..dee40704825c 100644
> > --- a/drivers/i2c/busses/i2c-mt65xx.c
> > +++ b/drivers/i2c/busses/i2c-mt65xx.c
> > @@ -1243,6 +1243,7 @@ static int mtk_i2c_transfer(struct
> > i2c_adapter *adap,
> >  {
> >       int ret;
> >       int left_num = num;
> > +     bool write_then_read_en = false;
> >       struct mtk_i2c *i2c = i2c_get_adapdata(adap);
> > 
> >       ret = clk_bulk_enable(I2C_MT65XX_CLK_MAX, i2c->clocks);
> > @@ -1256,6 +1257,7 @@ static int mtk_i2c_transfer(struct
> > i2c_adapter *adap,
> >               if (!(msgs[0].flags & I2C_M_RD) && (msgs[1].flags &
> > I2C_M_RD) &&
> >                   msgs[0].addr == msgs[1].addr) {
> >                       i2c->auto_restart = 0;
> > +                     write_then_read_en = true;
> 
> why don't we set "i2c->op = I2C_MASTER_WRRD" here and avoid an
> extra flag?
> 
we need to set "i2c->op" again in the following code, so an extra flag
is necessary.

> Thanks,
> Andi
> 
> >               }
> >       }
> > 

      reply	other threads:[~2025-09-01  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16  7:53 [PATCH] i2c: mediatek: fix potential incorrect use of I2C_MASTER_WRRD Leilk Liu
2025-08-18  3:53 ` Chen-Yu Tsai
2025-08-19 21:09 ` Andi Shyti
2025-09-01  9:25   ` Leilk Liu (刘磊) [this message]

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=008e347509c5f2e9a6ec9d2343be85a7838ac9d5.camel@mediatek.com \
    --to=leilk.liu@mediatek.com \
    --cc=Liguo.Zhang@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=Qii.Wang@mediatek.com \
    --cc=andi.shyti@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=wsa@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