From: linux@bohmer.net (Remy Bohmer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Updated: Fix soft lockup in at91 udc driver
Date: Tue, 19 Jan 2010 11:46:23 +0100 [thread overview]
Message-ID: <3efb10971001190246t3c47d2afg76ffde05d77ab33d@mail.gmail.com> (raw)
In-Reply-To: <20100119085304.GA17708@pengutronix.de>
Hi,
2010/1/19 Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>:
> Hello,
>
> On Fri, Jan 15, 2010 at 08:50:14AM +1300, Ryan Mallon wrote:
>> Fix a potential soft lockup in the AT91 UDC driver by ensuring that the
>> UDC clock is enabled inside the interrupt handler. If the UDC clock is
>> not enabled then the UDC registers cannot be written to and the
>> interrupt cannot be cleared or masked.
> Wouldn't it be cleaner to assert that the clock is already on when an
> irq comes in? ?That is enable the clock and let it enabled when
> configuring the device to generate irqs?
>
> Just my 2?
What we have seen here is that there is a condition during host-suspend.
When the host-suspends (3ms idle) the clocks are being disabled, after
a short time the host wakes up again and does a device reset.
This reset triggers a resume interrupt with the clocks disabled. BUT,
it only behaves like this with only a few host controllers. This
results in a hanging interrupt.
The locking code of this driver is not completely clean and that needs
some rework, especially for preempt-rt.
We want to rework this, but that takes more time. Until then this
patch at least solves the issue and can be used safely.
Kind regards,
Remy
prev parent reply other threads:[~2010-01-19 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 19:50 [PATCH] Updated: Fix soft lockup in at91 udc driver Ryan Mallon
2010-01-18 20:40 ` Ryan Mallon
2010-01-19 8:53 ` Uwe Kleine-König
2010-01-19 10:46 ` Remy Bohmer [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=3efb10971001190246t3c47d2afg76ffde05d77ab33d@mail.gmail.com \
--to=linux@bohmer.net \
--cc=linux-arm-kernel@lists.infradead.org \
/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).