From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dylan Reid <dgreid@chromium.org>
Cc: alsa-devel@alsa-project.org, kgene.kim@samsung.com,
clemens@ladisch.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ASoC: samsung dma - Don't indicate support for pause/resume.
Date: Thu, 6 Sep 2012 18:56:39 +0800 [thread overview]
Message-ID: <20120906105626.GH22330@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1346488699-11027-1-git-send-email-dgreid@chromium.org>
On Sat, Sep 01, 2012 at 01:38:19AM -0700, Dylan Reid wrote:
> The pause and resume operations indicate that the stream can be
> un-paused/resumed from the exact location they were paused/suspended.
> This is not true for this driver, the pause and suspend triggers share
> the same code path with stop, they flush all pending DMA transfers.
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ASoC: samsung dma - Don't indicate support for pause/resume.
Date: Thu, 6 Sep 2012 18:56:39 +0800 [thread overview]
Message-ID: <20120906105626.GH22330@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1346488699-11027-1-git-send-email-dgreid@chromium.org>
On Sat, Sep 01, 2012 at 01:38:19AM -0700, Dylan Reid wrote:
> The pause and resume operations indicate that the stream can be
> un-paused/resumed from the exact location they were paused/suspended.
> This is not true for this driver, the pause and suspend triggers share
> the same code path with stop, they flush all pending DMA transfers.
Applied, thanks.
next prev parent reply other threads:[~2012-09-06 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 8:38 [PATCH v2] ASoC: samsung dma - Don't indicate support for pause/resume Dylan Reid
2012-09-01 8:38 ` Dylan Reid
2012-09-06 10:56 ` Mark Brown [this message]
2012-09-06 10:56 ` Mark Brown
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=20120906105626.GH22330@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=dgreid@chromium.org \
--cc=kgene.kim@samsung.com \
--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 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.