From: Vinod Koul <vinod.koul@intel.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-kernel@vger.kernel.org, Dan Williams <djbw@fb.com>,
Matt Porter <matt@ohporter.com>
Subject: Re: [PATCH] dmaengine: add dma_slave_get_caps api
Date: Mon, 15 Jul 2013 15:53:33 +0530 [thread overview]
Message-ID: <20130715102332.GS16653@intel.com> (raw)
In-Reply-To: <51E3D463.3040200@metafoo.de>
On Mon, Jul 15, 2013 at 12:52:19PM +0200, Lars-Peter Clausen wrote:
> On 07/15/2013 11:57 AM, Vinod Koul wrote:
> > add new device callback .device_slave_caps api which can be used by clients to
> > query the dma channel capablties before they program the channel. This can help
> > is removing errors during the channel programming. Also add helper
> > dma_slave_get_caps API
> >
> > This patch folds the work done by Matt earlier
> > https://patchwork.kernel.org/patch/2094891/
> >
> > Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> > --
> > this version
> > changes api to include struct dma_slave_caps as arg
> > removed burst lengths, can be added when we have users
>
> Hi,
>
> it looks like you did send out v1 by accident.
Yes but problem wasnt sending wrong patch but generating patch without
comitting!
resent now...
I am planning to keep this on a branch which I wont rebase. That way users
(mostly ASoC for now), can merge this and get drivers converted.
~Vinod
next prev parent reply other threads:[~2013-07-15 11:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 8:54 [RFC] " Vinod Koul
2013-07-08 12:01 ` Lars-Peter Clausen
2013-07-08 13:40 ` Vinod Koul
2013-07-08 14:28 ` Lars-Peter Clausen
2013-07-08 14:03 ` Vinod Koul
2013-07-08 14:54 ` Lars-Peter Clausen
2013-07-15 9:57 ` [PATCH] " Vinod Koul
2013-07-15 10:52 ` Lars-Peter Clausen
2013-07-15 10:23 ` Vinod Koul [this message]
2013-07-15 10:21 ` Vinod Koul
2013-07-15 11:21 ` Lars-Peter Clausen
2013-07-15 15:51 ` Lars-Peter Clausen
2013-07-15 16:21 ` Vinod Koul
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=20130715102332.GS16653@intel.com \
--to=vinod.koul@intel.com \
--cc=djbw@fb.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@ohporter.com \
/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