From: Vinod Koul <vkoul@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: "Jyothi Kumar Seerapu" <quic_jseerapu@quicinc.com>,
"Mukesh Kumar Savaliya" <quic_msavaliy@quicinc.com>,
"Viken Dadhaniya" <quic_vdadhani@quicinc.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, quic_vtanuku@quicinc.com
Subject: Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support
Date: Wed, 23 Jul 2025 12:45:25 +0530 [thread overview]
Message-ID: <aICMDROkyjzBZFHo@vaman> (raw)
In-Reply-To: <iang2jpe4s6wmbypmtq5uswcm6n6xntqdulyhekcz5k6zxddu3@re3rrr4dso5p>
On 22-07-25, 15:46, Dmitry Baryshkov wrote:
> On Tue, Jul 22, 2025 at 05:50:08PM +0530, Jyothi Kumar Seerapu wrote:
> > On 7/19/2025 3:27 PM, Dmitry Baryshkov wrote:
> > > On Mon, Jul 07, 2025 at 09:58:30PM +0530, Jyothi Kumar Seerapu wrote:
> > > > On 7/4/2025 1:11 AM, Dmitry Baryshkov wrote:
> > > > > On Thu, 3 Jul 2025 at 15:51, Jyothi Kumar Seerapu
[Folks, would be nice to trim replies]
> > > > Could you please confirm if can go with the similar approach of unmap the
> > > > processed TREs based on a fixed threshold or constant value, instead of
> > > > unmapping them all at once?
> > >
> > > I'd still say, that's a bad idea. Please stay within the boundaries of
> > > the DMA API.
> > >
> > I agree with the approach you suggested—it's the GPI's responsibility to
> > manage the available TREs.
> >
> > However, I'm curious whether can we set a dynamic watermark value perhaps
> > half the available TREs) to trigger unmapping of processed TREs ? This would
> > allow the software to prepare the next set of TREs while the hardware
> > continues processing the remaining ones, enabling better parallelism and
> > throughput.
>
> Let's land the simple implementation first, which can then be improved.
> However I don't see any way to return 'above the watermark' from the DMA
> controller. You might need to enhance the API.
Traditionally, we set the dma transfers for watermark level and we get a
interrupt. So you might want to set the callback for watermark level
and then do mapping/unmapping etc in the callback. This is typical model
for dmaengines, we should follow that well
BR
--
~Vinod
next prev parent reply other threads:[~2025-07-23 7:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 11:18 [PATCH v6 0/2] Add Block event interrupt support for I2C protocol Jyothi Kumar Seerapu
2025-05-06 11:18 ` [PATCH v6 1/2] dmaengine: qcom: gpi: Add GPI Block event interrupt support Jyothi Kumar Seerapu
2025-05-06 11:32 ` Dmitry Baryshkov
2025-05-09 6:18 ` Jyothi Kumar Seerapu
2025-05-30 14:05 ` Jyothi Kumar Seerapu
2025-05-30 15:53 ` Dmitry Baryshkov
2025-06-17 14:16 ` Jyothi Kumar Seerapu
2025-05-06 11:18 ` [PATCH v6 2/2] i2c: i2c-qcom-geni: Add " Jyothi Kumar Seerapu
2025-05-06 11:46 ` Dmitry Baryshkov
2025-05-09 6:18 ` Jyothi Kumar Seerapu
2025-05-09 16:01 ` Dmitry Baryshkov
2025-05-21 10:28 ` Jyothi Kumar Seerapu
2025-05-21 12:45 ` Dmitry Baryshkov
2025-05-30 14:06 ` Jyothi Kumar Seerapu
2025-05-30 16:42 ` Dmitry Baryshkov
2025-06-17 14:11 ` Jyothi Kumar Seerapu
2025-06-17 19:32 ` Dmitry Baryshkov
2025-06-19 16:16 ` Jyothi Kumar Seerapu
2025-07-03 12:50 ` Jyothi Kumar Seerapu
2025-07-03 19:41 ` Dmitry Baryshkov
2025-07-07 16:28 ` Jyothi Kumar Seerapu
2025-07-19 9:57 ` Dmitry Baryshkov
2025-07-22 12:20 ` Jyothi Kumar Seerapu
2025-07-22 12:46 ` Dmitry Baryshkov
2025-07-23 7:15 ` Vinod Koul [this message]
2025-07-25 10:50 ` Jyothi Kumar Seerapu
2025-08-11 17:40 ` Vinod Koul
2025-08-14 12:44 ` Jyothi Kumar Seerapu
2025-05-07 2:21 ` ALOK TIWARI
2025-05-09 6:16 ` Jyothi Kumar Seerapu
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=aICMDROkyjzBZFHo@vaman \
--to=vkoul@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.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=quic_jseerapu@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_vdadhani@quicinc.com \
--cc=quic_vtanuku@quicinc.com \
--cc=sumit.semwal@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.