From: Troy Mitchell <troy.mitchell@linux.spacemit.com>
To: Alex Elder <elder@riscstar.com>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>,
Andi Shyti <andi.shyti@kernel.org>, Yixun Lan <dlan@gentoo.org>,
Troy Mitchell <troymitchell988@gmail.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH v4] i2c: spacemit: introduce pio for k1
Date: Mon, 15 Dec 2025 13:59:17 +0800 [thread overview]
Message-ID: <6ECB2C39812D3E23+aT-jFKR-o5RsJxD9@kernel.org> (raw)
In-Reply-To: <613db920-6025-43cb-a733-d58f65363caa@riscstar.com>
On Fri, Nov 07, 2025 at 09:50:26AM -0600, Alex Elder wrote:
> On 10/9/25 4:59 AM, Troy Mitchell wrote:
> > This patch introduces I2C PIO functionality for the Spacemit K1 SoC,
> > enabling the use of I2C in atomic context.
[...]
> > @@ -125,10 +127,14 @@ struct spacemit_i2c_dev {
> > enum spacemit_i2c_state state;
> > bool read;
> > + bool use_pio;
>
> This is fine, but you could maybe call it atomic (to match
> the callback funtion name).
>
> Actually, almost all uses of this field are negated, i.e.:
> if (!i2c->use_pio)
>
> Maybe you could use a name that doesn't require negation,
> like "can_block" for example.
Most of the negation is unnecessary; it's my code's behavior. I'll
modify the code behavior, not this variable. I believe this variable
directly reflects the hardware behavior. Therefore, I won't modify it
here.
- Troy
prev parent reply other threads:[~2025-12-15 6:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 9:59 [PATCH v4] i2c: spacemit: introduce pio for k1 Troy Mitchell
2025-11-05 22:29 ` Aurelien Jarno
2025-11-06 1:00 ` Troy Mitchell
2025-11-07 15:50 ` Alex Elder
2025-12-11 21:28 ` Aurelien Jarno
2025-12-15 2:52 ` Troy Mitchell
2025-12-15 5:42 ` Troy Mitchell
2025-12-15 5:59 ` Troy Mitchell [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=6ECB2C39812D3E23+aT-jFKR-o5RsJxD9@kernel.org \
--to=troy.mitchell@linux.spacemit.com \
--cc=andi.shyti@kernel.org \
--cc=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=spacemit@lists.linux.dev \
--cc=troymitchell988@gmail.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