From: Stefan Schoenleitner <dev.c0debabe@gmail.com>
To: linux-embedded@vger.kernel.org
Subject: Re: Using UART in kernel driver code on AT91SAM9260
Date: Wed, 24 Jun 2009 11:59:41 +0200 [thread overview]
Message-ID: <4A41F90D.6040103@gmail.com> (raw)
In-Reply-To: <8763em3qsp.fsf@macbook.be.48ers.dk>
Hi,
Peter Korsgaard wrote:
> The input layer has serio infrastructure for this (E.G. for serial
> mice/touchscreens). Now, a speech codec doesn't have much to do with
> input devices, but it atleast clearly seperates the lowlevel uart
> communication from the speech codec handling.
>
> Have a look in drivers/input/{serio,touchscreen}.
thanks for the tip !
I'm looking to find some more serio documentation now.
If it won't work out, I guess I still have the possibility to write a
line discipline.
However, using serio seems to be more comfortable (also from a useeland
perspective).
cheers,
stefan
next prev parent reply other threads:[~2009-06-24 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 8:57 Using UART in kernel driver code on AT91SAM9260 Stefan Schoenleitner
2009-06-24 9:49 ` Peter Korsgaard
2009-06-24 9:59 ` Stefan Schoenleitner [this message]
2009-06-24 9:49 ` Stefan Schoenleitner
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=4A41F90D.6040103@gmail.com \
--to=dev.c0debabe@gmail.com \
--cc=linux-embedded@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).