From: dirac3000@gmail.com (dirac3000)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] DMA: PL330: allow submitting 2 requests at a time
Date: Thu, 07 Feb 2013 14:46:37 +0100 [thread overview]
Message-ID: <5113B03D.5010206@gmail.com> (raw)
In-Reply-To: <CABb+yY3iPoXBFpKgmdTijeee71Xz9dkwjcay8keu+vsdWtDfXw@mail.gmail.com>
On 02/07/2013 12:31 PM, Jassi Brar wrote:
> On Thu, Feb 7, 2013 at 4:08 PM, Alvaro Moran<dirac3000@gmail.com> wrote:
>> Due to the original driver design, only one request was processed at a
>> time by the driver, even if the low-level part of the driver was able to
>> handle 2 requests.
>> With this patch we are able to create 2 microcodes per thread and to
>> launch the second transfer on the interrupt handler of the first one,
>> instead of having to wait for the tasklet to generate the microcode.
>>
> The following seems more appropriate and complete. Does it fix your problem?
>
> diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
> index 758122f..a821d71 100644
> --- a/drivers/dma/pl330.c
> +++ b/drivers/dma/pl330.c
> @@ -2292,13 +2292,12 @@ static inline void fill_queue(struct
> dma_pl330_chan *pch)
>
> /* If already submitted */
> if (desc->status == BUSY)
> - break;
> + continue;
>
> ret = pl330_submit_req(pch->pl330_chid,
> &desc->req);
> if (!ret) {
> desc->status = BUSY;
> - break;
> } else if (ret == -EAGAIN) {
> /* QFull or DMAC Dying */
> break;
Actually that isn't good enough. With your patch it will keep on looping
on the pch->work_list entries, but it will call pl330_submit_req the
first time only. I want it to call the function twice, so it will
generate 2 microcodes (one per available request) and it will be ready
the moment we get into the interrupt handler.
next prev parent reply other threads:[~2013-02-07 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 10:38 [PATCH 1/1] DMA: PL330: allow submitting 2 requests at a time Alvaro Moran
2013-02-07 11:31 ` Jassi Brar
2013-02-07 13:46 ` dirac3000 [this message]
2013-02-07 14:12 ` Jassi Brar
2013-02-07 17:08 ` dirac3000
2013-02-13 10:12 ` dirac3000
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=5113B03D.5010206@gmail.com \
--to=dirac3000@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).