From: Peter Hurley <peter@hurleysoftware.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Beat Bolli <bbolli@ewanet.ch>, linux-serial@vger.kernel.org
Subject: Re: PROBLEM: BUG: scheduling while atomic in the 8250 serial driver
Date: Sat, 01 Feb 2014 12:27:39 -0500 [thread overview]
Message-ID: <52ED2E8B.2050908@hurleysoftware.com> (raw)
In-Reply-To: <20140201150436.GA8992@kroah.com>
On 02/01/2014 10:04 AM, Greg Kroah-Hartman wrote:
> On Sat, Feb 01, 2014 at 09:42:57AM -0500, Peter Hurley wrote:
>> You can't use low_latency; only devices that receive data in
>> non-interrupt contexts (such as USB serial devices) can.
>
> USB serial devices get their data in interrupt context, until we fix USB
> callbacks to be threaded, which might happen one day...
Oh yeah, you're right.
Weird. Back when I was writing the Firewire serial driver,
I experimented with low_latency some but decided it wasn't worth
the hassle. I could swear I was copying from some USB serial
driver...
Regards,
Peter Hurley
prev parent reply other threads:[~2014-02-01 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 12:48 PROBLEM: BUG: scheduling while atomic in the 8250 serial driver Beat Bolli
2014-02-01 14:42 ` Peter Hurley
2014-02-01 15:04 ` Greg Kroah-Hartman
2014-02-01 17:27 ` Peter Hurley [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=52ED2E8B.2050908@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=bbolli@ewanet.ch \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.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).