From: Jisheng Zhang <jszhang@kernel.org>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>, Andi Shyti <andi.shyti@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: [PATCH 0/2] i2c: designware: Implement atomic transfer suppot
Date: Wed, 20 Aug 2025 23:31:23 +0800 [thread overview]
Message-ID: <20250820153125.22002-1-jszhang@kernel.org> (raw)
Implement atomic transfer support for designware i2c. This increases
complexity but is necessary for atomic I2C transfers required by some
hardware configurations, e.g., to trigger reboots on an external PMIC chip.
patch1 is bug fix
patch2 is the atomic transfer implementation patch.
Jisheng Zhang (2):
i2c: designware: Avoid taking clk_prepare mutex in PM callbacks
i2c: designware: Implement atomic transfer suppot
drivers/i2c/busses/i2c-designware-common.c | 47 +++++++++----
drivers/i2c/busses/i2c-designware-core.h | 5 +-
drivers/i2c/busses/i2c-designware-master.c | 80 +++++++++++++++++++---
3 files changed, 106 insertions(+), 26 deletions(-)
--
2.50.1
next reply other threads:[~2025-08-20 15:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 15:31 Jisheng Zhang [this message]
2025-08-20 15:31 ` [PATCH 1/2] i2c: designware: Avoid taking clk_prepare mutex in PM callbacks Jisheng Zhang
2025-08-20 16:05 ` Andy Shevchenko
2025-08-20 16:33 ` Jisheng Zhang
2025-08-21 12:45 ` Jarkko Nikula
2025-08-21 13:01 ` Andy Shevchenko
2025-08-21 16:32 ` Jisheng Zhang
2025-08-22 9:18 ` Andy Shevchenko
2025-08-22 9:34 ` Andy Shevchenko
2025-08-22 13:56 ` Jisheng Zhang
2025-08-22 23:51 ` Jisheng Zhang
2025-08-20 15:31 ` [PATCH 2/2] i2c: designware: Implement atomic transfer suppot Jisheng Zhang
2025-08-20 17:00 ` 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=20250820153125.22002-1-jszhang@kernel.org \
--to=jszhang@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.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 \
/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;
as well as URLs for NNTP newsgroup(s).