From: Felipe Balbi <balbi@ti.com>
To: Robert Baldyga <r.baldyga@samsung.com>
Cc: <paulz@synopsys.com>, <balbi@ti.com>,
<gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dinguyen@opensource.altera.com>,
<yousaf.kaukab@intel.com>, <m.szyprowski@samsung.com>
Subject: Re: [PATCH v2] usb: dwc2: call dwc2_is_controller_alive() under spinlock
Date: Wed, 14 Jan 2015 13:37:54 -0600 [thread overview]
Message-ID: <20150114193754.GQ16533@saruman> (raw)
In-Reply-To: <1421217931-23722-1-git-send-email-r.baldyga@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
On Wed, Jan 14, 2015 at 07:45:31AM +0100, Robert Baldyga wrote:
> This patch fixes bug described here:
> https://lkml.org/lkml/2014/12/22/185
>
> Signed-off-by: Robert Baldyga <r.baldyga@samsung.com>
> ---
>
> Changelog:
>
> v2:
> - fixed comment from Paul Zimmerman
>
> v1: https://lkml.org/lkml/2015/1/13/186
>
> drivers/usb/dwc2/core_intr.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/dwc2/core_intr.c b/drivers/usb/dwc2/core_intr.c
> index ad43c5b..02e3e2d 100644
> --- a/drivers/usb/dwc2/core_intr.c
> +++ b/drivers/usb/dwc2/core_intr.c
> @@ -476,13 +476,13 @@ irqreturn_t dwc2_handle_common_intr(int irq, void *dev)
> u32 gintsts;
> irqreturn_t retval = IRQ_NONE;
>
> + spin_lock(&hsotg->lock);
> +
> if (!dwc2_is_controller_alive(hsotg)) {
This is really, really odd. Register accesses are atomic, so the lock
isn't really doing anything. Besides, you're calling
dwc2_is_controller_alive() from within the IRQ handler, so IRQs are
already disabled.
When the problem happens, do you see this "Controller is dead" message ?
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-14 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 6:45 [PATCH v2] usb: dwc2: call dwc2_is_controller_alive() under spinlock Robert Baldyga
2015-01-14 19:03 ` Paul Zimmerman
2015-01-14 19:37 ` Felipe Balbi [this message]
2015-01-14 20:06 ` Alan Stern
2015-01-14 21:14 ` Felipe Balbi
2015-01-14 21:41 ` Alan Stern
2015-01-14 21:46 ` Felipe Balbi
2015-01-14 22:28 ` Paul Zimmerman
2015-01-14 22:39 ` Felipe Balbi
2015-01-14 22:40 ` Felipe Balbi
2015-01-14 22:45 ` Paul Zimmerman
2015-01-14 22:49 ` Felipe Balbi
2015-01-14 23:04 ` Paul Zimmerman
2015-01-15 6:24 ` Felipe Balbi
2015-01-15 10:23 ` Robert Baldyga
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=20150114193754.GQ16533@saruman \
--to=balbi@ti.com \
--cc=dinguyen@opensource.altera.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=paulz@synopsys.com \
--cc=r.baldyga@samsung.com \
--cc=yousaf.kaukab@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.