From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] s3cmci: port DMA code to dmaengine API
Date: Tue, 20 May 2014 12:39:52 +0200 [thread overview]
Message-ID: <6897537.JWQLgZ3Zsx@wuerfel> (raw)
In-Reply-To: <CA+E=qVch0K+raN4dkPK6XzXqOQc4t433UyCJ2Qnc2uymgTq7cA@mail.gmail.com>
On Tuesday 20 May 2014 13:22:35 Vasily Khoruzhick wrote:
> Hi Arnd,
>
> On Mon, May 19, 2014 at 10:02 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > For this driver, you don't have to go that far, as long as it's
> > ensure that the pointer to the filter function is available to
> > the driver, i.e. you can't have a built-in s3mci driver when the
> > dmaengine driver is a loadable module.
>
> OK, so I guess I need to add explicit dependency on
> CONFIG_S3C24XX_DMAC for s3cmci driver.
>
> Btw, I didn't understand if it's acceptable to pass DMA channel number
> through DMA resource for non-DT case or not?
It's commonly done on certain SoCs, but I'd prefer to not start doing
it on those that don't do it today.
At the moment, we do it only on s3c64xx, s5p, davinci, omap1, and pxa
on ARM, as well as arch/blackfin and one MIPS machine.
I suppose we have to introduce it on s3c24xx in order to keep
supporting sound, unless we put the audio dma channels into
s3c_audio_pdata.
I think that would be a better approach, given that you also need
to put the filter function pointer for the audio stuff somewhere.
Maybe Mark Brown has a strong preference to how he wants this done
in the audio drivers, then you can do it the same way for s3cmci.
Arnd
next prev parent reply other threads:[~2014-05-20 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 18:03 [PATCH] s3cmci: port DMA code to dmaengine API Vasily Khoruzhick
2014-05-19 18:18 ` Arnd Bergmann
2014-05-19 18:54 ` Vasily Khoruzhick
2014-05-19 19:02 ` Arnd Bergmann
2014-05-19 19:39 ` Vasily Khoruzhick
2014-05-20 10:22 ` Vasily Khoruzhick
2014-05-20 10:39 ` Arnd Bergmann [this message]
2014-05-20 11:36 ` Vasily Khoruzhick
2014-05-20 11:51 ` Arnd Bergmann
2014-05-20 11:55 ` Vasily Khoruzhick
2014-05-20 12:26 ` Arnd Bergmann
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=6897537.JWQLgZ3Zsx@wuerfel \
--to=arnd@arndb.de \
--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