From: simon.kagstrom@netinsight.net (Simon Kagstrom)
To: linux-arm-kernel@lists.infradead.org
Subject: 21285 serial driver deadlock(?) fix
Date: Mon, 4 Jan 2010 09:11:56 +0100 [thread overview]
Message-ID: <20100104091156.0f384dec@marrow.netinsight.se> (raw)
In-Reply-To: <1262039226.28196.125.camel@localhost>
On Mon, 28 Dec 2009 17:27:06 -0500
Steve Moskovchenko <stevenm86@gmail.com> wrote:
> I've got a board with a StrongARM SA-110 and a 21285 "footbrtidge" on
> it. The kernel's 21285 serial driver works for kernel messages but not
> for I/O from userspace.
>
> My kernel experience is pretty limited, but I believe the problem lies
> in drivers/serial/21285.c.
>
> As I understand it:
> serial21285_tx_chars looks like an ISR, which likes to call
> serial21285_stop_tx every once in a while.
> serial21285_stop_tx, in turn, calls disable_irq(), which waits for the
> current instance of the ISR to finish before disabling that interrupt.
> But, calling this from within an ISR results in deadlock and makes the
> puppy very sad.
>
> I've modified the ISR to call a different version of stop_tx, which uses
> disable_irq_nosync() instead. This gave me a working console.
I sent a similar patch some weeks ago:
http://www.spinics.net/lists/arm-kernel/msg77006.html
which fixes the same problem for me. It would be good to get at least
one of these in I think. My patch also uses _nosync for stop_rx.
// Simon
next prev parent reply other threads:[~2010-01-04 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 22:27 21285 serial driver deadlock(?) fix Steve Moskovchenko
2010-01-01 20:29 ` Russell King - ARM Linux
2010-01-04 8:11 ` Simon Kagstrom [this message]
[not found] ` <20dd1d411001051037o74fb1187j608889fae0271547@mail.gmail.com>
2010-01-11 9:57 ` Simon Kagstrom
2010-01-12 17:12 ` Steve M
2010-01-13 8:17 ` Simon Kagstrom
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=20100104091156.0f384dec@marrow.netinsight.se \
--to=simon.kagstrom@netinsight.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 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.