From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
vireshk@kernel.org
Subject: Re: dmaengine: dw-dmac: Custom cyclic API (Why?)
Date: Mon, 02 Jan 2017 10:38:00 +0200 [thread overview]
Message-ID: <1483346280.9552.181.camel@linux.intel.com> (raw)
In-Reply-To: <99eeb12c-fd4f-7982-4832-61116fd641d3@synopsys.com>
On Fri, 2016-12-30 at 12:05 +0000, Jose Abreu wrote:
> ++dw-dmac Maintainers
>
>
> On 30-12-2016 11:32, Jose Abreu wrote:
> > Hi All,
> >
> >
> > I am going to work with dw-dmac AHB controller and I wanted to
> > use SND_DMAENGINE_PCM. In order to use this, a standard DMA
> > driver with cyclic support is needed. I found out that dw-dmac is
> > capable of cyclic transfers but instead of using the DMA engine
> > standard cyclic API it uses a custom API. Is there any specific
> > reason for this? What is the effort to change the custom API to a
> > standard DMA engine cyclic API?
> >
Because it was a predecessor of generic implementation.
I used to have some semi-finished patch to switch to generic API, though
at that point I had no means to test it.
Since I eventually got iDMA 32-bit, which is used as LPE Audio DMA
engine, support in my branch I might test it in the future, though I
think someone else would be much faster than me.
So, I can share whatever I have to the topic with someone who is really
interested to do that task.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-01-02 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 11:32 Jose Abreu
2016-12-30 12:05 ` Jose Abreu
2017-01-02 8:38 ` Andy Shevchenko [this message]
2017-01-02 10:18 ` Vinod Koul
2017-01-02 10:58 ` Viresh Kumar
2017-01-02 11:30 ` Andy Shevchenko
2017-01-02 13:56 ` Jose Abreu
2017-04-04 16:23 ` Andy Shevchenko
2017-04-04 16:43 ` Jose Abreu
2017-05-22 18:17 ` Andy Shevchenko
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=1483346280.9552.181.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jose.Abreu@synopsys.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vireshk@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
Powered by JetHome