From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 2/2] dmaengine: sun6i: Add driver for the Allwinner A31 DMA controller
Date: Tue, 29 Jul 2014 13:05:56 +0100 [thread overview]
Message-ID: <20140729120556.GS17528@sirena.org.uk> (raw)
In-Reply-To: <20140728150911.GN3952@lukather>
On Mon, Jul 28, 2014 at 05:09:11PM +0200, Maxime Ripard wrote:
> On Sun, Jul 27, 2014 at 07:49:42PM +0100, Mark Brown wrote:
> > There's supposed to be facilities appearing in the generic clock code
> > for specifying default clock tree configurations via the DT - it's quite
> > a common requirement after all. It sounds like that should be able to
> > do the job here. Not sure if these have gone in yet or not but there's
> > quite a bit of demand.
> As far as I'm aware, it's not been merged yet.
Well, another reason to push Mike about it then I guess - there are a
lot of these case cropping up.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140729/d7dcd600/attachment.sig>
next prev parent reply other threads:[~2014-07-29 12:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 13:20 [PATCH v10 0/2] Add support for the Allwinner A31 DMA Controller Maxime Ripard
2014-06-30 13:20 ` [PATCH v10 1/2] Documentation: dt: Add Allwinner A31 DMA controller bindings Maxime Ripard
2014-06-30 13:20 ` [PATCH v10 2/2] dmaengine: sun6i: Add driver for the Allwinner A31 DMA controller Maxime Ripard
2014-06-30 14:20 ` Mark Rutland
2014-06-30 15:19 ` Maxime Ripard
2014-06-30 15:33 ` Mark Rutland
2014-07-01 7:21 ` Maxime Ripard
2014-07-01 12:48 ` Mark Rutland
2014-07-04 7:57 ` Maxime Ripard
2014-07-06 15:22 ` Arnd Bergmann
2014-07-07 12:41 ` Maxime Ripard
2014-07-27 18:49 ` Mark Brown
2014-07-28 15:09 ` Maxime Ripard
2014-07-29 12:05 ` Mark Brown [this message]
2014-07-06 3:23 ` [linux-sunxi] " Emilio López
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=20140729120556.GS17528@sirena.org.uk \
--to=broonie@kernel.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).