devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@linaro.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Rob Herring <rob.herring@calxeda.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] of/platform: add error reporting to of_amba_device_create()
Date: Mon, 09 Sep 2013 17:05:03 +0100	[thread overview]
Message-ID: <20130909160503.6F9C13E0F23@localhost> (raw)
In-Reply-To: <2891140.lVrJfIiCi5@amdc1032>

On Fri, 30 Aug 2013 13:17:29 +0200, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> wrote:
> Add error reporting to of_amba_device_create() so the user knows
> when (and why) some device tree nodes fail to initialize.
> 
> [ The issue was spotted on Universal C210 board (using revision 0 of
>   ARM Exynos4210 SoC) on which initialization was silently failing
>   for PL330 MDMA1 device tree node (it was using the wrong addres
>   resulting in amba_device_add() returning -ENODEV). ]
> 
> Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>

Applied, thanks

g.

> ---
> v2:
> * don't change the return value
> * don't change the user of of_amba_device_create()
> 
>  drivers/of/platform.c |   19 ++++++++++++++++---
>  1 file changed, 16 insertions(+), 3 deletions(-)
> 
> Index: b/drivers/of/platform.c
> ===================================================================
> --- a/drivers/of/platform.c	2013-08-29 17:04:38.227921054 +0200
> +++ b/drivers/of/platform.c	2013-08-30 13:13:31.202813954 +0200
> @@ -268,8 +268,11 @@ static struct amba_device *of_amba_devic
>  		return NULL;
>  
>  	dev = amba_device_alloc(NULL, 0, 0);
> -	if (!dev)
> +	if (!dev) {
> +		pr_err("%s(): amba_device_alloc() failed for %s\n",
> +		       __func__, node->full_name);
>  		return NULL;
> +	}
>  
>  	/* setup generic device info */
>  	dev->dev.coherent_dma_mask = ~0;
> @@ -294,12 +297,18 @@ static struct amba_device *of_amba_devic
>  		dev->irq[i] = irq_of_parse_and_map(node, i);
>  
>  	ret = of_address_to_resource(node, 0, &dev->res);
> -	if (ret)
> +	if (ret) {
> +		pr_err("%s(): of_address_to_resource() failed (%d) for %s\n",
> +		       __func__, ret, node->full_name);
>  		goto err_free;
> +	}
>  
>  	ret = amba_device_add(dev, &iomem_resource);
> -	if (ret)
> +	if (ret) {
> +		pr_err("%s(): amba_device_add() failed (%d) for %s\n",
> +		       __func__, ret, node->full_name);
>  		goto err_free;
> +	}
>  
>  	return dev;
>  
> @@ -378,6 +387,10 @@ static int of_platform_bus_create(struct
>  	}
>  
>  	if (of_device_is_compatible(bus, "arm,primecell")) {
> +		/*
> +		 * Don't return an error here to keep compatibility with older
> +		 * device tree files.
> +		 */
>  		of_amba_device_create(bus, bus_id, platform_data, parent);
>  		return 0;
>  	}
> 

      reply	other threads:[~2013-09-09 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 11:17 [PATCH v2] of/platform: add error reporting to of_amba_device_create() Bartlomiej Zolnierkiewicz
2013-09-09 16:05 ` Grant Likely [this message]

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=20130909160503.6F9C13E0F23@localhost \
    --to=grant.likely@linaro.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.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).