Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0b3d4ef6fe43b75d4b2a6fc4b814cf03aa248e13
Commit:     0b3d4ef6fe43b75d4b2a6fc4b814cf03aa248e13
Parent:     3afb209a43a4216ad4f1411922d47a44252926c6
Author:     Paul Mundt <[EMAIL PROTECTED]>
AuthorDate: Wed Mar 14 13:22:37 2007 +0900
Committer:  Paul Mundt <[EMAIL PROTECTED]>
CommitDate: Wed Mar 14 13:22:37 2007 +0900

    serial: Fix sh-sci break interrupt/sysrq handling.
    
    The sh-sci sci_br_interrupt() handler was failing to call
    in to uart_handle_break(), which was something that only
    the SH-3 path was doing, fix that up.
    
    Additionally, SUPPORT_SYSRQ seems to have moved down too
    far, move it back to the top so uart_handle_break() and
    friends aren't no-ops.
    
    Signed-off-by: Paul Mundt <[EMAIL PROTECTED]>
---
 drivers/serial/sh-sci.c |   11 ++++++-----
 1 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/drivers/serial/sh-sci.c b/drivers/serial/sh-sci.c
index c53b696..46c40bb 100644
--- a/drivers/serial/sh-sci.c
+++ b/drivers/serial/sh-sci.c
@@ -17,6 +17,9 @@
  * License.  See the file "COPYING" in the main directory of this archive
  * for more details.
  */
+#if defined(CONFIG_SERIAL_SH_SCI_CONSOLE) && defined(CONFIG_MAGIC_SYSRQ)
+#define SUPPORT_SYSRQ
+#endif
 
 #undef DEBUG
 
@@ -49,11 +52,6 @@
 #endif
 
 #include <asm/sci.h>
-
-#if defined(CONFIG_SERIAL_SH_SCI_CONSOLE) && defined(CONFIG_MAGIC_SYSRQ)
-#define SUPPORT_SYSRQ
-#endif
-
 #include "sh-sci.h"
 
 struct sci_port {
@@ -645,6 +643,9 @@ static inline int sci_handle_breaks(struct uart_port *port)
        struct tty_struct *tty = port->info->tty;
        struct sci_port *s = &sci_ports[port->line];
 
+       if (uart_handle_break(port))
+               return 0;
+
        if (!s->break_flag && status & SCxSR_BRK(port)) {
 #if defined(CONFIG_CPU_SH3)
                /* Debounce break */
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to