From: Aniket RANDIVE <aniket.randive@oss.qualcomm.com>
To: Mukesh Savaliya <mukesh.savaliya@oss.qualcomm.com>,
Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>,
Andi Shyti <andi.shyti@kernel.org>
Cc: naresh.maramaina@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dmaengine: qcom: gpi: Add I2C bus recovery opcode support
Date: Tue, 3 Nov 2026 12:51:52 +0530 [thread overview]
Message-ID: <cb63c8ad-abf2-41f3-a2c2-0b21196fe46e@oss.qualcomm.com> (raw)
In-Reply-To: <197ed473-d259-4f1f-ace0-ce98ac0fd127@oss.qualcomm.com>
On 10/27/2026 7:04 PM, Mukesh Savaliya wrote:
>
>
> On 10/27/2026 10:43 AM, Aniket Randive wrote:
> [...]
>> diff --git a/drivers/dma/qcom/gpi.c b/drivers/dma/qcom/gpi.c
>> index c41bfac65ddf..394e7287f6e9 100644
>> --- a/drivers/dma/qcom/gpi.c
>> +++ b/drivers/dma/qcom/gpi.c
>
> [...]
>
>> @@ -1692,6 +1709,7 @@ static int gpi_create_i2c_tre(struct gchan
>> *chan, struct gpi_desc *desc,
>> tre->dword[3] |= u32_encode_bits(1, TRE_FLAGS_BEI);
>> }
>> +log_tre:
>> for (i = 0; i < tre_idx; i++)
>> dev_dbg(dev, "TRE:%d %x:%x:%x:%x\n", i, desc->tre[i].dword[0],
>> desc->tre[i].dword[1], desc->tre[i].dword[2], desc-
>> >tre[i].dword[3]);
>> @@ -1825,6 +1843,18 @@ gpi_prep_slave_sg(struct dma_chan *chan, struct
>> scatterlist *sgl,
>> nr_tre = 2;
>> if (direction == DMA_DEV_TO_MEM) /* rx */
>> nr_tre = 1;
>> + /*
>> + * Recovery opcodes do not require DMA data TREs, only CONFIG
>> + * (for set_config) and GO TREs. Since gpi_prep_slave_sg() is
>> + * shared with SPI, verify the channel is I2C before accessing
>> + * the configuration data.
> I think i have mentioned earlier also. gpi_prep_slave_sg() Not only
> shared with spi but rather say, is a common function for all protocols.>
> + */
Currently, the GPI driver has only I2C and SPI clients, so I mentioned
SPI specifically. However, UART may also use GSI mode in the future.
I’ll update the comment to state that gpi_prep_slave_sg() is common to
all protocols.
>> + if (gchan->protocol == QCOM_GPI_I2C) {
>> + struct gpi_i2c_config *i2c = gchan->config;
>> +
>> + if (i2c->op == I2C_BUS_CLEAR || i2c->op == I2C_STOP_ON_BUS)
>> + nr_tre = set_config ? 2 : 1;
>> + }
>> /* calculate # of elements required & available */
>> nr = gpi_ring_num_elements_avail(ch_ring);
>> diff --git a/drivers/i2c/busses/i2c-qcom-geni.c b/drivers/i2c/busses/
>> i2c-qcom-geni.c
> [...]
next prev parent reply other threads:[~2026-11-03 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 5:13 [PATCH v3 0/3] i2c: qcom-geni: Add I2C bus recovery support Aniket Randive
2026-10-27 5:13 ` [PATCH v3 1/3] dmaengine: qcom: gpi: Add I2C bus recovery opcode support Aniket Randive
2026-10-27 13:34 ` Mukesh Savaliya
2026-11-03 7:21 ` Aniket RANDIVE [this message]
2026-10-27 5:13 ` [PATCH v3 2/3] i2c: qcom-geni: Add bus recovery support for FIFO mode Aniket Randive
2026-10-27 14:07 ` Mukesh Savaliya
2026-11-03 7:19 ` Aniket RANDIVE
2026-10-27 5:13 ` [PATCH v3 3/3] i2c: qcom-geni: Add bus recovery support for GPI DMA mode Aniket Randive
2026-10-27 14:31 ` Mukesh Savaliya
2026-11-03 7:18 ` Aniket RANDIVE
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=cb63c8ad-abf2-41f3-a2c2-0b21196fe46e@oss.qualcomm.com \
--to=aniket.randive@oss.qualcomm.com \
--cc=Frank.Li@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=naresh.maramaina@oss.qualcomm.com \
--cc=viken.dadhaniya@oss.qualcomm.com \
--cc=vkoul@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
all inboxes | Powered by JetHome®