From: "René Bürgel" <r.buergel@unicontrol.de>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH] mpc52xx_uart: report serial errors to users
Date: Thu, 30 Oct 2008 07:14:07 +0100 [thread overview]
Message-ID: <490950AF.1000303@unicontrol.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
Hi! This patch adds the capability to the mpc52xx-uart to report framing
errors, parity errors, breaks and overruns to userspace. These values
may be requested in userspace by using the ioctl TIOCGICOUNT.
Signed-off-by: René Bürgel <r.buergel@unicontrol.de>
Kind regards, René Bürgel
--
René Bürgel
Software Engineer
Unicontrol Systemtechnik GmbH
OT Dittersbach
Sachsenburger Weg 34
09669 Frankenberg
Tel.: 03 72 06/ 88 73 - 19
Fax: 03 72 06/ 88 73 - 60
E-Mail: r.buergel@unicontrol.de
Internet: www.unicontrol.de
[-- Attachment #2: 121-mpc52xx_serial_icounter.patch --]
[-- Type: text/plain, Size: 735 bytes --]
--- drivers/serial/mpc52xx_uart.c 2008-08-07 15:55:43.000000000 +0200
+++ drivers/serial/mpc52xx_uart_orig.c 2008-09-11 13:19:12.000000000 +0200
@@ -752,10 +752,17 @@
if (status & MPC52xx_PSC_SR_RB) {
flag = TTY_BREAK;
uart_handle_break(port);
+ port->icount.brk++;
} else if (status & MPC52xx_PSC_SR_PE)
+ {
flag = TTY_PARITY;
+ port->icount.parity++;
+ }
else if (status & MPC52xx_PSC_SR_FE)
+ {
flag = TTY_FRAME;
+ port->icount.frame++;
+ }
/* Clear error condition */
out_8(&PSC(port)->command, MPC52xx_PSC_RST_ERR_STAT);
@@ -769,6 +776,7 @@
* affect the current character
*/
tty_insert_flip_char(tty, 0, TTY_OVERRUN);
+ port->icount.overrun++;
}
}
next reply other threads:[~2008-10-30 6:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 6:14 René Bürgel [this message]
2008-10-30 15:19 ` [PATCH] mpc52xx_uart: report serial errors to users Grant Likely
2008-11-03 9:35 ` [PATCH] mpc52xx_uart: report serial errors to users v2 René Bürgel
-- strict thread matches above, loose matches on Subject: below --
2008-10-29 17:22 [PATCH] mpc52xx_uart: report serial errors to users René Bürgel
2008-10-29 18:35 ` Grant Likely
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=490950AF.1000303@unicontrol.de \
--to=r.buergel@unicontrol.de \
--cc=linuxppc-dev@ozlabs.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).