public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: omap_hsmmc: don't print uninitialized variables
Date: Tue, 26 Jan 2016 16:52:40 +0200	[thread overview]
Message-ID: <56A78838.3050400@ti.com> (raw)
In-Reply-To: <1453737031-1959584-1-git-send-email-arnd@arndb.de>

On 01/25/2016 05:50 PM, Arnd Bergmann wrote:
> When DT based probing is used but the DMA request fails, the
> driver will print uninitialized stack data from the rx_req
> and tx_req variables, as indicated by this warning:
> 
> drivers/mmc/host/omap_hsmmc.c: In function 'omap_hsmmc_probe':
> drivers/mmc/host/omap_hsmmc.c:2162:3: warning: 'rx_req' may be used uninitialized in this function [-Wmaybe-uninitialized]
>    dev_err(mmc_dev(host->mmc), "unable to obtain RX DMA engine channel %u\n", rx_req);
> 
> This restructures the function to separate the simple DT probe
> from the more complex platform data code path, and only
> prints the information that is actually available and
> needed in case of an error, which makes it nicer to read
> and avoids the warning.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  drivers/mmc/host/omap_hsmmc.c | 48 +++++++++++++++++++++----------------------
>  1 file changed, 23 insertions(+), 25 deletions(-)
> 
> diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
> index b6639ea0bf18..e06b1881b6a1 100644
> --- a/drivers/mmc/host/omap_hsmmc.c
> +++ b/drivers/mmc/host/omap_hsmmc.c
> @@ -2002,8 +2002,6 @@ static int omap_hsmmc_probe(struct platform_device *pdev)
>  	struct resource *res;
>  	int ret, irq;
>  	const struct of_device_id *match;
> -	dma_cap_mask_t mask;
> -	unsigned tx_req, rx_req;
>  	const struct omap_mmc_of_data *data;
>  	void __iomem *base;
>  
> @@ -2133,7 +2131,17 @@ static int omap_hsmmc_probe(struct platform_device *pdev)
>  
>  	omap_hsmmc_conf_bus_power(host);
>  
> -	if (!pdev->dev.of_node) {
> +	host->tx_chan = dma_request_slave_channel(&pdev->dev, "tx");
> +	host->rx_chan = dma_request_slave_channel(&pdev->dev, "rx");
> +	if (!host->tx_chan || !host->rx_chan) {

While it is really unlikely that we are failing to get only one of the
channels... It means anyway that the omap_hsmmc is not usable, but we will
still try to get via legacy mode and there is a chance that we might get some
channel.

Too bad that I can not send the conversion to dma_request_chan() yet due to
missing things in arch...

It might be simpler to just remove the printout of the rx/tx_req from the
dev_err() when reporting failed channel requests...

> +		dma_cap_mask_t mask;
> +		unsigned tx_req, rx_req;
> +
> +		dev_err(mmc_dev(host->mmc), "falling back to manual DMA configuration\n");
> +
> +		dma_cap_zero(mask);
> +		dma_cap_set(DMA_SLAVE, mask);
> +
>  		res = platform_get_resource_byname(pdev, IORESOURCE_DMA, "tx");
>  		if (!res) {
>  			dev_err(mmc_dev(host->mmc), "cannot get DMA TX channel\n");
> @@ -2141,6 +2149,12 @@ static int omap_hsmmc_probe(struct platform_device *pdev)
>  			goto err_irq;
>  		}
>  		tx_req = res->start;
> +		host->tx_chan = dma_request_channel(mask, omap_dma_filter_fn, &tx_req);
> +		if (!host->rx_chan) {
> +			dev_err(mmc_dev(host->mmc), "unable to obtain TX DMA engine channel %u\n", tx_req);
> +			ret = -ENXIO;
> +			goto err_irq;
> +		}
>  
>  		res = platform_get_resource_byname(pdev, IORESOURCE_DMA, "rx");
>  		if (!res) {
> @@ -2149,29 +2163,13 @@ static int omap_hsmmc_probe(struct platform_device *pdev)
>  			goto err_irq;
>  		}
>  		rx_req = res->start;
> -	}
> -
> -	dma_cap_zero(mask);
> -	dma_cap_set(DMA_SLAVE, mask);
> -
> -	host->rx_chan =
> -		dma_request_slave_channel_compat(mask, omap_dma_filter_fn,
> -						 &rx_req, &pdev->dev, "rx");
> +		host->tx_chan = dma_request_channel(mask, omap_dma_filter_fn, &rx_req);
>  
> -	if (!host->rx_chan) {
> -		dev_err(mmc_dev(host->mmc), "unable to obtain RX DMA engine channel %u\n", rx_req);
> -		ret = -ENXIO;
> -		goto err_irq;
> -	}
> -
> -	host->tx_chan =
> -		dma_request_slave_channel_compat(mask, omap_dma_filter_fn,
> -						 &tx_req, &pdev->dev, "tx");
> -
> -	if (!host->tx_chan) {
> -		dev_err(mmc_dev(host->mmc), "unable to obtain TX DMA engine channel %u\n", tx_req);
> -		ret = -ENXIO;
> -		goto err_irq;
> +		if (!host->tx_chan) {
> +			dev_err(mmc_dev(host->mmc), "unable to obtain RX DMA engine channel %u\n", rx_req);
> +			ret = -ENXIO;
> +			goto err_irq;
> +		}
>  	}
>  
>  	/* Request IRQ for MMC operations */
> 


-- 
P?ter

  reply	other threads:[~2016-01-26 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 15:50 [PATCH] mmc: omap_hsmmc: don't print uninitialized variables Arnd Bergmann
2016-01-26 14:52 ` Peter Ujfalusi [this message]
2016-01-26 15:18   ` Arnd Bergmann

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=56A78838.3050400@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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