From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kimriver liu <kimriver.liu@siengine.com>
Cc: jarkko.nikula@linux.intel.com, mika.westerberg@linux.intel.com,
jsd@semihalf.com, andi.shyti@kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: designware: fix master is holding SCL low while ENABLE bit is disabled
Date: Wed, 4 Sep 2024 15:55:29 +0300 [thread overview]
Message-ID: <ZthYwQfj3Vy6dU-S@smile.fi.intel.com> (raw)
In-Reply-To: <20240904064224.2394-1-kimriver.liu@siengine.com>
On Wed, Sep 04, 2024 at 02:42:24PM +0800, kimriver liu wrote:
> From: "kimriver.liu" <kimriver.liu@siengine.com>
>
> Failure in normal Stop operational path
>
> This failure happens rarely and is hard to reproduce. Debug
> trace showed that IC_STATUS had value of 0x23 when STOP_DET
> occurred, immediately disable ENABLE bit that can result in
> IC_RAW_INTR_STAT.MASTER_ON_HOLD holding SCL low.
>
> Failure in ENABLE bit is disabled path
>
> It was observed that master is holding SCL low and the
> IC_ENABLE is already disabled, Enable ABORT bit and
> ENABLE bit simultaneously cannot take effect.
>
> Check if the master is holding SCL low after ENABLE bit is
> already disabled. If SCL is held low, The software can set
> this ABORT bit only when ENABLE is already set,otherwise,
> the controller ignores any write to ABORT bit. When the
> abort is done, then proceed with disabling the controller.
>
> These kernel logs show up whenever an I2C transaction is
> attempted after this failure.
> i2c_designware e95e0000.i2c: timeout in disabling adapter
> i2c_designware e95e0000.i2c: timeout waiting for bus ready
>
> The patch can be fix the controller cannot be disabled while
> SCL is held low in ENABLE bit is already disabled.
...
> abort_needed = raw_intr_stats & DW_IC_INTR_MST_ON_HOLD;
> if (abort_needed) {
> + if (!enable) {
> + regmap_write(dev->map, DW_IC_ENABLE, DW_IC_ENABLE_ENABLE);
> + enable |= DW_IC_ENABLE_ENABLE;
> + usleep_range(25, 100);
fsleep()
And add a short comment to explain the chosen value.
> + }
...
> +static int i2c_dw_check_mst_activity(struct dw_i2c_dev *dev)
> +{
> + u32 status = 0;
> + int ret = 0;
> +
> + regmap_read(dev->map, DW_IC_STATUS, &status);
> + if (status & DW_IC_STATUS_MASTER_ACTIVITY) {
> + ret = regmap_read_poll_timeout(dev->map, DW_IC_STATUS, status,
> + !(status & DW_IC_STATUS_MASTER_ACTIVITY),
> + 1100, 20000);
> + if (ret)
> + dev_err(dev->dev, "i2c mst activity not idle %d\n", ret);
> + }
> +
> + return ret;
This can be rewritten as
u32 status = 0;
int ret;
regmap_read(dev->map, DW_IC_STATUS, &status);
if (!status & DW_IC_STATUS_MASTER_ACTIVITY))
return 0;
ret = regmap_read_poll_timeout(dev->map, DW_IC_STATUS, status,
!(status & DW_IC_STATUS_MASTER_ACTIVITY),
1100, 20000);
if (ret)
dev_err(dev->dev, "i2c mst activity not idle %d\n", ret);
return ret;
> +}
...
> + ret = i2c_dw_check_mst_activity(dev);
> + if (!ret)
> + __i2c_dw_disable_nowait(dev);
...but looking at the usage, I think the proper is to have the above to return
boolean. And also update the name to follow the usual pattern for boolean helpers.
static bool i2c_dw_is_mst_idling(struct dw_i2c_dev *dev)
...
if (i2c_dw_is_mst_idling(dev))
__i2c_dw_disable_nowait(dev);
...
Also what does the heck "mst" stand for? Please, use decrypted words in
function names and error messages..
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-04 12:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 6:42 [PATCH] i2c: designware: fix master is holding SCL low while ENABLE bit is disabled kimriver liu
2024-09-04 12:55 ` Andy Shevchenko [this message]
2024-09-05 2:46 ` 回复: " Liu Kimriver/刘金河
2024-09-05 7:32 ` Liu Kimriver/刘金河
-- strict thread matches above, loose matches on Subject: below --
2024-09-05 5:57 kimriver liu
2024-09-05 11:00 ` Andy Shevchenko
2024-09-05 7:42 kimriver liu
2024-09-05 11:03 ` Andy Shevchenko
2024-09-08 13:31 ` kernel test robot
2024-09-09 1:31 ` Liu Kimriver/刘金河
2024-09-09 6:50 ` Liu Kimriver/刘金河
2024-09-06 5:42 Kimriver Liu
2024-09-06 6:16 ` Mika Westerberg
2024-09-06 11:47 ` Andy Shevchenko
2024-09-08 2:12 ` Liu Kimriver/刘金河
2024-09-06 6:54 Kimriver Liu
2024-09-06 7:05 ` Mika Westerberg
2024-09-06 11:50 ` Andy Shevchenko
2024-09-06 7:47 Kimriver Liu
2024-09-06 8:07 ` Mika Westerberg
2024-09-06 11:52 ` Andy Shevchenko
2024-09-06 16:03 ` Andi Shyti
2024-09-06 21:34 ` Andi Shyti
2024-09-08 2:56 ` 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=ZthYwQfj3Vy6dU-S@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