From: Mark Brown <broonie@kernel.org>
To: Vinod <vkoul@kernel.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Lars-Peter Clausen <lars@metafoo.de>,
dmaengine@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: dma: add support for reporting pause and resume separately
Date: Mon, 9 Jul 2018 12:17:50 +0100 [thread overview]
Message-ID: <20180709111750.GC16082@sirena.org.uk> (raw)
On Wed, Jul 04, 2018 at 12:30:33PM +0530, Vinod wrote:
> > Existing clients of dma_get_slave_caps() have been checked and the only
> > driver which rely on proper channel resuming is soc-generic-dmaengine-pcm
> > driver, which has been updated to check the newly added capability.
> > Existing 'cmd_pause' now only indicates that DMA engine support pausing
> > given DMA channel.
> The change looks fine to me. I was hoping that serial would also check
> this..
> Mark, Lars you okay with this?
Acked-by: Mark Brown <broonie@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Vinod <vkoul@kernel.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Lars-Peter Clausen <lars@metafoo.de>,
dmaengine@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] dma: add support for reporting pause and resume separately
Date: Mon, 9 Jul 2018 12:17:50 +0100 [thread overview]
Message-ID: <20180709111750.GC16082@sirena.org.uk> (raw)
In-Reply-To: <20180704070033.GA22377@vkoul-mobl>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
On Wed, Jul 04, 2018 at 12:30:33PM +0530, Vinod wrote:
> > Existing clients of dma_get_slave_caps() have been checked and the only
> > driver which rely on proper channel resuming is soc-generic-dmaengine-pcm
> > driver, which has been updated to check the newly added capability.
> > Existing 'cmd_pause' now only indicates that DMA engine support pausing
> > given DMA channel.
> The change looks fine to me. I was hoping that serial would also check
> this..
> Mark, Lars you okay with this?
Acked-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-07-09 11:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 11:17 Mark Brown [this message]
2018-07-09 11:17 ` [PATCH] dma: add support for reporting pause and resume separately Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2018-07-09 17:29 Vinod Koul
2018-07-09 17:29 ` [PATCH] " Vinod
2018-07-06 6:22 Marek Szyprowski
2018-07-06 6:22 ` [PATCH] " Marek Szyprowski
2018-07-06 6:00 Vinod Koul
2018-07-06 6:00 ` [PATCH] " Vinod
2018-07-04 10:38 Andy Shevchenko
2018-07-04 10:38 ` [PATCH] " Andy Shevchenko
2018-07-04 7:00 Vinod Koul
2018-07-04 7:00 ` [PATCH] " Vinod
2018-07-02 13:08 Marek Szyprowski
2018-07-02 13:08 ` [PATCH] " Marek Szyprowski
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=20180709111750.GC16082@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=b.zolnierkie@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=vkoul@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.