From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: nsekhar@ti.com, joelf@ti.com, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
dmaengine@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH 0/2] dma: edma: Allow to disable eDMA IRQ during cyclic transfer
Date: Mon, 28 Jul 2014 17:04:21 +0530 [thread overview]
Message-ID: <20140728113421.GA8181@intel.com> (raw)
In-Reply-To: <1405513761-23739-1-git-send-email-peter.ujfalusi@ti.com>
On Wed, Jul 16, 2014 at 03:29:19PM +0300, Peter Ujfalusi wrote:
> Hi,
>
> After this series clients can ask to not receive notifications after each period.
> In this case we can disable the completion interrupt since the position reporting
> does not rely on it for cyclic mode.
> Patchset for ASoC part has been sent which allows users space to take adventage
> of SNDRV_PCM_INFO_NO_PERIOD_WAKEUP:
> [1] http://mailman.alsa-project.org/pipermail/alsa-devel/2014-July/078993.html
Applied, thanks
Please use right subsystem name for patches, i have fixed that while
applying
--
~Vinod
prev parent reply other threads:[~2014-07-28 11:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 12:29 [PATCH 0/2] dma: edma: Allow to disable eDMA IRQ during cyclic transfer Peter Ujfalusi
2014-07-16 12:29 ` Peter Ujfalusi
2014-07-16 12:29 ` [PATCH 2/2] dma: edma: Support to suppress the period interrupts in cyclic mode Peter Ujfalusi
2014-07-16 12:29 ` Peter Ujfalusi
[not found] ` <1405513761-23739-1-git-send-email-peter.ujfalusi-l0cyMroinI0@public.gmane.org>
2014-07-16 12:29 ` [PATCH 1/2] dma: edma: Update caps->residue_granularity to match with reality Peter Ujfalusi
2014-07-16 12:29 ` Peter Ujfalusi
2014-07-28 6:13 ` [PATCH 0/2] dma: edma: Allow to disable eDMA IRQ during cyclic transfer Peter Ujfalusi
2014-07-28 6:13 ` Peter Ujfalusi
2014-07-28 11:34 ` Vinod Koul [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=20140728113421.GA8181@intel.com \
--to=vinod.koul@intel.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dmaengine@vger.kernel.org \
--cc=joelf@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=tglx@linutronix.de \
/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.