From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: 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 13:30:03 +0200 [thread overview]
Message-ID: <1483356603.9552.197.camel@linux.intel.com> (raw)
In-Reply-To: <20170102101802.GX3573@localhost>
On Mon, 2017-01-02 at 15:48 +0530, Vinod Koul wrote:
> On Mon, Jan 02, 2017 at 10:38:00AM +0200, Andy Shevchenko wrote:
> > On Fri, 2016-12-30 at 12:05 +0000, Jose Abreu wrote:
> > > ++dw-dmac Maintainers
> > 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.
>
> no we can't, since the DSP is involved and takes control, so unless we
> do
> lots of nasty hacks, it won't be testable. I don't see the ROI for
> such an
> effort.
Thanks for clarification
> btw, feel free to test and send patches if you have such a h/w
Actually we have AVR32 connected to our lab. So, I can test it there,
but I rather need a patch to use some dummy stub instead of codec (it
has no codec connected).
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-01-02 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 11:32 dmaengine: dw-dmac: Custom cyclic API (Why?) Jose Abreu
2016-12-30 12:05 ` Jose Abreu
2017-01-02 8:38 ` Andy Shevchenko
2017-01-02 10:18 ` Vinod Koul
2017-01-02 10:58 ` Viresh Kumar
2017-01-02 11:30 ` Andy Shevchenko [this message]
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=1483356603.9552.197.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=vinod.koul@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.