From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] mmc: sh_mmcif: Silence DMA slave ID compile warnings on 64-bit
Date: Wed, 12 Aug 2015 16:50:39 +0200 [thread overview]
Message-ID: <1539991.LpcThZV47z@wuerfel> (raw)
In-Reply-To: <1439297314-29118-1-git-send-email-geert+renesas@glider.be>
On Tuesday 11 August 2015 14:48:34 Geert Uytterhoeven wrote:
> dma_cap_mask_t mask;
> @@ -413,12 +413,11 @@ sh_mmcif_request_dma_one(struct sh_mmcif_host *host,
> dma_cap_set(DMA_SLAVE, mask);
>
> if (pdata)
> - slave_data = direction == DMA_MEM_TO_DEV ?
> - (void *)pdata->slave_id_tx :
> - (void *)pdata->slave_id_rx;
> + slave_id = direction == DMA_MEM_TO_DEV ?
> + pdata->slave_id_tx : pdata->slave_id_rx;
>
> chan = dma_request_slave_channel_compat(mask, shdma_chan_filter,
> - slave_data, dev,
> + (void *)(uintptr_t)slave_id, dev,
> direction == DMA_MEM_TO_DEV ? "tx" : "rx");
>
> dev_dbg(dev, "%s: %s: got channel %p\n", __func__,
How about changing the type of the slave_id_rx/slave_id_tx fields
to void*? That way, the hack can be moved to arch/sh/boards/board-sh7757lcr.c,
which is now the only file passing data this way. Ideally, we'd also
pass the shdma_chan_filter function pointer in pdata to avoid the link
time dependency on a particular dmaengine driver.
Arnd
next prev parent reply other threads:[~2015-08-12 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 12:48 [PATCH] mmc: sh_mmcif: Silence DMA slave ID compile warnings on 64-bit Geert Uytterhoeven
2015-08-12 14:50 ` Arnd Bergmann [this message]
2015-08-12 15:13 ` Geert Uytterhoeven
2015-08-15 20:26 ` Arnd Bergmann
2015-08-17 12:17 ` Geert Uytterhoeven
2015-08-20 13:29 ` Arnd Bergmann
2015-08-17 13:02 ` Geert Uytterhoeven
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=1539991.LpcThZV47z@wuerfel \
--to=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ulf.hansson@linaro.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