From: Vinod Koul <vinod.koul@intel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
Subject: Re: [PATCH v5 0/7] DMA: shdma: switch DT to use OF device ID tables
Date: Sun, 25 Aug 2013 13:06:57 +0530 [thread overview]
Message-ID: <20130825073656.GF8091@intel.com> (raw)
In-Reply-To: <1375455042-24093-1-git-send-email-g.liakhovetski@gmx.de>
On Fri, Aug 02, 2013 at 04:50:35PM +0200, Guennadi Liakhovetski wrote:
> In this version of shdma Device Tree support I preserved the DT
> configuration approach via OF device ID tables from v4, but now it is only
> used for the DT-mode, the C-version is left untouched. In this series I
> only include one platform: r8a73a4-based APE6EVM, if accepted, others can
> be added easily. I also took care not to include mach/*.h headers in
> driver .c files. To illustrate the use of DT DMA support for MMC DMA on
> APE6EVM a patch from a previously separate patch series "DMA for MMCIF and
> SDHI devices in DT mode"
I have applied all the dma patches, the ARM ones fail for me so should possible
go thru ARM tree.
thanks
~Vinod
next prev parent reply other threads:[~2013-08-25 8:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 14:50 [PATCH v5 0/7] DMA: shdma: switch DT to use OF device ID tables Guennadi Liakhovetski
2013-08-02 14:50 ` [PATCH v5 1/7] DMA: shdma: switch DT mode to use configuration data from a match table Guennadi Liakhovetski
2013-08-02 14:50 ` [PATCH v5 2/7] DMA: shdma: remove private and unused defines from a global header Guennadi Liakhovetski
2013-08-02 14:50 ` [PATCH v5 3/7] DMA: shdma: add a header with common for ARM SoCs defines Guennadi Liakhovetski
2013-08-02 14:50 ` [PATCH v5 4/7] DMA: shdma: add r8a73a4 DMAC data to the device ID table Guennadi Liakhovetski
2013-08-02 14:50 ` [PATCH v5 5/7] ARM: shmobile: r8a73a4: add a DMAC platform device and clock for it Guennadi Liakhovetski
2013-09-25 5:50 ` Simon Horman
2013-09-25 6:52 ` Guennadi Liakhovetski
2013-09-25 7:10 ` Simon Horman
2013-09-25 7:22 ` Guennadi Liakhovetski
2013-08-02 14:50 ` [PATCH v5 6/7] ARM: shmobile: r8a73a4: add a DT node and a clock alias for the DMAC Guennadi Liakhovetski
2013-09-25 5:53 ` Simon Horman
2013-09-25 8:01 ` Simon Horman
2013-08-02 14:50 ` [PATCH v5 7/7] ARM: shmobile: ape6evm-reference: enable DMA for the MMC interface Guennadi Liakhovetski
2013-09-25 5:54 ` Simon Horman
2013-09-25 7:56 ` Simon Horman
2013-09-25 8:07 ` Simon Horman
2013-08-25 7:36 ` Vinod Koul [this message]
2013-08-26 7:17 ` [PATCH v5 0/7] DMA: shdma: switch DT to use OF device ID tables Simon Horman
2013-08-26 7:49 ` Vinod Koul
2013-08-26 8:46 ` Simon Horman
2013-08-29 11:24 ` Guennadi Liakhovetski
2013-09-04 8:55 ` Simon Horman
2013-09-25 7:12 ` Simon Horman
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=20130825073656.GF8091@intel.com \
--to=vinod.koul@intel.com \
--cc=g.liakhovetski+renesas@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sergei.shtylyov@cogentembedded.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