public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Liu Kimriver/刘金河" <kimriver.liu@siengine.com>
Cc: "jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>,
	"mika.westerberg@linux.intel.com"
	<mika.westerberg@linux.intel.com>,
	"jsd@semihalf.com" <jsd@semihalf.com>,
	"andi.shyti@kernel.org" <andi.shyti@kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8] i2c: designware: fix master is holding SCL low while ENABLE bit is disabled
Date: Tue, 10 Sep 2024 13:45:06 +0300	[thread overview]
Message-ID: <ZuAjMmr7q4f8VJpA@smile.fi.intel.com> (raw)
In-Reply-To: <743187d2fde54a9ebf86d42e29eadfb4@siengine.com>

On Tue, Sep 10, 2024 at 09:38:53AM +0000, Liu Kimriver/刘金河 wrote:
> >From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> 
> >Sent: 2024年9月10日 17:03
> >To: Liu Kimriver/刘金河 <kimriver.liu@siengine.com>
> >On Tue, Sep 10, 2024 at 02:13:09PM +0800, Kimriver Liu wrote:

...

> >master --> controller
> 
>  Update it in V9

Also in the Subject.

...

> >> holding SCL low. If ENABLE bit is disabled, the software need
> >> enable it before trying to issue ABORT bit. otherwise,
> >> the controller ignores any write to ABORT bit.
> 
> >Fixes tag?
> 
>  Patch rebase:  on Linux v6.11.0-rc6 (89f5e14d05b)

No, this one is done by understanding where the problem appear first.
What you mentioned above may be achieved by using --base option when
format the patch.

...

> >> +static bool i2c_dw_is_master_idling(struct dw_i2c_dev *dev)
> 
> >Sorry if I made a mistake, but again, looking at the usage you have again
> >negation here and there...
> 
> >	i2c_dw_is_controller_active
> 
> > (note new terminology, dunno if it makes sense start using it in function
> > names, as we have more of them following old style)
> 
>  Last week , You suggested that I used this i2c_dw_is_master_idling(dev)

Yes, sorry about that. I did maybe not clearly get how it is going to
look like.

> >> +{
> >> +	u32 status;
> >> +
> >> +	regmap_read(dev->map, DW_IC_STATUS, &status);
> >> +	if (!(status & DW_IC_STATUS_MASTER_ACTIVITY))
> >> +		return true;
> 
> 		return false;
> 
> >> +	return !regmap_read_poll_timeout(dev->map, DW_IC_STATUS, status,
> >> +			!(status & DW_IC_STATUS_MASTER_ACTIVITY),
> >> +			1100, 20000);
> 
> >...and drop !.
> 
>  We reproduce this issue in RTL simulation(About(~1:500) in our soc). It is necessary
>  to add waiting DW_IC_STATUS_MASTER_ACTIVITY idling before disabling I2C when 
>  I2C transfer completed.  as described in the DesignWare
>  I2C databook(Flowchart for DW_apb_i2c Controller)

Cool, but here I'm talking purely about inverting the logic (with renaming),
nothing more.

> >> +}

...

> >> +	/*
> >> +	 * This happens rarely and is hard to reproduce. Debug trace
> 
> >Rarely how? Perhaps put a ration in the parentheses, like
> 
> >"...rarely (~1:100)..."
>  About(~1:500) in our soc

Yes, what I showed was just an example, put the real numbers into the comment.

> >> +	 * showed that IC_STATUS had value of 0x23 when STOP_DET occurred,
> >> +	 * if disable IC_ENABLE.ENABLE immediately that can result in
> >> +	 * IC_RAW_INTR_STAT.MASTER_ON_HOLD holding SCL low.
> >> +	 */
> >> +	if (!i2c_dw_is_master_idling(dev))
> 
> >...and here
> 
> >	if (i2c_dw_is_controller_active(dev))
> 
> >But please double check that I haven't made any mistakes in all this logic.
> 
>  Last week , You suggested that I used this i2c_dw_is_master_idling(dev)
>  keep using i2c_dw_is_master_idling(dev) , Ok?

See above.

> >> +		dev_err(dev->dev, "I2C master not idling\n");

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2024-09-10 10:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10  6:13 [PATCH v8] i2c: designware: fix master is holding SCL low while ENABLE bit is disabled Kimriver Liu
2024-09-10  9:02 ` Jarkko Nikula
2024-09-10  9:53   ` Liu Kimriver/刘金河
2024-09-10  9:02 ` Andy Shevchenko
2024-09-10  9:38   ` Liu Kimriver/刘金河
2024-09-10 10:45     ` Andy Shevchenko [this message]
2024-09-10 11:43       ` Liu Kimriver/刘金河
2024-09-10 11:59         ` Andy Shevchenko
2024-09-11  1:37           ` Liu Kimriver/刘金河
2024-09-11 14:42             ` Andy Shevchenko
2024-09-10 11:20     ` Jarkko Nikula
2024-09-10 11:54       ` Liu Kimriver/刘金河

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=ZuAjMmr7q4f8VJpA@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jsd@semihalf.com \
    --cc=kimriver.liu@siengine.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@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