mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>, Vinod Koul <vinod.koul@intel.com>
Cc: "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, 22 May 2017 21:17:48 +0300	[thread overview]
Message-ID: <1495477068.6967.63.camel@linux.intel.com> (raw)
In-Reply-To: <35f38fbf-d411-3cf2-cf41-9638a085b715@synopsys.com>

On Tue, 2017-04-04 at 17:43 +0100, Jose Abreu wrote:
> 
> On 04-04-2017 17:23, Andy Shevchenko wrote:
> > On Mon, 2017-01-02 at 13:56 +0000, Jose Abreu wrote:
> > > On 02-01-2017 11:30, Andy Shevchenko wrote:
> > > > 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:
> > > > 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).
> > > > 
> > > 
> > > Thank you all for the info. I don't have the HW ready to test yet
> > > (I was collecting some info first), but when I do I can test on
> > > my side using Designware I2S and ALSA SoC DMA engine.
> > 
> > Just TWIMC, AVR32 is going to be removed from kernel.
> > It means in particularly I will follow up and remove related bits in
> > dw_dmac driver, including custom cyclic API.
> > 
> 
> Thanks for sharing this! Unfortunately the plans to include a DMA
> for I2S audio were postponed so I never got to the point of
> implementing/testing it. As I don't see any plans in using this
> cyclic DMA for now I guess if I need to use it I will implement
> it again using the standard cyclic DMA engine API.

Just heads up TWIMC the custom API has been removed.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2017-05-22 18:17 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
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 [this message]

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=1495477068.6967.63.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome