From: Matt Porter <mporter@ti.com>
To: Venkatraman S <svenkatr@ti.com>, Chris Ball <cjb@laptop.org>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
Tony Lindgren <tony@atomide.com>,
Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>,
Linux OMAP List <linux-omap@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Dan Williams <djbw@fb.com>,
Jon Hunter <jon-hunter@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: [PATCH 0/3] omap_hsmmc DT DMA Client support
Date: Fri, 1 Feb 2013 16:01:16 -0500 [thread overview]
Message-ID: <1359752479-29427-1-git-send-email-mporter@ti.com> (raw)
This series adds DT DMA Engine Client support to the omap_hsmmc.
It leverages the generic DMA OF helpers in -next and the
dma_request_slave_channel_compat() wrapper introduced in the
AM33XX DMA Engine series to support DMA in omap_hsmmc on platforms
booting via DT. These platforms include omap2/3/4/5 and am33xx.
These patches were split out from the v5 version of the AM33XX DMA
series and split from the EDMA-specific omap_hsmmc changes.
The series depends on the following patches:
- dmaengine DT support and edma dmaengine driver fix from
the git://git.infradead.org/users/vkoul/slave-dma.git next
branch
- dma_request_slave_channel_compat() support
https://patchwork.kernel.org/patch/2081671/
The series with all dependencies can be found at
https://github.com/ohporter/linux/tree/omap-hsmmc-dt-dmaengine-v1
Matt Porter (2):
mmc: omap_hsmmc: convert to dma_request_slave_channel_compat()
mmc: omap_hsmmc: add generic DMA request support to the DT binding
Santosh Shilimkar (1):
mmc: omap_hsmmc: Skip platform_get_resource_byname() for dt case
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 26 +++++++++++++-
drivers/mmc/host/omap_hsmmc.c | 38 ++++++++++++--------
2 files changed, 48 insertions(+), 16 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-02-01 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 21:01 Matt Porter [this message]
[not found] ` <1359752479-29427-1-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
2013-02-01 21:01 ` [PATCH 1/3] mmc: omap_hsmmc: convert to dma_request_slave_channel_compat() Matt Porter
[not found] ` <1359752479-29427-2-git-send-email-mporter-l0cyMroinI0@public.gmane.org>
2013-02-02 7:05 ` Santosh Shilimkar
2013-02-01 21:01 ` [PATCH 2/3] mmc: omap_hsmmc: Skip platform_get_resource_byname() for dt case Matt Porter
2013-02-01 21:01 ` [PATCH 3/3] mmc: omap_hsmmc: add generic DMA request support to the DT binding Matt Porter
2013-02-02 7:06 ` Santosh Shilimkar
2013-02-06 12:41 ` [PATCH 0/3] omap_hsmmc DT DMA Client support Lars Poeschel
2013-02-06 13:23 ` Matt Porter
2013-02-06 13:38 ` Arnd Bergmann
2013-02-11 17:34 ` Chris Ball
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=1359752479-29427-1-git-send-email-mporter@ti.com \
--to=mporter@ti.com \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=djbw@fb.com \
--cc=grant.likely@secretlab.ca \
--cc=jon-hunter@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=santosh.shilimkar@ti.com \
--cc=svenkatr@ti.com \
--cc=tony@atomide.com \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).