From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Cixi Geng <gengcixi@gmail.com>,
orsonzhai@gmail.com, zhang.lyra@gmail.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Cixi Geng <cixi.geng1@unisoc.com>
Subject: Re: [PATCH V2] dmaengine: sprd: Support two-stage dma interrupt
Date: Fri, 21 Oct 2022 09:35:17 +0800 [thread overview]
Message-ID: <18c6c091-6eb6-cc56-68d6-2b9811da9618@linux.alibaba.com> (raw)
In-Reply-To: <Y1EvX+hL/LWBnuvX@matsya>
On 10/20/2022 7:22 PM, Vinod Koul wrote:
> On 20-10-22, 16:15, Baolin Wang wrote:
>
>>>> why is sprd_dma_int_type part of driver interface. sprd_dma_int_type is
>>>> used only by this driver and should be moved into the driver..
>>
>> Now we can not move this into dma driver, since we have some drivers in the
>> mainline will set the DMA interrupt type, such as spi-sprd.c, sprd_serial.c
>> and sprd-pcm-compress.c.
>
> That may not sound right.. Why should peripheral set the DMA
> interrupt..?
That's because SPRD DMA controller supplies several different interrupt
types for different scenarios of users, for example:
@SPRD_DMA_FRAG_INT: fragment done interrupt when one fragment request is
done.
@SPRD_DMA_BLK_INT: block done interrupt when one block request is done.
@SPRD_DMA_BLK_FRAG_INT: block and fragment interrupt when one fragment
or one block request is done.
@SPRD_DMA_TRANS_INT: tansaction done interrupt when one transaction
request is done.
......
Some users may want use Linklist interrupt, and others may just want
tansaction interrupt. So exposing these interrupt types for users to
decide seems more suitable.
prev parent reply other threads:[~2022-10-21 1:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 23:49 Cixi Geng
2022-10-10 6:30 ` Baolin Wang
2022-10-19 14:07 ` Vinod Koul
2022-10-20 7:33 ` Cixi Geng
2022-10-20 8:15 ` Baolin Wang
2022-10-20 11:22 ` Vinod Koul
2022-10-21 1:35 ` Baolin Wang [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=18c6c091-6eb6-cc56-68d6-2b9811da9618@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=cixi.geng1@unisoc.com \
--cc=dmaengine@vger.kernel.org \
--cc=gengcixi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=vkoul@kernel.org \
--cc=zhang.lyra@gmail.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®