From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: kernel driver for rs232 serial peripheral
Date: Thu, 25 Aug 2011 23:38:08 +0200 [thread overview]
Message-ID: <4184628.BPS10NrKVa@wuerfel> (raw)
In-Reply-To: <4E56BE79.4030103@drewtech.com>
On Thursday 25 August 2011 17:28:25 Joey Oravec wrote:
> We make a multi-function chip (rtc, gpio, nvram, etc) for embedded
> applications that has an rs232 serial interface. My goal is to write an
> MFD kernel driver that speaks serial to this device and implements
> interfaces. Other busses like spi and i2c are pretty straightforward in
> the kernel but serial feels a lot more complicated. To talk to this
> device from the kernel it seems like I need to:
>
> - Call tty_register_ldisc to create a line discipline
> - Call tty_register_driver and setup a driver
> - Require userspace to call setserial and change the line discipline
>
> This might work, but the documentation implies that a line discipline is
> for a protocol, not for connecting a device driver to a serial port. Is
> there any kind of easier-to-use serial class similar to i2c or spi where
> I can just setup a platform device/driver on a specific serial port? Am
> I missing an easier solution?
I don't think you need to call tty_register_driver, if it's a standard
serial port, it should already work.
Also, I believe that there is a way to set the line discipline from
inside the kernel if you know what is connected. I forgot the details
but there should be a number of examples in the kernel source.
Arnd
prev parent reply other threads:[~2011-08-25 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 21:28 kernel driver for rs232 serial peripheral Joey Oravec
2011-08-25 21:38 ` Arnd Bergmann [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=4184628.BPS10NrKVa@wuerfel \
--to=arnd@arndb.de \
--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).