From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: add dma_ctrl_cmd to pass buffer stride configuration
Date: Tue, 12 Jul 2011 12:03:22 +0200 [thread overview]
Message-ID: <CACRpkdbLg0+_2kpi4NizFj0fDWb6QPtkcKirKgoH+83vGD0O0A@mail.gmail.com> (raw)
In-Reply-To: <CABb+yY1HJOR+QzmM4-ju4cs+8keoyUbMv+SpVoM6BW=DCMzmQQ@mail.gmail.com>
On Tue, Jul 12, 2011 at 6:17 AM, Jassi Brar <jassisinghbrar@gmail.com> wrote:
> 1) Striding, in one form or other, is supported by other DMACs as well.
> ? The number will only increase in future.
> ? Are we to add ?<VENDOR>_DMA_STRIDE_CONFIG for each case ?
If we are sure about this and striding will work in a similar way on all
then let's have the enum named DMA_STRIDE_CONFIG and move the
passed-in struct to <linux/dmaengine.h) then?
Would that be:
struct dma_stride_config {
u32 read_bytes;
u32 skip_bytes;
};
Or something more complex?
> 2) As Dan noted, client drivers are going to have ifdef hackery in
> order to be common
> ?to other SoCs.
Don't think so, why? This is a runtime config entirely, and I just illustrated
in mail to Dan how that can be handled by falling back to a sglist I believe?
We can *maybe* even put the fallback code into dmaengine, so that an
emulated sglist in place for the DMAengine is done automatically of the
DMA controller does not support striding.
> 3) TI may not have just one DMAC IP used in all the SoCs. So if you want
> ?vendor specific defines anyway, please atleast also add DMAC version to it.
> ?Something like
>> ? ? ? ?DMA_SLAVE_CONFIG,
>> ? ? ? ?FSLDMA_EXTERNAL_START,
>> + ? ? ? TI_DMA_v1_STRIDE_CONFIG,
Yep unless we make it generic DMA_STRIDE_CONFIG simply, this makes
a lot of sense.
Linus Walleij
next prev parent reply other threads:[~2011-07-12 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 15:03 [PATCH] dmaengine: add dma_ctrl_cmd to pass buffer stride configuration Sundaram Raju
2011-07-11 9:28 ` Linus Walleij
2011-07-11 21:39 ` Dan Williams
2011-07-12 9:58 ` Linus Walleij
2011-07-12 10:15 ` Raju, Sundaram
2011-07-12 4:17 ` Jassi Brar
2011-07-12 10:03 ` Linus Walleij [this message]
2011-07-12 10:56 ` Raju, Sundaram
2011-07-12 11:09 ` Linus Walleij
2011-07-12 11:20 ` Jassi Brar
2011-07-12 11:31 ` Raju, Sundaram
2011-07-12 12:45 ` Jassi Brar
2011-07-18 7:51 ` Raju, Sundaram
2011-07-23 20:35 ` Jassi Brar
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=CACRpkdbLg0+_2kpi4NizFj0fDWb6QPtkcKirKgoH+83vGD0O0A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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).