From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Ivan Kuten <ivan.kuten@promwad.com>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>,
Andrew Victor <andrew@sanpeople.com>,
Nicolas Ferre <nicolas.ferre@rfo.atmel.com>,
Patrice Vilchez <patrice.vilchez@rfo.atmel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] atmel_serial: Fix break handling
Date: Mon, 18 Jun 2007 11:33:54 +0100 [thread overview]
Message-ID: <20070618103353.GB10387@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070618132121.2d00a907@newbox>
On Mon, Jun 18, 2007 at 01:21:21PM +0300, Ivan Kuten wrote:
> Hi Haavard,
>
> I tried /dev/ttyAT3, break appeared but not the way I expected, after:
> stty -F /dev/ttyAT3 brkint I get:
>
> cat /proc/tty/driver/atmel_serial
> serinfo:1.0 driver revision:
> 0: uart:ATMEL_SERIAL mmio:0xFEFFF200 irq:1 tx:0 rx:0 CTS|DSR|CD|RI
> 1: uart:ATMEL_SERIAL mmio:0xFFFC0000 irq:6 tx:0 rx:0 CTS|DSR|CD|RI
> 2: uart:ATMEL_SERIAL mmio:0xFFFC4000 irq:7 tx:0 rx:0 RI
> 3: uart:ATMEL_SERIAL mmio:0xFFFC8000 irq:8 tx:1530 rx:115 brk:1 RTS|DTR|DSR|CD|RI
> 4: uart:ATMEL_SERIAL mmio:0xFFFCC000 irq:9 tx:0 rx:0 DSR|CD|RI
>
> brk is 1 not depending on how many breaks was sent. May be I missunderstood
> "break" meaning?
> I use from minicom: Main Functions : send break.........F .
Note that if you want to use magic sysrq on ttyAT3, you need the kernel
console on ttyAT3. Since you successfully received one break event on
ttyAT3, the next character should have caused a sysrq event.
> I inserted printk:
>
> /*
> * Control the transmission of a break signal
^^^^^^^^^^^^
So if you're looking at the reception paths, this clearly isn't it...
> */
> static void atmel_break_ctl(struct uart_port *port, int break_state)
> {
> printk(KERN_EMERG "atmel_break_ctl break_state %d", break_state);
> if (break_state != 0)
> UART_PUT_CR(port, ATMEL_US_STTBRK); /* start break */
> else
> UART_PUT_CR(port, ATMEL_US_STPBRK); /* stop break */
> }
>
> it's also not shown.
... and that explains why.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-06-18 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 19:31 Haavard Skinnemoen
2007-06-05 11:07 ` Ivan Kuten
2007-06-05 11:23 ` Haavard Skinnemoen
2007-06-18 10:21 ` Ivan Kuten
2007-06-18 10:33 ` Russell King [this message]
2007-06-19 10:36 ` Ivan Kuten
2007-06-19 16:58 ` Russell King
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=20070618103353.GB10387@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=andrew@sanpeople.com \
--cc=hskinnemoen@atmel.com \
--cc=ivan.kuten@promwad.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@rfo.atmel.com \
--cc=patrice.vilchez@rfo.atmel.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
all inboxes | Powered by JetHome®