From: Magnus Damm <magnus.damm@gmail.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
linux-mmc@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Ian Molton <ian@mnementh.co.uk>
Subject: Re: [PATCH 6/8] SH: Add SDHI DMA support to ms7724se
Date: Wed, 21 Apr 2010 20:18:26 -0400 [thread overview]
Message-ID: <m2xaec7e5c31004211718t85936386k6c0f09684b17b10f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1004211735180.5292@axis700.grange>
On Wed, Apr 21, 2010 at 11:37 AM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:
> @@ -456,11 +458,20 @@ static struct resource sdhi0_cn7_resources[] = {
> },
> };
>
> +static struct sh_mobile_sdhi_info sh7724_sdhi0_data = {
> + .dma_slave_tx = SHDMA_SLAVE_SDHI0_TX,
> + .dma_slave_rx = SHDMA_SLAVE_SDHI0_RX,
> + .tmio_flags = TMIO_IMMEDIATE_RX_COMPLETE,
> +};
> +
> static struct platform_device sdhi0_cn7_device = {
> .name = "sh_mobile_sdhi",
> .id = 0,
> .num_resources = ARRAY_SIZE(sdhi0_cn7_resources),
> .resource = sdhi0_cn7_resources,
> + .dev = {
> + .platform_data = &sh7724_sdhi0_data,
> + },
> .archdata = {
> .hwblk_id = HWBLK_SDHI0,
> },
> @@ -479,11 +490,19 @@ static struct resource sdhi1_cn8_resources[] = {
> },
> };
>
> +static struct sh_mobile_sdhi_info sh7724_sdhi1_data = {
> + .dma_slave_tx = SHDMA_SLAVE_SDHI1_TX,
> + .dma_slave_rx = SHDMA_SLAVE_SDHI1_RX,
And these two are the opposite of Ecovec even though both are sh7724? Hm..
/ magnus
next prev parent reply other threads:[~2010-04-22 0:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 15:36 [PATCH 0/8] add DMA support to tmio_mmc, using dmaengine API, use it on SH Guennadi Liakhovetski
2010-04-21 15:36 ` [PATCH 1/8] SH: constify multiple DMA related objects and references to them Guennadi Liakhovetski
2010-04-26 7:10 ` Paul Mundt
2010-04-21 15:36 ` [PATCH 2/8] SH: add DMA slave IDs for two SDHI controllers, add slaves to sh7722 Guennadi Liakhovetski
2010-04-22 0:02 ` Magnus Damm
2010-04-22 6:28 ` Guennadi Liakhovetski
2010-04-22 7:05 ` Magnus Damm
2010-04-22 9:38 ` Guennadi Liakhovetski
2010-04-21 15:36 ` [PATCH 3/8] SH: add DMA slave definitions to sh7724 Guennadi Liakhovetski
2010-04-21 15:37 ` [PATCH 4/8] MMC: add DMA support to tmio_mmc driver, when used on SuperH Guennadi Liakhovetski
2010-04-22 0:12 ` Magnus Damm
2010-04-22 9:51 ` Guennadi Liakhovetski
2010-04-21 15:37 ` [PATCH 5/8] SH: Add SDHI DMA support to ecovec Guennadi Liakhovetski
2010-04-22 0:16 ` Magnus Damm
2010-04-21 15:37 ` [PATCH 6/8] SH: Add SDHI DMA support to ms7724se Guennadi Liakhovetski
2010-04-22 0:18 ` Magnus Damm [this message]
2010-04-22 6:20 ` Guennadi Liakhovetski
2010-04-21 15:37 ` [PATCH 7/8] SH: Add SDHI DMA support to kfr2r09 Guennadi Liakhovetski
2010-04-21 15:37 ` [PATCH 8/8] SH: Add SDHI DMA support to migor Guennadi Liakhovetski
2010-04-27 10:38 ` [PATCH 0/8] add DMA support to tmio_mmc, using dmaengine API, use it on SH Guennadi Liakhovetski
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=m2xaec7e5c31004211718t85936386k6c0f09684b17b10f@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=ian@mnementh.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.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).