From: Greg KH <gregkh@linuxfoundation.org>
To: Ivo Sieben <meltedpianoman@gmail.com>
Cc: linux-serial@vger.kernel.org, Alan Cox <alan@linux.intel.com>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: Deterministic behavior for TTY serial
Date: Wed, 18 Apr 2012 17:14:07 -0700 [thread overview]
Message-ID: <20120419001407.GA24710@kroah.com> (raw)
In-Reply-To: <CAMSQXEENByqSmK2bSxMngY2WuV86AAcX_LxTbA5JSOjT3ta_FA@mail.gmail.com>
On Tue, Apr 17, 2012 at 04:38:30PM +0200, Ivo Sieben wrote:
> Hello,
>
> We are currently using the TTY framework for serial communication.
>
> We are wondering if it is possible to give the TTY device in more
> deterministic behavior (as in "less locks & no sleeping")
What specifically are you looking for?
> So in case of non blocking read/write behavior:
> - We want directly write data to the serial_core transmit buffer and
> return immediately.
What is "immediately"?
> - Incoming data should be buffered, on a read data is read directly
> from that buffer and when no data available return immediately
That doesn't happen today?
What type of latencies are you seeing today that is bothering you? What
hardware are you expecting to work in this manner? What exact UART are
you using? What happens when the UART buffers data?
thanks,
greg k-h
next prev parent reply other threads:[~2012-04-19 0:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 14:38 Deterministic behavior for TTY serial Ivo Sieben
2012-04-19 0:14 ` Greg KH [this message]
2012-04-19 15:37 ` Ivo Sieben
2012-04-19 15:46 ` Greg KH
2012-04-26 14:27 ` Ivo Sieben
2012-05-01 14:30 ` Ivo Sieben
2012-05-01 15:04 ` Alan Cox
[not found] ` <CAMSQXEHAyPOF6YghsYmqqyx+N0oMgn5E=znhgFyspMUnaH78ig@mail.gmail.com>
2012-05-02 8:38 ` Ivo Sieben
2012-05-02 12:39 ` Ivo Sieben
2012-05-03 15:28 ` Ivo Sieben
2012-05-05 0:32 ` Greg KH
2012-04-19 11:19 ` Alan Cox
2012-04-19 15:42 ` Ivo Sieben
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=20120419001407.GA24710@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=meltedpianoman@gmail.com \
/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.