From: Troy Mitchell <troy.mitchell@linux.spacemit.com>
To: Andi Shyti <andi.shyti@kernel.org>, Yixun Lan <dlan@gentoo.org>,
Alex Elder <elder@riscstar.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Michael Opdenacker <michael.opdenacker@rootcommit.com>,
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,
Troy Mitchell <troy.mitchell@linux.spacemit.com>
Subject: [PATCH v6 0/2] i2c: spacemit: introduce pio for k1
Date: Thu, 08 Jan 2026 15:52:10 +0800 [thread overview]
Message-ID: <20260108-k1-i2c-atomic-v6-0-41b132b70f68@linux.spacemit.com> (raw)
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 | 314 +++++++++++++++++++++++++++++++++-----------
1 file changed, 237 insertions(+), 77 deletions(-)
---
base-commit: 003e84792ce811256114dee4f4ecc1cafdab2b0d
change-id: 20250814-k1-i2c-atomic-f1a90cd34364
Best regards,
--
Troy Mitchell <troy.mitchell@linux.spacemit.com>
next reply other threads:[~2026-01-08 7:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 7:52 Troy Mitchell [this message]
2026-01-08 7:52 ` [PATCH v6 1/2] i2c: spacemit: move i2c_xfer_msg() Troy Mitchell
2026-01-08 7:52 ` [PATCH v6 2/2] i2c: spacemit: introduce pio for k1 Troy Mitchell
2026-01-14 15:47 ` Andi Shyti
2026-01-15 17:02 ` Alex Elder
2026-02-07 13:49 ` Troy Mitchell
2026-01-15 17:02 ` Alex Elder
2026-02-07 13:57 ` Troy Mitchell
2026-01-08 19:21 ` [PATCH v6 0/2] " Aurelien Jarno
2026-01-27 22:51 ` Aurelien Jarno
2026-01-29 9:58 ` Troy Mitchell
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=20260108-k1-i2c-atomic-v6-0-41b132b70f68@linux.spacemit.com \
--to=troy.mitchell@linux.spacemit.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=michael.opdenacker@rootcommit.com \
--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
all inboxes | Powered by JetHome®