From: Francesco Dolcini <francesco@dolcini.it>
To: Dong Aisheng <aisheng.dong@nxp.com>,
Andi Shyti <andi.shyti@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
linux-i2c@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] i2c: lpi2c: implement master_xfer_atomic callback
Date: Thu, 26 Jun 2025 09:58:37 +0200 [thread overview]
Message-ID: <20250626075837.GA9216@francesco-nb> (raw)
In-Reply-To: <20250523082931.23170-1-francesco@dolcini.it>
Hello,
On Fri, May 23, 2025 at 10:29:29AM +0200, Francesco Dolcini wrote:
> From: Francesco Dolcini <francesco.dolcini@toradex.com>
>
> This series adds atomic operations support to the imx-lpi2c driver and split
> the previous v3 patch into two separate patches.
>
> The first patch replaces the open-coded polling loops with readl_poll_timeout.
> This improves readability and consistency, and prepares the code for
> integration of the second patch, while maintaining the same functionality.
>
> The second patch implements the .master_xfer_atomic() callback, enabling
> support for atomic I2C transfers.
Just a gentle ping to not forget about this.
Francesco
next prev parent reply other threads:[~2025-06-26 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 8:29 [PATCH v4 0/2] i2c: lpi2c: implement master_xfer_atomic callback Francesco Dolcini
2025-05-23 8:29 ` [PATCH v4 1/2] i2c: lpi2c: use readl_poll_timeout() for register polling Francesco Dolcini
2025-05-23 8:29 ` [PATCH v4 2/2] i2c: lpi2c: implement master_xfer_atomic callback Francesco Dolcini
2025-06-26 7:58 ` Francesco Dolcini [this message]
2025-07-14 11:55 ` [PATCH v4 0/2] " Primoz Fiser
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=20250626075837.GA9216@francesco-nb \
--to=francesco@dolcini.it \
--cc=aisheng.dong@nxp.com \
--cc=andi.shyti@kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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