From: Alain Volmat <alain.volmat@foss.st.com>
To: "Clément Le Goffic" <clement.legoffic@foss.st.com>
Cc: "Pierre-Yves MORDRET" <pierre-yves.mordret@foss.st.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"M'boumba Cedric Madianga" <cedric.madianga@gmail.com>,
"Wolfram Sang" <wsa@kernel.org>,
"Pierre-Yves MORDRET" <pierre-yves.mordret@st.com>,
linux-i2c@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH 3/3] i2c: stm32f7: support i2c_*_dma_safe_msg_buf APIs
Date: Thu, 26 Jun 2025 12:32:57 +0200 [thread overview]
Message-ID: <20250626103257.GA349896@gnbcxd0016.gnb.st.com> (raw)
In-Reply-To: <20250616-i2c-upstream-v1-3-42d3d5374e65@foss.st.com>
Hi Clément,
thanks for the patch.
On Mon, Jun 16, 2025 at 10:53:56AM +0200, Clément Le Goffic wrote:
> Use the i2c-core-base APIs to allocate a DMA safe buffer when needed.
>
> Signed-off-by: Clément Le Goffic <clement.legoffic@foss.st.com>
> ---
> drivers/i2c/busses/i2c-stm32f7.c | 36 +++++++++++++++++++++++++-----------
> 1 file changed, 25 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-stm32f7.c b/drivers/i2c/busses/i2c-stm32f7.c
> index a05cac5ee9db..5be14c8a2af4 100644
> --- a/drivers/i2c/busses/i2c-stm32f7.c
> +++ b/drivers/i2c/busses/i2c-stm32f7.c
> @@ -742,9 +742,12 @@ static void stm32f7_i2c_dma_callback(void *arg)
> struct stm32f7_i2c_dev *i2c_dev = (struct stm32f7_i2c_dev *)arg;
> struct stm32_i2c_dma *dma = i2c_dev->dma;
> struct device *dev = dma->chan_using->device->dev;
> + struct stm32f7_i2c_msg *f7_msg = &i2c_dev->f7_msg;
>
> stm32f7_i2c_disable_dma_req(i2c_dev);
> dma_unmap_single(dev, dma->dma_buf, dma->dma_len, dma->dma_data_dir);
> + if (!f7_msg->smbus)
> + i2c_put_dma_safe_msg_buf(f7_msg->buf, i2c_dev->msg, true);
> complete(&dma->dma_complete);
> }
>
> @@ -880,6 +883,7 @@ static void stm32f7_i2c_xfer_msg(struct stm32f7_i2c_dev *i2c_dev,
> {
> struct stm32f7_i2c_msg *f7_msg = &i2c_dev->f7_msg;
> void __iomem *base = i2c_dev->base;
> + u8 *dma_buf;
> u32 cr1, cr2;
> int ret;
>
> @@ -929,17 +933,23 @@ static void stm32f7_i2c_xfer_msg(struct stm32f7_i2c_dev *i2c_dev,
>
> /* Configure DMA or enable RX/TX interrupt */
> i2c_dev->use_dma = false;
> - if (i2c_dev->dma && f7_msg->count >= STM32F7_I2C_DMA_LEN_MIN
> - && !i2c_dev->atomic) {
> - ret = stm32_i2c_prep_dma_xfer(i2c_dev->dev, i2c_dev->dma,
> - msg->flags & I2C_M_RD,
> - f7_msg->count, f7_msg->buf,
> - stm32f7_i2c_dma_callback,
> - i2c_dev);
> - if (!ret)
> - i2c_dev->use_dma = true;
> - else
> - dev_warn(i2c_dev->dev, "can't use DMA\n");
> + if (i2c_dev->dma && !i2c_dev->atomic) {
> + dma_buf = i2c_get_dma_safe_msg_buf(msg, STM32F7_I2C_DMA_LEN_MIN);
> + if (dma_buf) {
> + f7_msg->buf = dma_buf;
> + ret = stm32_i2c_prep_dma_xfer(i2c_dev->dev, i2c_dev->dma,
> + msg->flags & I2C_M_RD,
> + f7_msg->count, f7_msg->buf,
> + stm32f7_i2c_dma_callback,
> + i2c_dev);
> + if (ret) {
> + dev_warn(i2c_dev->dev, "can't use DMA\n");
> + i2c_put_dma_safe_msg_buf(f7_msg->buf, msg, false);
> + f7_msg->buf = msg->buf;
> + } else {
> + i2c_dev->use_dma = true;
> + }
> + }
> }
>
> if (!i2c_dev->use_dma) {
> @@ -1624,6 +1634,8 @@ static irqreturn_t stm32f7_i2c_isr_event_thread(int irq, void *data)
> dmaengine_terminate_async(dma->chan_using);
> dma_unmap_single(i2c_dev->dev, dma->dma_buf, dma->dma_len,
> dma->dma_data_dir);
> + if (!f7_msg->smbus)
> + i2c_put_dma_safe_msg_buf(f7_msg->buf, i2c_dev->msg, false);
> }
> f7_msg->result = -ENXIO;
> }
> @@ -1646,6 +1658,8 @@ static irqreturn_t stm32f7_i2c_isr_event_thread(int irq, void *data)
> dmaengine_terminate_async(dma->chan_using);
> dma_unmap_single(i2c_dev->dev, dma->dma_buf, dma->dma_len,
> dma->dma_data_dir);
> + if (!f7_msg->smbus)
> + i2c_put_dma_safe_msg_buf(f7_msg->buf, i2c_dev->msg, false);
> f7_msg->result = -ETIMEDOUT;
> }
> }
>
Looks good to me.
Acked-by: Alain Volmat <alain.volmat@foss.st.com>
Regards,
Alain
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-06-26 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 8:53 [PATCH 0/3] Fix STM32 I2C dma operations Clément Le Goffic
2025-06-16 8:53 ` [PATCH 1/3] i2c: stm32: fix the device used for the DMA map Clément Le Goffic
2025-06-26 8:37 ` Alain Volmat
2025-06-26 8:43 ` Alain Volmat
2025-06-27 7:30 ` Clement LE GOFFIC
2025-06-16 8:53 ` [PATCH 2/3] i2c: stm32f7: unmap DMA mapped buffer Clément Le Goffic
2025-06-26 9:03 ` Alain Volmat
2025-06-27 10:16 ` Clement LE GOFFIC
2025-06-16 8:53 ` [PATCH 3/3] i2c: stm32f7: support i2c_*_dma_safe_msg_buf APIs Clément Le Goffic
2025-06-26 10:32 ` Alain Volmat [this message]
2025-06-25 22:17 ` [PATCH 0/3] Fix STM32 I2C dma operations Andi Shyti
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=20250626103257.GA349896@gnbcxd0016.gnb.st.com \
--to=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andi.shyti@kernel.org \
--cc=cedric.madianga@gmail.com \
--cc=christian.koenig@amd.com \
--cc=clement.legoffic@foss.st.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pierre-yves.mordret@foss.st.com \
--cc=pierre-yves.mordret@st.com \
--cc=sumit.semwal@linaro.org \
--cc=wsa@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