From: Arnd Bergmann <arnd@arndb.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: Russell King <linux@arm.linux.org.uk>,
linus.walleij@stericsson.com, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, Chris Ball <cjb@laptop.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mmc: mmci: Allow MMCI to request channels with information acquired from DT
Date: Wed, 17 Apr 2013 17:31:56 +0200 [thread overview]
Message-ID: <201304171731.56292.arnd@arndb.de> (raw)
In-Reply-To: <20130417150437.GA3137@gmail.com>
On Wednesday 17 April 2013, Lee Jones wrote:
> > This looks unnecessarily complex.
>
> That thought did cross my mind.
>
> > Why not just do dma_request_slave_channel_compat() unconditionally here?
>
> So how about something like this instead, as it keeps the current
> semantics, and only differs in the case of DT.
Yes, looks better.
> @@ -298,14 +298,16 @@ static void mmci_init_sg(struct mmci_host *host, struct mmc_data *data)
> * no custom DMA interfaces are supported.
> */
> #ifdef CONFIG_DMA_ENGINE
> -static void mmci_dma_setup(struct mmci_host *host)
> +static void mmci_dma_setup(struct amba_device *dev,
> + struct mmci_host *host)
> {
> + struct device_node *np = dev->dev.of_node;
> struct mmci_platform_data *plat = host->plat;
> const char *rxname, *txname;
> dma_cap_mask_t mask;
>
> - if (!plat || !plat->dma_filter) {
> - dev_info(mmc_dev(host->mmc), "no DMA platform data\n");
> + if (!(plat && plat->dma_filter) && !np) {
> + dev_info(mmc_dev(host->mmc), "no DMA platform data or DT\n");
> return;
> }
I think you can further simplify this, given that in the DT case we always
allocate a zeroed mmci_platform_data for host->plat, so !plat cannot happen
when we get here.
> @@ -321,19 +323,21 @@ static void mmci_dma_setup(struct mmci_host *host)
> * attempt to use it bidirectionally, however if it is
> * is specified but cannot be located, DMA will be disabled.
> */
> - if (plat->dma_rx_param) {
> - host->dma_rx_channel = dma_request_channel(mask,
> - plat->dma_filter,
> - plat->dma_rx_param);
> + if ((plat && plat->dma_rx_param) || np) {
> + host->dma_rx_channel = dma_request_slave_channel_compat(mask,
> + (plat) ? plat->dma_filter : NULL,
> + (plat) ? plat->dma_rx_param : NULL,
> + &dev->dev, "rx");
> /* E.g if no DMA hardware is present */
> if (!host->dma_rx_channel)
> dev_err(mmc_dev(host->mmc), "no RX DMA channel\n");
And based on that, you can unconditionally pass plat->dma_filter and
plat->dma_rx_param here. In case of DT, they will be NULL, and they
will not be used either.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: mmci: Allow MMCI to request channels with information acquired from DT
Date: Wed, 17 Apr 2013 17:31:56 +0200 [thread overview]
Message-ID: <201304171731.56292.arnd@arndb.de> (raw)
In-Reply-To: <20130417150437.GA3137@gmail.com>
On Wednesday 17 April 2013, Lee Jones wrote:
> > This looks unnecessarily complex.
>
> That thought did cross my mind.
>
> > Why not just do dma_request_slave_channel_compat() unconditionally here?
>
> So how about something like this instead, as it keeps the current
> semantics, and only differs in the case of DT.
Yes, looks better.
> @@ -298,14 +298,16 @@ static void mmci_init_sg(struct mmci_host *host, struct mmc_data *data)
> * no custom DMA interfaces are supported.
> */
> #ifdef CONFIG_DMA_ENGINE
> -static void mmci_dma_setup(struct mmci_host *host)
> +static void mmci_dma_setup(struct amba_device *dev,
> + struct mmci_host *host)
> {
> + struct device_node *np = dev->dev.of_node;
> struct mmci_platform_data *plat = host->plat;
> const char *rxname, *txname;
> dma_cap_mask_t mask;
>
> - if (!plat || !plat->dma_filter) {
> - dev_info(mmc_dev(host->mmc), "no DMA platform data\n");
> + if (!(plat && plat->dma_filter) && !np) {
> + dev_info(mmc_dev(host->mmc), "no DMA platform data or DT\n");
> return;
> }
I think you can further simplify this, given that in the DT case we always
allocate a zeroed mmci_platform_data for host->plat, so !plat cannot happen
when we get here.
> @@ -321,19 +323,21 @@ static void mmci_dma_setup(struct mmci_host *host)
> * attempt to use it bidirectionally, however if it is
> * is specified but cannot be located, DMA will be disabled.
> */
> - if (plat->dma_rx_param) {
> - host->dma_rx_channel = dma_request_channel(mask,
> - plat->dma_filter,
> - plat->dma_rx_param);
> + if ((plat && plat->dma_rx_param) || np) {
> + host->dma_rx_channel = dma_request_slave_channel_compat(mask,
> + (plat) ? plat->dma_filter : NULL,
> + (plat) ? plat->dma_rx_param : NULL,
> + &dev->dev, "rx");
> /* E.g if no DMA hardware is present */
> if (!host->dma_rx_channel)
> dev_err(mmc_dev(host->mmc), "no RX DMA channel\n");
And based on that, you can unconditionally pass plat->dma_filter and
plat->dma_rx_param here. In case of DT, they will be NULL, and they
will not be used either.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linus.walleij@stericsson.com,
Russell King <linux@arm.linux.org.uk>,
Chris Ball <cjb@laptop.org>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: mmci: Allow MMCI to request channels with information acquired from DT
Date: Wed, 17 Apr 2013 17:31:56 +0200 [thread overview]
Message-ID: <201304171731.56292.arnd@arndb.de> (raw)
In-Reply-To: <20130417150437.GA3137@gmail.com>
On Wednesday 17 April 2013, Lee Jones wrote:
> > This looks unnecessarily complex.
>
> That thought did cross my mind.
>
> > Why not just do dma_request_slave_channel_compat() unconditionally here?
>
> So how about something like this instead, as it keeps the current
> semantics, and only differs in the case of DT.
Yes, looks better.
> @@ -298,14 +298,16 @@ static void mmci_init_sg(struct mmci_host *host, struct mmc_data *data)
> * no custom DMA interfaces are supported.
> */
> #ifdef CONFIG_DMA_ENGINE
> -static void mmci_dma_setup(struct mmci_host *host)
> +static void mmci_dma_setup(struct amba_device *dev,
> + struct mmci_host *host)
> {
> + struct device_node *np = dev->dev.of_node;
> struct mmci_platform_data *plat = host->plat;
> const char *rxname, *txname;
> dma_cap_mask_t mask;
>
> - if (!plat || !plat->dma_filter) {
> - dev_info(mmc_dev(host->mmc), "no DMA platform data\n");
> + if (!(plat && plat->dma_filter) && !np) {
> + dev_info(mmc_dev(host->mmc), "no DMA platform data or DT\n");
> return;
> }
I think you can further simplify this, given that in the DT case we always
allocate a zeroed mmci_platform_data for host->plat, so !plat cannot happen
when we get here.
> @@ -321,19 +323,21 @@ static void mmci_dma_setup(struct mmci_host *host)
> * attempt to use it bidirectionally, however if it is
> * is specified but cannot be located, DMA will be disabled.
> */
> - if (plat->dma_rx_param) {
> - host->dma_rx_channel = dma_request_channel(mask,
> - plat->dma_filter,
> - plat->dma_rx_param);
> + if ((plat && plat->dma_rx_param) || np) {
> + host->dma_rx_channel = dma_request_slave_channel_compat(mask,
> + (plat) ? plat->dma_filter : NULL,
> + (plat) ? plat->dma_rx_param : NULL,
> + &dev->dev, "rx");
> /* E.g if no DMA hardware is present */
> if (!host->dma_rx_channel)
> dev_err(mmc_dev(host->mmc), "no RX DMA channel\n");
And based on that, you can unconditionally pass plat->dma_filter and
plat->dma_rx_param here. In case of DT, they will be NULL, and they
will not be used either.
Arnd
next prev parent reply other threads:[~2013-04-17 15:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 13:32 [PATCH] mmc: mmci: Allow MMCI to request channels with information acquired from DT Lee Jones
2013-04-17 13:32 ` Lee Jones
2013-04-17 13:50 ` Arnd Bergmann
2013-04-17 13:50 ` Arnd Bergmann
2013-04-17 15:04 ` Lee Jones
2013-04-17 15:04 ` Lee Jones
2013-04-17 15:31 ` Arnd Bergmann [this message]
2013-04-17 15:31 ` Arnd Bergmann
2013-04-17 15:31 ` Arnd Bergmann
2013-04-18 8:02 ` Lee Jones
2013-04-18 8:02 ` Lee Jones
2013-04-18 8:15 ` Russell King - ARM Linux
2013-04-18 8:15 ` Russell King - ARM Linux
2013-04-18 9:25 ` Arnd Bergmann
2013-04-18 9:25 ` Arnd Bergmann
2013-04-18 9:30 ` Russell King - ARM Linux
2013-04-18 9:30 ` Russell King - ARM Linux
2013-04-18 8:21 ` Ulf Hansson
2013-04-18 8:21 ` Ulf Hansson
-- strict thread matches above, loose matches on Subject: below --
2013-04-24 10:58 Lee Jones
2013-04-24 10:58 ` Lee Jones
2013-04-30 13:01 ` Linus Walleij
2013-04-30 13:01 ` Linus Walleij
2013-04-30 13:12 ` Lee Jones
2013-04-30 13:12 ` Lee Jones
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=201304171731.56292.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.