From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: "Aniket Randive" <aniket.randive@oss.qualcomm.com>,
"Mukesh Kumar Savaliya" <mukesh.savaliya@oss.qualcomm.com>,
"Viken Dadhaniya" <viken.dadhaniya@oss.qualcomm.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>
Cc: <linux-i2c@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<linaro-mm-sig@lists.linaro.org>,
Maramaina Naresh <naresh.maramaina@oss.qualcomm.com>
Subject: Re: [PATCH v1] i2c: qcom-geni: Skip extra TX DMA TRE for single read message in GPI mode
Date: Fri, 27 Mar 2026 11:51:31 +0530 [thread overview]
Message-ID: <341f2f06-eae0-44b1-b513-61a4a129bae2@quicinc.com> (raw)
In-Reply-To: <20260326-skip_extra_dma_tre-v1-1-deef018895dc@oss.qualcomm.com>
On 3/26/2026 10:01 AM, Aniket Randive wrote:
> In GPI mode, the I2C GENI driver incorrectly generates an extra TX DMA
> TRE on the TX channel during single read message transfer. This results
What's the impact of this extra DMA TRE ? do you see failure/timeout,
anything ?
> in an unnecessary write operation on the I2C bus, which is not required.
>
> Update the logic to avoid generating the extra TX DMA TRE for single
> read message, ensuring correct behavior and preventing redundant
> transfers.
>
So for read, we do unwanted write too ? if so, please write it
accordingly. Correct behavior needs to be justified against wrong.
> Co-developed-by: Maramaina Naresh <naresh.maramaina@oss.qualcomm.com>
> Signed-off-by: Maramaina Naresh <naresh.maramaina@oss.qualcomm.com>
> Signed-off-by: Aniket Randive <aniket.randive@oss.qualcomm.com>
> ---
> drivers/i2c/busses/i2c-qcom-geni.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-qcom-geni.c b/drivers/i2c/busses/i2c-qcom-geni.c
> index a4acb78fafb6..2706309bbebb 100644
> --- a/drivers/i2c/busses/i2c-qcom-geni.c
> +++ b/drivers/i2c/busses/i2c-qcom-geni.c
> @@ -625,8 +625,8 @@ static int geni_i2c_gpi(struct geni_i2c_dev *gi2c, struct i2c_msg msgs[],
> {
> struct gpi_i2c_config *peripheral;
> unsigned int flags;
> - void *dma_buf;
> - dma_addr_t addr;
> + void *dma_buf = NULL;
> + dma_addr_t addr = 0;
> enum dma_data_direction map_dirn;
> enum dma_transfer_direction dma_dirn;
> struct dma_async_tx_descriptor *desc;
> @@ -639,6 +639,11 @@ static int geni_i2c_gpi(struct geni_i2c_dev *gi2c, struct i2c_msg msgs[],
> gi2c_gpi_xfer = &gi2c->i2c_multi_desc_config;
> msg_idx = gi2c_gpi_xfer->msg_idx_cnt;
>
> + if (op == I2C_WRITE && msgs[msg_idx].flags & I2C_M_RD) {
> + peripheral->multi_msg = true;
what's the actual meaning of multi_msg here ? IIUC, this multi_msg is
set to true for single transfer ? any better name if so ? Yes, need to
change it out of this patch.
> + goto skip_dma;
> + }
> +
> dma_buf = i2c_get_dma_safe_msg_buf(&msgs[msg_idx], 1);
> if (!dma_buf) {
> ret = -ENOMEM;
> @@ -668,6 +673,7 @@ static int geni_i2c_gpi(struct geni_i2c_dev *gi2c, struct i2c_msg msgs[],
> flags = DMA_PREP_INTERRUPT | DMA_CTRL_ACK;
> }
>
> +skip_dma:
> /* set the length as message for rx txn */
> peripheral->rx_len = msgs[msg_idx].len;
> peripheral->op = op;
> @@ -740,9 +746,11 @@ static int geni_i2c_gpi(struct geni_i2c_dev *gi2c, struct i2c_msg msgs[],
> return 0;
>
> err_config:
> - dma_unmap_single(gi2c->se.dev->parent, addr,
> - msgs[msg_idx].len, map_dirn);
> - i2c_put_dma_safe_msg_buf(dma_buf, &msgs[msg_idx], false);
> + if (op == I2C_WRITE && (msgs[msg_idx].flags & I2C_M_RD)) {
> + dma_unmap_single(gi2c->se.dev->parent, addr,
> + msgs[msg_idx].len, map_dirn);
> + i2c_put_dma_safe_msg_buf(dma_buf, &msgs[msg_idx], false);
> + }
>
> out:
> gi2c->err = ret;
>
> ---
> base-commit: 785f0eb2f85decbe7c1ef9ae922931f0194ffc2e
> change-id: 20260325-skip_extra_dma_tre-a3cf22f81d9b
>
> Best regards,
> --
> Aniket Randive <aniket.randive@oss.qualcomm.com>
>
>
next prev parent reply other threads:[~2026-03-27 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 4:31 Aniket Randive
2026-03-27 6:21 ` Mukesh Kumar Savaliya [this message]
2026-03-27 10:07 ` Aniket RANDIVE
2026-03-31 9:30 ` Mukesh Kumar Savaliya
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=341f2f06-eae0-44b1-b513-61a4a129bae2@quicinc.com \
--to=quic_msavaliy@quicinc.com \
--cc=andi.shyti@kernel.org \
--cc=aniket.randive@oss.qualcomm.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=naresh.maramaina@oss.qualcomm.com \
--cc=sumit.semwal@linaro.org \
--cc=viken.dadhaniya@oss.qualcomm.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®