public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [RFC] tty (or char) bus?
Date: Fri, 17 Jul 2009 13:54:28 -0400	[thread overview]
Message-ID: <20090717175428.GB4852@const.linuxsymposium.org> (raw)
In-Reply-To: <4A5CA4CB.8070500@tis.icnet.pl>

Hello,

Janusz Krzysztofik, le Tue 14 Jul 2009 17:31:23 +0200, a écrit :
> In my attempt to add support for contols to a voice modem codec sound 
> device driver, I found that in order to talk to the modem, it would be 
> convenient if I can get access to a tty device from inside the kernel in 
> a way similiar to that available form userspace.

I agree.

> AFAICS, even if tty lowlevel write() could be used unmodified, a
> convenient way of reading characters from a tty is missing and should
> be implemented in a line discipline. Please correct me if I am wrong.

Have you seen the receive_buf line discipline hook?  Indeed it's not a
read() operation as from userland, but at least you can get the data
from the tty that way.

> OTOH, I found that some kind of abstraction layer for acccessing devices 
> over a tty could be convenient. Instead of allocating a new line 
> discipline for each specific device, sometimes found on a specific board 
> only, why not just create a new bus type?

I'd tend to agree with you, as I also have a use case for that: braille
& speech synthesis devices.  However for now I haven't found a really
convincing argument why line disciplines aren't enough.

Samuel

  reply	other threads:[~2009-07-17 17:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 15:31 [RFC] tty (or char) bus? Janusz Krzysztofik
2009-07-17 17:54 ` Samuel Thibault [this message]
2009-07-19 13:19   ` Tilman Schmidt
2009-07-19 13:34     ` Samuel Thibault

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=20090717175428.GB4852@const.linuxsymposium.org \
    --to=samuel.thibault@ens-lyon.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=jkrzyszt@tis.icnet.pl \
    --cc=linux-kernel@vger.kernel.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