From: Frank Li <Frank.li@nxp.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: linux-i3c@lists.infradead.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH v4 2/4] i3c: mipi-i3c-hci: Use core helpers for DMA mapping and bounce buffering
Date: Mon, 25 Aug 2025 12:23:41 -0400 [thread overview]
Message-ID: <aKyODemS7jryOn8E@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250822105630.2820009-3-jarkko.nikula@linux.intel.com>
On Fri, Aug 22, 2025 at 01:56:28PM +0300, Jarkko Nikula wrote:
> So far only I3C private and I2C transfers have required a bounce buffer
> for DMA transfers when buffer is not DMA'able.
>
> It was observed that when the device DMA is IOMMU mapped and the receive
> length is not a multiple of DWORDs (32-bit), the last DWORD is padded
> with stale data from the RX FIFO, corrupting 1-3 bytes beyond the
> expected data.
>
> A similar issue, though less severe, occurs when an I3C target returns
> less data than requested. In this case, the padding does not exceed the
> requested number of bytes, assuming the device DMA is not IOMMU mapped.
>
> Therefore, all I3C private transfer, CCC command payload and I2C
> transfer receive buffers must be properly sized for the DMA being IOMMU
> mapped. Even if those buffers are already DMA safe, their size may not
> be DWORD aligned.
>
> To prepare for the device DMA being IOMMU mapped and to address the
> above issue, use helpers from I3C core for DMA mapping and bounce
> buffering for all DMA transfers.
>
> For now, require bounce buffer only when the buffer is in the
> vmalloc() area to avoid unnecessary copying with CCC commands and
> DMA-safe I2C transfers.
>
> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> drivers/i3c/master/mipi-i3c-hci/core.c | 34 --------------------------
> drivers/i3c/master/mipi-i3c-hci/dma.c | 27 +++++++++-----------
> drivers/i3c/master/mipi-i3c-hci/hci.h | 3 +--
> 3 files changed, 12 insertions(+), 52 deletions(-)
>
> diff --git a/drivers/i3c/master/mipi-i3c-hci/core.c b/drivers/i3c/master/mipi-i3c-hci/core.c
> index 60f1175f1f37..b2977b6ac9f7 100644
> --- a/drivers/i3c/master/mipi-i3c-hci/core.c
> +++ b/drivers/i3c/master/mipi-i3c-hci/core.c
> @@ -272,34 +272,6 @@ static int i3c_hci_daa(struct i3c_master_controller *m)
> return hci->cmd->perform_daa(hci);
> }
>
> -static int i3c_hci_alloc_safe_xfer_buf(struct i3c_hci *hci,
> - struct hci_xfer *xfer)
> -{
> - if (hci->io != &mipi_i3c_hci_dma ||
> - xfer->data == NULL || !is_vmalloc_addr(xfer->data))
> - return 0;
> -
> - if (xfer->rnw)
> - xfer->bounce_buf = kzalloc(xfer->data_len, GFP_KERNEL);
> - else
> - xfer->bounce_buf = kmemdup(xfer->data,
> - xfer->data_len, GFP_KERNEL);
> -
> - return xfer->bounce_buf == NULL ? -ENOMEM : 0;
> -}
> -
> -static void i3c_hci_free_safe_xfer_buf(struct i3c_hci *hci,
> - struct hci_xfer *xfer)
> -{
> - if (hci->io != &mipi_i3c_hci_dma || xfer->bounce_buf == NULL)
> - return;
> -
> - if (xfer->rnw)
> - memcpy(xfer->data, xfer->bounce_buf, xfer->data_len);
> -
> - kfree(xfer->bounce_buf);
> -}
> -
> static int i3c_hci_priv_xfers(struct i3c_dev_desc *dev,
> struct i3c_priv_xfer *i3c_xfers,
> int nxfers)
> @@ -333,9 +305,6 @@ static int i3c_hci_priv_xfers(struct i3c_dev_desc *dev,
> }
> hci->cmd->prep_i3c_xfer(hci, dev, &xfer[i]);
> xfer[i].cmd_desc[0] |= CMD_0_ROC;
> - ret = i3c_hci_alloc_safe_xfer_buf(hci, &xfer[i]);
> - if (ret)
> - goto out;
> }
> last = i - 1;
> xfer[last].cmd_desc[0] |= CMD_0_TOC;
> @@ -359,9 +328,6 @@ static int i3c_hci_priv_xfers(struct i3c_dev_desc *dev,
> }
>
> out:
> - for (i = 0; i < nxfers; i++)
> - i3c_hci_free_safe_xfer_buf(hci, &xfer[i]);
> -
> hci_free_xfer(xfer, nxfers);
> return ret;
> }
> diff --git a/drivers/i3c/master/mipi-i3c-hci/dma.c b/drivers/i3c/master/mipi-i3c-hci/dma.c
> index 491dfe70b660..351851859f02 100644
> --- a/drivers/i3c/master/mipi-i3c-hci/dma.c
> +++ b/drivers/i3c/master/mipi-i3c-hci/dma.c
> @@ -349,9 +349,7 @@ static void hci_dma_unmap_xfer(struct i3c_hci *hci,
> xfer = xfer_list + i;
> if (!xfer->data)
> continue;
> - dma_unmap_single(&hci->master.dev,
> - xfer->data_dma, xfer->data_len,
> - xfer->rnw ? DMA_FROM_DEVICE : DMA_TO_DEVICE);
> + i3c_master_dma_unmap_single(xfer->dma);
> }
> }
>
> @@ -362,7 +360,6 @@ static int hci_dma_queue_xfer(struct i3c_hci *hci,
> struct hci_rh_data *rh;
> unsigned int i, ring, enqueue_ptr;
> u32 op1_val, op2_val;
> - void *buf;
>
> /* For now we only use ring 0 */
> ring = 0;
> @@ -373,6 +370,8 @@ static int hci_dma_queue_xfer(struct i3c_hci *hci,
> for (i = 0; i < n; i++) {
> struct hci_xfer *xfer = xfer_list + i;
> u32 *ring_data = rh->xfer + rh->xfer_struct_sz * enqueue_ptr;
> + enum dma_data_direction dir = xfer->rnw ? DMA_FROM_DEVICE :
> + DMA_TO_DEVICE;
>
> /* store cmd descriptor */
> *ring_data++ = xfer->cmd_desc[0];
> @@ -391,21 +390,17 @@ static int hci_dma_queue_xfer(struct i3c_hci *hci,
>
> /* 2nd and 3rd words of Data Buffer Descriptor Structure */
> if (xfer->data) {
> - buf = xfer->bounce_buf ? xfer->bounce_buf : xfer->data;
> - xfer->data_dma =
> - dma_map_single(&hci->master.dev,
> - buf,
> - xfer->data_len,
> - xfer->rnw ?
> - DMA_FROM_DEVICE :
> - DMA_TO_DEVICE);
> - if (dma_mapping_error(&hci->master.dev,
> - xfer->data_dma)) {
> + xfer->dma = i3c_master_dma_map_single(&hci->master.dev,
> + xfer->data,
> + xfer->data_len,
> + false,
> + dir);
> + if (!xfer->dma) {
> hci_dma_unmap_xfer(hci, xfer_list, i);
> return -ENOMEM;
> }
> - *ring_data++ = lower_32_bits(xfer->data_dma);
> - *ring_data++ = upper_32_bits(xfer->data_dma);
> + *ring_data++ = lower_32_bits(xfer->dma->addr);
> + *ring_data++ = upper_32_bits(xfer->dma->addr);
> } else {
> *ring_data++ = 0;
> *ring_data++ = 0;
> diff --git a/drivers/i3c/master/mipi-i3c-hci/hci.h b/drivers/i3c/master/mipi-i3c-hci/hci.h
> index 69ea1d10414b..33bc4906df1f 100644
> --- a/drivers/i3c/master/mipi-i3c-hci/hci.h
> +++ b/drivers/i3c/master/mipi-i3c-hci/hci.h
> @@ -94,8 +94,7 @@ struct hci_xfer {
> };
> struct {
> /* DMA specific */
> - dma_addr_t data_dma;
> - void *bounce_buf;
> + struct i3c_dma *dma;
> int ring_number;
> int ring_entry;
> };
> --
> 2.47.2
>
>
> --
> linux-i3c mailing list
> linux-i3c@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-i3c
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2025-08-25 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 10:56 [PATCH v4 0/4] mipi-i3c-hci: Make able to work with IOMMU enabled Jarkko Nikula
2025-08-22 10:56 ` [PATCH v4 1/4] i3c: master: Add helpers for DMA mapping and bounce buffer handling Jarkko Nikula
2025-08-25 16:21 ` Frank Li
2025-08-22 10:56 ` [PATCH v4 2/4] i3c: mipi-i3c-hci: Use core helpers for DMA mapping and bounce buffering Jarkko Nikula
2025-08-25 16:23 ` Frank Li [this message]
2025-08-22 10:56 ` [PATCH v4 3/4] i3c: mipi-i3c-hci: Use physical device pointer with DMA API Jarkko Nikula
2025-08-22 10:56 ` [PATCH v4 4/4] i3c: mipi-i3c-hci: Use own DMA bounce buffer management for I2C transfers Jarkko Nikula
2025-09-14 20:31 ` [PATCH v4 0/4] mipi-i3c-hci: Make able to work with IOMMU enabled Alexandre Belloni
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=aKyODemS7jryOn8E@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i3c@lists.infradead.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