Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Vignesh R <vigneshr@ti.com>, Felipe Balbi <balbi@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
	Carlos Hernandez <ceh@ti.com>
Subject: Re: [PATCH] usb: dwc3: omap: remove IRQ_NOAUTOEN used with shared irq
Date: Fri, 7 Jul 2017 16:32:34 -0500	[thread overview]
Message-ID: <c397e4ca-638f-2a8d-8800-46314a5c5da1@ti.com> (raw)
In-Reply-To: <20170707062252.10086-1-vigneshr@ti.com>



On 07/07/2017 01:22 AM, Vignesh R wrote:
> IRQ_NOAUTOEN cannot be used with shared IRQs, since commit 04c848d39879
> ("genirq: Warn when IRQ_NOAUTOEN is used with shared interrupts") and
> kernel now throws a warn dump. But OMAP DWC3 driver uses this flag. As
> per commit 12a7f17fac5b ("usb: dwc3: omap: fix race of pm runtime with
> irq handler in probe") that introduced this flag, PM runtime can race
> with IRQ handler when deferred probing happens due to extcon,
> therefore IRQ_NOAUTOEN needs to be set so that irq is not enabled until
> extcon is registered.
> 
> Remove setting of IRQ_NOAUTOEN and move the registration of
> shared irq to a point after dwc3_omap_extcon_register() and
> of_platform_populate(). This avoids possibility of probe deferring and
> above said race condition.
> 
> Signed-off-by: Vignesh R <vigneshr@ti.com>


Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>

> ---
>   drivers/usb/dwc3/dwc3-omap.c | 18 ++++++++----------
>   1 file changed, 8 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/usb/dwc3/dwc3-omap.c b/drivers/usb/dwc3/dwc3-omap.c
> index 98926504b55b..f5aaa0cf3873 100644
> --- a/drivers/usb/dwc3/dwc3-omap.c
> +++ b/drivers/usb/dwc3/dwc3-omap.c
> @@ -512,15 +512,6 @@ static int dwc3_omap_probe(struct platform_device *pdev)
>   
>   	/* check the DMA Status */
>   	reg = dwc3_omap_readl(omap->base, USBOTGSS_SYSCONFIG);
> -	irq_set_status_flags(omap->irq, IRQ_NOAUTOEN);
> -	ret = devm_request_threaded_irq(dev, omap->irq, dwc3_omap_interrupt,
> -					dwc3_omap_interrupt_thread, IRQF_SHARED,
> -					"dwc3-omap", omap);
> -	if (ret) {
> -		dev_err(dev, "failed to request IRQ #%d --> %d\n",
> -				omap->irq, ret);
> -		goto err1;
> -	}
>   
>   	ret = dwc3_omap_extcon_register(omap);
>   	if (ret < 0)
> @@ -532,8 +523,15 @@ static int dwc3_omap_probe(struct platform_device *pdev)
>   		goto err1;
>   	}
>   
> +	ret = devm_request_threaded_irq(dev, omap->irq, dwc3_omap_interrupt,
> +					dwc3_omap_interrupt_thread, IRQF_SHARED,
> +					"dwc3-omap", omap);
> +	if (ret) {
> +		dev_err(dev, "failed to request IRQ #%d --> %d\n",
> +			omap->irq, ret);
> +		goto err1;
> +	}
>   	dwc3_omap_enable_irqs(omap);
> -	enable_irq(omap->irq);
>   	return 0;
>   
>   err1:
> 

-- 
regards,
-grygorii

      reply	other threads:[~2017-07-07 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07  6:22 [PATCH] usb: dwc3: omap: remove IRQ_NOAUTOEN used with shared irq Vignesh R
2017-07-07 21:32 ` Grygorii Strashko [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=c397e4ca-638f-2a8d-8800-46314a5c5da1@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc=balbi@kernel.org \
    --cc=ceh@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=vigneshr@ti.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