From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, ralf@linux-mips.org
Subject: Re: [PATCH] serial: serial_txx9 driver update
Date: Mon, 23 Jan 2006 09:57:00 +0000 [thread overview]
Message-ID: <20060123095700.GB4104@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060123.150502.89066381.nemoto@toshiba-tops.co.jp>
On Mon, Jan 23, 2006 at 03:05:02PM +0900, Atsushi Nemoto wrote:
> - if (disr & TXX9_SIDISR_UOER)
> + if (disr & TXX9_SIDISR_UOER) {
> up->port.icount.overrun++;
> + /*
> + * The receiver read buffer still hold
> + * a char which caused overrun.
> + * Ignore next char by adding RFDN_MASK
> + * to ignore_status_mask temporarily.
> + */
> + next_ignore_status_mask |=
> + TXX9_SIDISR_RFDN_MASK;
> + }
I'm not sure what you mean here.
If we successfully received the string ABCDEFGH, and the next character
to be received (I) causes an overrun condition, what happens in the
case that overruns are not ignored?
Will you read ABCDEFG without any errors from the UART, and then H with
an overrun error? If so, you should pass to the TTY layer ABCDEFGH and
then a NUL character with TTY_OVERRUN set. Note that uart_insert_char()
does this for you.
Alternatively, the UART may give you: ABCDEFGI where I is marked as an
overrun error. In this case, you want to pass to the TTY layer ABCDEFG,
then a NUL character with TTY_OVERRUN set, then I.
If overruns are ignored, you merely omit to insert the NUL character with
TTY_OVERRUN set.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-01-23 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 17:19 [PATCH] serial: serial_txx9 driver update Atsushi Nemoto
2006-01-22 7:36 ` Andrew Morton
2006-01-22 8:00 ` Russell King
2006-01-22 8:33 ` Andrew Morton
2006-01-22 23:02 ` Russell King
2006-01-23 6:05 ` Atsushi Nemoto
2006-01-23 9:57 ` Russell King [this message]
2006-01-23 13:39 ` Atsushi Nemoto
2006-01-23 13:42 ` Atsushi Nemoto
2006-01-23 19:49 ` Russell King
2006-01-24 2:24 ` Atsushi Nemoto
-- strict thread matches above, loose matches on Subject: below --
2006-12-21 17:01 Atsushi Nemoto
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=20060123095700.GB4104@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.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 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.