From: arnd.bergmann@linaro.org (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] mtd: sh_flctl: Add device tree support
Date: Tue, 2 Oct 2012 20:47:49 +0000 [thread overview]
Message-ID: <201210022047.50064.arnd.bergmann@linaro.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1210021602250.15778@axis700.grange>
On Tuesday 02 October 2012, Guennadi Liakhovetski wrote:
> >
> > Since you are also adding dma-engine support, I would suggest you specify
> > a "dmas" and "dma-names" property as well, so the device can find the
> > right dma channel. The code might not do that yet while you're still
> > sorting out the dependencies (and the sh dmaengine code is not yet
> > converted to DT), but I think it would be good to nail down the binding
> > for this device.
>
> Have DMA DT bindings been accepted yet, are they fixed? Wouldn't it be
> better to wait until patches appear in a tree, at least with high
> probability heading towards the mainline, or have they already?
>
I think they ended up not getting scheduled for 3.7, which is a bit disappointing
after we got an agreement on the binding. However, I am rather confident that
we won't change the binding again, at least I don't see how they would change
in a way that would impact the binding document for a device using a DMA channel.
Arnd
next prev parent reply other threads:[~2012-10-02 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 13:12 [PATCH 0/2] Add DMA and device tree support to the flash controller FLCTL Bastian Hecht
2012-10-02 13:12 ` [PATCH 1/2] mtd: sh_flctl: Add DMA capabilty Bastian Hecht
2012-10-02 13:55 ` Guennadi Liakhovetski
2012-10-04 10:12 ` Bastian Hecht
2012-10-02 13:12 ` [PATCH 2/2] mtd: sh_flctl: Add device tree support Bastian Hecht
2012-10-02 13:54 ` Arnd Bergmann
2012-10-02 14:04 ` Guennadi Liakhovetski
2012-10-02 20:47 ` Arnd Bergmann [this message]
2012-10-04 10:07 ` Bastian Hecht
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=201210022047.50064.arnd.bergmann@linaro.org \
--to=arnd.bergmann@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).