From: vinod.koul@intel•com (Vinod Koul)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4] dmaengine: sirf: enable generic dt binding for dma channels
Date: Mon, 17 Mar 2014 10:21:05 +0530 [thread overview]
Message-ID: <20140317045105.GB1976@intel.com> (raw)
In-Reply-To: <CAGsJ_4zMYGTS4CyCsTAH_5PMK3v4Pr+e88YjXL=d3A=EjPf9rQ@mail.gmail.com>
On Sat, Mar 01, 2014 at 10:49:18AM +0800, Barry Song wrote:
> 2014-01-20 17:35 GMT+08:00 Barry Song <21cnbao@gmail•com>:
> > 2014/1/20 Vinod Koul <vinod.koul@intel•com>:
> >> On Wed, Jan 08, 2014 at 10:12:49PM +0800, Barry Song wrote:
> >>> From: Barry Song <Baohua.Song@csr•com>
> >>>
> >>> move to support of_dma_request_slave_channel() and dma_request_slave_channel.
> >>> we add a xlate() to let dma clients be able to find right dma_chan by generic
> >>> "dmas" properties in dts.
> >>>
> >>> Cc: Mark Rutland <mark.rutland@arm•com>
> >>> Cc: Lars-Peter Clausen <lars@metafoo•de>
> >>> Signed-off-by: Barry Song <Baohua.Song@csr•com>
> >> Look okay, need an ACk from DT maintainers before I can apply...
>
> Hi Vinod,
> v5 is sent to devicetree list and there is no object.
> http://www.spinics.net/lists/devicetree/msg19677.html
> this patch is using general dt-binding for dma completely same with
> other dma drivers, there is no special binding here.
> so i think there is no reason to wait for merging since now updates
> for its clients e.g. SPI, UART have been in 3.14-rc.
I still need the ack for DT folks... Seems still missing :(
--
~Vinod
next prev parent reply other threads:[~2014-03-17 4:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 14:12 [PATCH v4] dmaengine: sirf: enable generic dt binding for dma channels Barry Song
2014-01-20 7:48 ` Vinod Koul
2014-01-20 9:35 ` Barry Song
2014-01-20 8:47 ` Vinod Koul
2014-01-20 10:20 ` Barry Song
2014-03-01 2:49 ` Barry Song
2014-03-17 4:51 ` Vinod Koul [this message]
2014-03-18 2:02 ` Barry Song
2014-03-18 12:20 ` Arnd Bergmann
2014-01-20 10:30 ` Barry Song
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=20140317045105.GB1976@intel.com \
--to=vinod.koul@intel$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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