From: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>
To: Vaishnav Achath <vaishnav.a@ti.com>,
vkoul@kernel.org, broonie@kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Cc: vigneshr@ti.com, kishon@ti.com
Subject: Re: [PATCH 1/2] dmaengine: ti: k3-udma: Respond TX done if DMA_PREP_INTERRUPT is not requested
Date: Sat, 10 Sep 2022 21:57:20 +0300 [thread overview]
Message-ID: <607af3f8-9fb2-da00-1867-5ab59ce9d3e8@gmail.com> (raw)
In-Reply-To: <a30e917d-e031-3829-36fb-b897e971825f@ti.com>
On 05/09/2022 06:02, Vaishnav Achath wrote:
>> Let me think about over the weekend... Do you have performance numbers for this
>> change?
>>
> Thank you, yes we tested mainly for the SPI cases(Master and Slave mode), there
> we saw a peak delay of 400ms for transaction completion and this varied with CPU
> load, after adding the patch to not wait for DMA TX completion and use EOW
> interrupt the peak latency reduced to 2ms.
Thank you for the details.
>> If we make sure that this is only affecting non cyclic transfers with a in code
>> comment to explain the expectations from the user I think this can be safe.
>> \
> Sure I will add this in the next revision.
You can add my Acked-by when you send the next version:
Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>
>>>
>>>>>
>>>>> Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
>>>>> ---
>>>>> drivers/dma/ti/k3-udma.c | 5 ++++-
>>>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/drivers/dma/ti/k3-udma.c b/drivers/dma/ti/k3-udma.c
>>>>> index 39b330ada200..03d579068453 100644
>>>>> --- a/drivers/dma/ti/k3-udma.c
>>>>> +++ b/drivers/dma/ti/k3-udma.c
>>>>> @@ -263,6 +263,7 @@ struct udma_chan_config {
>>>>> enum udma_tp_level channel_tpl; /* Channel Throughput Level */
>>>>> u32 tr_trigger_type;
>>>>> + unsigned long tx_flags;
>>>>> /* PKDMA mapped channel */
>>>>> int mapped_channel_id;
>>>>> @@ -1057,7 +1058,7 @@ static bool udma_is_desc_really_done(struct udma_chan
>>>>> *uc, struct udma_desc *d)
>>>>> /* Only TX towards PDMA is affected */
>>>>> if (uc->config.ep_type == PSIL_EP_NATIVE ||
>>>>> - uc->config.dir != DMA_MEM_TO_DEV)
>>>>> + uc->config.dir != DMA_MEM_TO_DEV || !(uc->config.tx_flags &
>>>>> DMA_PREP_INTERRUPT))
>>>>> return true;
>>>>> peer_bcnt = udma_tchanrt_read(uc, UDMA_CHAN_RT_PEER_BCNT_REG);
>>>>> @@ -3418,6 +3419,8 @@ udma_prep_slave_sg(struct dma_chan *chan, struct
>>>>> scatterlist *sgl,
>>>>> if (!burst)
>>>>> burst = 1;
>>>>> + uc->config.tx_flags = tx_flags;
>>>>> +
>>>>> if (uc->config.pkt_mode)
>>>>> d = udma_prep_slave_sg_pkt(uc, sgl, sglen, dir, tx_flags,
>>>>> context);
>>>>
>>>
>>
>
--
Péter
next prev parent reply other threads:[~2022-09-10 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:15 [PATCH 0/2] spi: spi-omap2-mcspi: Use EOW interrupt for transfer completion Vaishnav Achath
2022-08-22 9:15 ` [PATCH 1/2] dmaengine: ti: k3-udma: Respond TX done if DMA_PREP_INTERRUPT is not requested Vaishnav Achath
2022-08-22 13:12 ` Péter Ujfalusi
2022-08-23 6:57 ` Vaishnav Achath
2022-09-02 14:20 ` Péter Ujfalusi
2022-09-05 3:02 ` Vaishnav Achath
2022-09-10 18:57 ` Péter Ujfalusi [this message]
2022-08-22 9:15 ` [PATCH 2/2] spi: spi-omap2-mcspi: Use EOW interrupt for completion when DMA enabled Vaishnav Achath
2022-08-22 13:14 ` kernel test robot
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=607af3f8-9fb2-da00-1867-5ab59ce9d3e8@gmail.com \
--to=peter.ujfalusi@gmail.com \
--cc=broonie@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=vaishnav.a@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).