From: John Youn <John.Youn@synopsys.com>
To: Romain Perier <romain.perier@gmail.com>,
"John.Youn@synopsys.com" <John.Youn@synopsys.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH v2] usb: dwc2: Register interrupt handler only once gadget is correctly initialized
Date: Thu, 12 Feb 2015 18:47:21 -0800 [thread overview]
Message-ID: <54DD65B9.8060806@synopsys.com> (raw)
In-Reply-To: <CABgxDoKT7zYkk2bMfMOmKJHoTSXEDcaP7E1w5huBh+U5cVAmtA@mail.gmail.com>
On 2/12/2015 4:42 AM, Romain Perier wrote:
> ping
>
> 2015-02-06 17:50 GMT+01:00 Romain Perier <romain.perier@gmail.com>:
>> Don't register interrupt handler before usb gadget is correctly initialized.
>> For some embedded platforms which don't have a usb-phy, it crashes the driver
>> because an interrupt is emitted with non-initialized hardware.
>> According to devm_request_irq documentation, an interrupt can be emitted
>> at any time once the interrupt is registered, so we have to care about driver
>> and hardware initialization.
>>
>> Signed-off-by: Romain Perier <romain.perier@gmail.com>
>> ---
>>
>> Changes for v2: fix typos in commit log
>>
>> drivers/usb/dwc2/platform.c | 17 +++++++++--------
>> 1 file changed, 9 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/usb/dwc2/platform.c b/drivers/usb/dwc2/platform.c
>> index ae095f0..b26cf8c 100644
>> --- a/drivers/usb/dwc2/platform.c
>> +++ b/drivers/usb/dwc2/platform.c
>> @@ -196,14 +196,6 @@ static int dwc2_driver_probe(struct platform_device *dev)
>> return irq;
>> }
>>
>> - dev_dbg(hsotg->dev, "registering common handler for irq%d\n",
>> - irq);
>> - retval = devm_request_irq(hsotg->dev, irq,
>> - dwc2_handle_common_intr, IRQF_SHARED,
>> - dev_name(hsotg->dev), hsotg);
>> - if (retval)
>> - return retval;
>> -
>> res = platform_get_resource(dev, IORESOURCE_MEM, 0);
>> hsotg->regs = devm_ioremap_resource(&dev->dev, res);
>> if (IS_ERR(hsotg->regs))
>> @@ -237,6 +229,15 @@ static int dwc2_driver_probe(struct platform_device *dev)
>> retval = dwc2_gadget_init(hsotg, irq);
>> if (retval)
>> return retval;
>> +
>> + dev_dbg(hsotg->dev, "registering common handler for irq%d\n",
>> + irq);
>> + retval = devm_request_irq(hsotg->dev, irq,
>> + dwc2_handle_common_intr, IRQF_SHARED,
>> + dev_name(hsotg->dev), hsotg);
>> + if (retval)
>> + return retval;
>> +
>> retval = dwc2_hcd_init(hsotg, irq, params);
>> if (retval)
>> return retval;
Hi,
I'm going to be away until Wednesday, Feb 18. I'll take a look at
this and other pending dwc2 patches at that time.
Regards,
John
next prev parent reply other threads:[~2015-02-13 2:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 16:50 [PATCH v2] usb: dwc2: Register interrupt handler only once gadget is correctly initialized Romain Perier
2015-02-12 12:42 ` Romain Perier
2015-02-13 2:47 ` John Youn [this message]
2015-02-13 6:50 ` Romain Perier
2015-02-21 1:45 ` John Youn
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=54DD65B9.8060806@synopsys.com \
--to=john.youn@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=romain.perier@gmail.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