From: "David McIlwraith" <quack@bigpond.net.au>
To: "Martin Diehl" <lists@mdiehl.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: calling context when writing to tty_driver
Date: Tue, 1 Oct 2002 21:32:56 +1000 [thread overview]
Message-ID: <090e01c2693e$4a32fea0$41368490@archaic> (raw)
In-Reply-To: Pine.LNX.4.21.0210011324110.485-100000@notebook.diehl.home
Spinlocks *could* be used in place, if this is the case. Having not examined
the code, I don't know the implementation specifics.
----- Original Message -----
From: "Martin Diehl" <lists@mdiehl.de>
To: "David McIlwraith" <quack@bigpond.net.au>
Cc: "Martin Diehl" <lists@mdiehl.de>; <linux-kernel@vger.kernel.org>
Sent: Tuesday, October 01, 2002 9:28 PM
Subject: Re: calling context when writing to tty_driver
> On Tue, 1 Oct 2002, David McIlwraith wrote:
>
> > Semaphores may sleep - therefore, they cannot be used from a 'non-sleep'
> > context.
>
> Yes, sure. Sorry if I wasn't clear enough - the point is whether those
> tty_driver write/write_room() calls are allowed to sleep or not. If yes,
> the usbserial implementation is right and it is impossible to do further
> writing directly from write_wakeup() callback (which would be really bad
> IMHO) - if not, usbserial needs to avoid the down() somehow.
>
> Martin
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-10-01 11:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 10:37 calling context when writing to tty_driver Martin Diehl
2002-10-01 11:13 ` David McIlwraith
2002-10-01 11:28 ` Martin Diehl
2002-10-01 11:32 ` David McIlwraith [this message]
2002-10-01 18:34 ` Greg KH
2002-10-01 19:30 ` Russell King
2002-10-01 21:10 ` Martin Diehl
2002-10-03 6:52 ` Greg KH
2002-10-03 9:51 ` Paul Mackerras
2002-10-03 21:36 ` Martin Diehl
2002-10-01 23:20 ` Paul Mackerras
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='090e01c2693e$4a32fea0$41368490@archaic' \
--to=quack@bigpond.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mdiehl.de \
/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.