public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Liu Peibao <loven.liu@jaguarmicro.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Jan Dabros <jsd@semihalf.com>,
	"xiaowu . ding" <xiaowu.ding@jaguarmicro.com>,
	Angus Chen <angus.chen@jaguarmicro.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND TO CC MAILLIST] i2c: designware: fix master holding SCL low when I2C_DYNAMIC_TAR_UPDATE not set
Date: Wed, 6 Nov 2024 15:27:42 +0800	[thread overview]
Message-ID: <d2abc63a-884d-4d48-b652-56989e55d0cd@jaguarmicro.com> (raw)
In-Reply-To: <anhqlov5vdsicmopulnvbaerhctjaauwsvl6nlc3llsh4hi5sn@d3jmeqxnlhpl>

On 2024/11/6 4:30, Andi Shyti wrote:
> External Mail: This email originated from OUTSIDE of the organization!
> Do not click links, open attachments or provide ANY information unless you recognize the sender and know the content is safe.
> 
> 
> Hi Liu,
> 
> On Fri, Nov 01, 2024 at 06:18:36PM +0800, Liu Peibao wrote:
>> On 2024/11/1 16:44, Andy Shevchenko wrote:
>>> External Mail: This email originated from OUTSIDE of the organization!
>>> Do not click links, open attachments or provide ANY information unless you recognize the sender and know the content is safe.
>>>
>>> On Fri, Nov 01, 2024 at 04:12:43PM +0800, Liu Peibao wrote:
>>>> When Tx FIFO empty and last command with no STOP bit set, the master
>>>> holds SCL low. If I2C_DYNAMIC_TAR_UPDATE is not set, BIT(13) MST_ON_HOLD
>>>> of IC_RAW_INTR_STAT is not Enabled, causing the __i2c_dw_disable()
>>>> timeout. This is quiet similar as commit 2409205acd3c ("i2c: designware:
>>>> fix __i2c_dw_disable() in case master is holding SCL low") mentioned.
>>>> Check BIT(7) MST_HOLD_TX_FIFO_EMPTY in IC_STATUS also which is available
>>>> when IC_STAT_FOR_CLK_STRETCH is set.
>>>
>>> Who are those people? Why Angus Chen is not a committer of the change?
>>> Please, consult with the Submitting Patches documentation to clarify on these
>>> tags.
>>>
>>
>> We have discussed and analyzed this issue together. I developed this patch.
>> This patch was also reviewed by Angus Chen and Xiaowu Ding.
> 
> The tag list follows a specific order: tags are sorted
> sequentially, with the last Signed-off-by (SoB) being the person
> sending the patch, which is your email.
> 
> The other SoBs are fine, but if someone contributed to
> development, consider using "Co-developed-by" instead.
> 
> If someone tested the patch, use "Tested-by"; if they reviewed
> it, use "Reviewed-by"; and if they simply agreed with the
> change, use "Acked-by."
> 
> Please ensure that "Reviewed-by," "Tested-by," or "Acked-by"
> tags are visible in the mailing list. I do not typically accept
> offline R-b, T-b, or A-b.
> 
> This is why Andy asked about those contributors. Three SoBs can
> seem unusual, but it's acceptable if justified. Reviewers may
> ask for clarification, and it's fine to specify contributors'
> roles. You can also provide extra details after the "---"
> delimiter.
>

I think this tag list should be much better than the original. ^-^

Fixes: 2409205acd3c ("i2c: designware: fix __i2c_dw_disable() in case master is holding SCL low")
Co-developed-by: xiaowu.ding <xiaowu.ding@jaguarmicro.com>
Signed-off-by: xiaowu.ding <xiaowu.ding@jaguarmicro.com>
Co-developed-by: Angus Chen <angus.chen@jaguarmicro.com>
Signed-off-by: Angus Chen <angus.chen@jaguarmicro.com>
Signed-off-by: Liu Peibao <loven.liu@jaguarmicro.com>

>> And in this case, should I replace the "SoBs" with "Reviewed-by"?
>>
>>> Also, sounds to me that Fixes tag is needed.
>>>
>>
>> How about this tag:
>> Fixes: 2409205acd3c ("i2c: designware: fix __i2c_dw_disable() in case master is holding SCL low")
> 
> Sounds reasonable.
> 
> For accepting this patch I need an ack from either Andy, Jarkko
> or Mika.
> 
> As long as the fixes are limited to the commit message there is
> no need to resend the patch.
> 
> Thanks,
> Andi

Got it!

BR,
Peibao

  reply	other threads:[~2024-11-06  7:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01  8:12 [PATCH RESEND TO CC MAILLIST] i2c: designware: fix master holding SCL low when I2C_DYNAMIC_TAR_UPDATE not set Liu Peibao
2024-11-01  8:44 ` Andy Shevchenko
2024-11-01 10:18   ` Liu Peibao
2024-11-05 20:30     ` Andi Shyti
2024-11-06  7:27       ` Liu Peibao [this message]
2024-11-06  9:46         ` Andi Shyti
2024-11-06 10:09           ` Liu Peibao
2024-11-06 11:53             ` Jarkko Nikula
2024-11-06 23:07               ` 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=d2abc63a-884d-4d48-b652-56989e55d0cd@jaguarmicro.com \
    --to=loven.liu@jaguarmicro.com \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=angus.chen@jaguarmicro.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jsd@semihalf.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=xiaowu.ding@jaguarmicro.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