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 3/3] i2c: qcom-geni: Add bus recovery support for GPI DMA mode
Date: Tue, 3 Nov 2026 12:48:46 +0530 [thread overview]
Message-ID: <fc929696-92ad-460a-b097-40e66a264252@oss.qualcomm.com> (raw)
In-Reply-To: <b88efeae-6041-4189-a559-a16be07450bc@oss.qualcomm.com>
On 10/27/2026 8:01 PM, Mukesh Savaliya wrote:
>
>
> On 10/27/2026 10:43 AM, Aniket Randive wrote:
> [...]
>
>> +static int geni_i2c_gpi_bus_cmd(struct geni_i2c_dev *gi2c, enum
>> i2c_op cmd)
>> +{
>> + const struct geni_i2c_clk_fld *itr = gi2c->clk_fld;
>> + struct dma_async_tx_descriptor *desc;
>> + struct gpi_i2c_config peripheral = {};
>> + struct dma_slave_config config = {};
>> + unsigned long time_left;
>> + unsigned long flags;
>> + dma_cookie_t cookie;
>> + int ret;
>> +
>> + config.peripheral_config = &peripheral;
>> + config.peripheral_size = sizeof(peripheral);
>> +
>> + peripheral.set_config = 1;
>> + peripheral.pack_enable = I2C_PACK_TX | I2C_PACK_RX;
>> + peripheral.cycle_count = itr->t_cycle_cnt;
>> + peripheral.high_count = itr->t_high_cnt;
>> + peripheral.low_count = itr->t_low_cnt;
>> + peripheral.clk_div = itr->clk_div;
>> + peripheral.op = cmd;
>> +
>> + ret = dmaengine_slave_config(gi2c->tx_c, &config);
>> + if (ret) {
>> + dev_err(gi2c->se.dev, "dma config error %d for bus cmd %u\n",
>> ret, cmd);
>> + return ret;
>> + }
>> +
>> + desc = dmaengine_prep_slave_single(gi2c->tx_c, 0, 0, DMA_MEM_TO_DEV,
>> + DMA_PREP_INTERRUPT | DMA_CTRL_ACK);
>> + if (!desc)
>> + return -EIO;
>> +
>> + desc->callback_result = i2c_gpi_cb_result;
>> + desc->callback_param = gi2c;
>> +
>> + cookie = dmaengine_submit(desc);
>> + if (dma_submit_error(cookie))
>> + return -EIO;
>
> Rather capture ret and return it if it's an error ?
sure. I will make the change in next patch.
>
>> +
>> + /*
>> + * cur and err are shared with geni_i2c_irq() and the GPI callback
>> + * i2c_gpi_cb_result(); both write err (the IRQ handler under
>> + * gi2c->lock). Reset them under the lock before issuing the
>> transfer.
>> + */
>> + spin_lock_irqsave(&gi2c->lock, flags);
>> + gi2c->cur = NULL;
>> + gi2c->err = 0;
>> + spin_unlock_irqrestore(&gi2c->lock, flags);
>> + reinit_completion(&gi2c->done);
> Safe to init before dmaengine_submit().> + dma_async_issue_pending(gi2c-
> >tx_c);
Agree. I will make the change in next patch.
>> +
>> + time_left = wait_for_completion_timeout(&gi2c->done, gi2c-
>> >adap.timeout);
>> + if (!time_left) {
>> + dev_err(gi2c->se.dev, "timeout waiting for GPI bus cmd %u\n",
>> cmd);
>> + ret = dmaengine_terminate_sync(gi2c->tx_c);
>> + if (ret)
>> + dev_err(gi2c->se.dev, "DMA termination failed for bus cmd
>> %u: %d\n",
>> + cmd, ret);
>> + return -ETIMEDOUT;
>> + }
>> +
>> + return gi2c->err;
>> +}
>> +[...]
prev parent reply other threads:[~2026-11-03 7:18 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
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 [this message]
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=fc929696-92ad-460a-b097-40e66a264252@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®