From: "William A. Kennington III" <william@wkennington.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] i2c: designware: Introduce shutdown exported function
Date: Thu, 7 May 2026 11:48:38 -0700 [thread overview]
Message-ID: <b69efe0a-0760-4391-bc31-7a3ba2f297a6@wkennington.com> (raw)
In-Reply-To: <afxjpG8Gvh7FyC5z@ashevche-desk.local>
On 5/7/26 03:04, Andy Shevchenko wrote:
> On Thu, May 07, 2026 at 12:56:50AM -0700, William A. Kennington III wrote:
>> On 5/5/26 00:29, Andy Shevchenko wrote:
>>> On Mon, May 04, 2026 at 08:15:02PM +0000, William A. Kennington III wrote:
>>>> Introduce an exported shutdown function to safely shutdown the
>>>> DesignWare I2C controller.
>>>>
>>>> This shutdown hook gracefully sets the slave disable bit before disabling
>>>> the controller. This guarantees that any incoming requests from the master
>>>> are immediately NACKed during shutdown, preventing the bus from hanging.
> ...
>
>> Is this just language correction?
> I have asked for replacing 'slave'/'master' terminology to a new,
> inclusive one.
Yeah, this is exactly what I figured I just wanted to make sure I didn't
misunderstand. I updated all of those cases in all the patches.
> ...
>
>
>>>> + /*
>>>> + * We only need to handle shutdown for slave mode to ensure
>>>> + * we NACK any incoming master requests. Master mode cleanup
>>>> + * is handled after each transfer in i2c_dw_xfer.
>>> i2c_dw_xfer()
>>>
>>>> + */
>>> Since it's a newly added comment, can you switch to use inclusive language?
>>> Same for the whole series related to the commit messages, comments, and
>>> documentation.
> Same here and...
>
>>>> + /*
>>>> + * To quickly NACK the master during shutdown, we set the slave
>>>> + * disable bit while the controller is still enabled.
>>>> + */
> ...here.
>
> ...
>
>>>> +EXPORT_SYMBOL_GPL(i2c_dw_shutdown);
>>> Can we use namespace?
>> It already does use namespaces with
>>
>> `#define DEFAULT_SYMBOL_NAMESPACE "I2C_DW_COMMON"`
>>
>> I assume I should just keep it consistent as-is?
> Yep, thanks for pointing that out!
>
next prev parent reply other threads:[~2026-05-07 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 20:15 [PATCH v3 0/4] i2c: designware: Improve device disable handling William A. Kennington III
2026-05-04 20:15 ` [PATCH v3 1/4] i2c: designware: Introduce shutdown exported function William A. Kennington III
2026-05-05 7:29 ` Andy Shevchenko
2026-05-07 7:56 ` William A. Kennington III
2026-05-07 10:04 ` Andy Shevchenko
2026-05-07 18:48 ` William A. Kennington III [this message]
2026-05-04 20:15 ` [PATCH v3 2/4] i2c: designware: Convert PCI driver to use shutdown hook William A. Kennington III
2026-05-05 7:31 ` Andy Shevchenko
2026-05-04 20:15 ` [PATCH v3 3/4] i2c: designware: Convert platform " William A. Kennington III
2026-05-05 7:31 ` Andy Shevchenko
2026-05-04 20:15 ` [PATCH v3 4/4] i2c: designware: Handle active slave cleanly William A. Kennington III
2026-05-05 7:34 ` Andy Shevchenko
2026-05-05 7:35 ` [PATCH v3 0/4] i2c: designware: Improve device disable handling Andy Shevchenko
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=b69efe0a-0760-4391-bc31-7a3ba2f297a6@wkennington.com \
--to=william@wkennington.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@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 \
/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