From: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
To: linux-sh@vger.kernel.org, linux-serial@vger.kernel.org
Cc: horms@verge.net.au, magnus.damm@gmail.com,
Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Subject: [RFC 0/3] serial: sh-sci: SCIF FIFO exploitation
Date: Fri, 12 Sep 2014 08:51:45 +0000 [thread overview]
Message-ID: <1410511908-9282-1-git-send-email-ulrich.hecht+renesas@gmail.com> (raw)
Hi!
The current sh-sci implementation doesn't exploit the RX FIFOs at all and
has the chip issue an interrupt for every byte received. This series
implements the necessary changes to improve that.
It includes a sysfs interface for changing the FIFO trigger level; there
seem to be few drivers that implement something like that (I only found
one), so I'd like to know if this implementation is palatable.
CU
Uli
Ulrich Hecht (3):
serial: sh-sci: consider DR (data ready) bit adequately
serial: sh-sci: exploit RX FIFOs better
serial: sh-sci: make RX FIFO trigger tunable via sysfs
drivers/tty/serial/sh-sci.c | 113 ++++++++++++++++++++++++++++++++++++++++++--
drivers/tty/serial/sh-sci.h | 5 ++
include/linux/serial_sci.h | 2 +
3 files changed, 116 insertions(+), 4 deletions(-)
--
1.8.4.5
next reply other threads:[~2014-09-12 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 8:51 Ulrich Hecht [this message]
2014-09-12 8:51 ` [RFC 1/3] serial: sh-sci: consider DR (data ready) bit adequately Ulrich Hecht
2014-09-12 8:51 ` [RFC 2/3] serial: sh-sci: exploit RX FIFOs better Ulrich Hecht
2014-09-12 8:51 ` [RFC 3/3] serial: sh-sci: make RX FIFO trigger tunable via sysfs Ulrich Hecht
2014-09-17 16:49 ` [RFC 0/3] serial: sh-sci: SCIF FIFO exploitation Peter Hurley
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=1410511908-9282-1-git-send-email-ulrich.hecht+renesas@gmail.com \
--to=ulrich.hecht+renesas@gmail.com \
--cc=horms@verge.net.au \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@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 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).