From: Troy Mitchell <troymitchell988@gmail.com>
To: "Aurelien Jarno" <aurelien@aurel32.net>,
"Troy Mitchell" <troy.mitchell@linux.spacemit.com>
Cc: "Andi Shyti" <andi.shyti@kernel.org>,
"Yixun Lan" <dlan@gentoo.org>, <linux-i2c@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<spacemit@lists.linux.dev>, "Alex Elder" <elder@riscstar.com>
Subject: Re: [PATCH v7 0/2] i2c: spacemit: introduce pio for k1
Date: Sun, 08 Feb 2026 22:53:07 +0800 [thread overview]
Message-ID: <DG9NZG0N2T3V.3DZ7YPCZAMD36@linux.spacemit.com> (raw)
In-Reply-To: <aYiR0VQXvBJDSQPh@aurel32.net>
On Sun Feb 8, 2026 at 9:38 PM CST, Aurelien Jarno wrote:
> Hi Troy,
>
> On 2026-02-07 23:08, Troy Mitchell wrote:
>> This patch introduces I2C PIO functionality for the Spacemit K1 SoC,
>> enabling the use of I2C in atomic context.
>>
>> Signed-off-by: Troy Mitchell <troy.mitchell@linux.spacemit.com>
>> ---
>> Troy Mitchell (2):
>> i2c: spacemit: move i2c_xfer_msg()
>> i2c: spacemit: introduce pio for k1
>>
>> drivers/i2c/busses/i2c-k1.c | 316 +++++++++++++++++++++++++++++++++-----------
>> 1 file changed, 236 insertions(+), 80 deletions(-)
>> ---
>> base-commit: 2fe0719258a48c204270366ef574066122e81924
>> change-id: 20260207-b4-k3-i2c-pio-318088c1b3b7
>>
>
> Thanks for this new version. This is:
>
> Tested-by: Aurelien Jarno <aurelien@aurel32.net>
Thanks for your tag. I have collected all of your tags in this version.
Apologies for the delay in sending this version.
I hope it hasn't held up your patch queue (p1-reboot)
- Troy
>
> Regards
> Aurelien
next prev parent reply other threads:[~2026-02-08 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 15:08 [PATCH v7 0/2] i2c: spacemit: introduce pio for k1 Troy Mitchell
2026-02-07 15:08 ` [PATCH v7 1/2] i2c: spacemit: move i2c_xfer_msg() Troy Mitchell
2026-02-07 15:08 ` [PATCH v7 2/2] i2c: spacemit: introduce pio for k1 Troy Mitchell
2026-02-08 13:38 ` [PATCH v7 0/2] " Aurelien Jarno
2026-02-08 14:53 ` Troy Mitchell [this message]
2026-03-11 18:42 ` Aurelien Jarno
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=DG9NZG0N2T3V.3DZ7YPCZAMD36@linux.spacemit.com \
--to=troymitchell988@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=aurelien@aurel32.net \
--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=troy.mitchell@linux.spacemit.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