public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Russell King <linux@arm.linux.org.uk>,
	Rob Herring <robh@kernel.org>, Tony Lindgren <tony@atomide.com>,
	Grant Likely <grant.likely@linaro.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Lee Jones <lee.jones@linaro.org>,
	Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH v2] platform_get_irq: Revert to platform_get_resource if of_irq_get fails
Date: Mon, 23 Jun 2014 08:33:12 -0700	[thread overview]
Message-ID: <53A848B8.8060501@roeck-us.net> (raw)
In-Reply-To: <1403045462-24204-1-git-send-email-linux@roeck-us.net>

ping ... any comments ?

Guenter

On 06/17/2014 03:51 PM, Guenter Roeck wrote:
> Commits 9ec36ca (of/irq: do irq resolution in platform_get_irq)
> and ad69674 (of/irq: do irq resolution in platform_get_irq_byname)
> change the semantics of platform_get_irq and platform_get_irq_byname
> to always rely on devicetree information if devicetree is enabled
> and if a devicetree node is attached to the device. The functions
> now return an error if the devicetree data does not include interrupt
> information, even if the information is available as platform resource
> data.
>
> This causes mfd client drivers to fail if the interrupt number is
> passed via platform resources. Therefore, if of_irq_get fails, try
> platform_get_resource as method of last resort. This restores the
> original functionality for drivers depending on platform resources
> to get irq information.
>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Grant Likely <grant.likely@linaro.org>
> Cc: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> v2: Include change for platform_get_irq_byname
>      Handle EPROBE_DEFER
>
> It looks like v1 got lost in space, so you may not have seen it.
> I am sending this patch as v2 anyway to avoid confusion, just in case
> v1 shows up somewhere.
>
> At least 9ec36ca has been applied to -stable, so if this patch is
> accepted it may make sense to apply it to the same -stable releases.
>
>   drivers/base/platform.c | 18 ++++++++++++++----
>   1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/base/platform.c b/drivers/base/platform.c
> index 9e9227e..eee48c4 100644
> --- a/drivers/base/platform.c
> +++ b/drivers/base/platform.c
> @@ -89,8 +89,13 @@ int platform_get_irq(struct platform_device *dev, unsigned int num)
>   	return dev->archdata.irqs[num];
>   #else
>   	struct resource *r;
> -	if (IS_ENABLED(CONFIG_OF_IRQ) && dev->dev.of_node)
> -		return of_irq_get(dev->dev.of_node, num);
> +	if (IS_ENABLED(CONFIG_OF_IRQ) && dev->dev.of_node) {
> +		int ret;
> +
> +		ret = of_irq_get(dev->dev.of_node, num);
> +		if (ret >= 0 || ret == -EPROBE_DEFER)
> +			return ret;
> +	}
>
>   	r = platform_get_resource(dev, IORESOURCE_IRQ, num);
>
> @@ -133,8 +138,13 @@ int platform_get_irq_byname(struct platform_device *dev, const char *name)
>   {
>   	struct resource *r;
>
> -	if (IS_ENABLED(CONFIG_OF_IRQ) && dev->dev.of_node)
> -		return of_irq_get_byname(dev->dev.of_node, name);
> +	if (IS_ENABLED(CONFIG_OF_IRQ) && dev->dev.of_node) {
> +		int ret;
> +
> +		ret = of_irq_get_byname(dev->dev.of_node, name);
> +		if (ret >= 0 || ret == -EPROBE_DEFER)
> +			return ret;
> +	}
>
>   	r = platform_get_resource_byname(dev, IORESOURCE_IRQ, name);
>   	return r ? r->start : -ENXIO;
>


  reply	other threads:[~2014-06-23 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 22:51 [PATCH v2] platform_get_irq: Revert to platform_get_resource if of_irq_get fails Guenter Roeck
2014-06-23 15:33 ` Guenter Roeck [this message]
2014-06-23 15:48 ` Rob Herring
2014-06-23 17:12   ` Guenter Roeck
2014-06-30 16:18   ` Guenter Roeck
2014-06-30 16:22     ` Greg Kroah-Hartman
2014-07-04 19:51       ` Guenter Roeck

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=53A848B8.8060501@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=grygorii.strashko@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=robh@kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=tony@atomide.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