From: "Kim, Jong-Sung" <neidhard.kim@lge.com>
To: 'Chanho Min' <chanho0207@gmail.com>,
'Russell King' <linux@arm.linux.org.uk>,
'Alan Cox' <alan@linux.intel.com>,
'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>,
'Linus Walleij' <linus.walleij@linaro.org>,
'Shreshtha Kumar Sahu' <shreshthakumar.sahu@stericsson.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: RE: [PATCH] Clear previous interrupts after fifo is disabled
Date: Thu, 8 Mar 2012 18:02:48 +0900 [thread overview]
Message-ID: <00d901ccfd0a$3c268740$b47395c0$@lge.com> (raw)
In-Reply-To: <CAOAMb1ASB0zznSSOAU9HgPNW2e=Do+8hSJ6JZ00DxtAxqsXyXQ@mail.gmail.com>
> -----Original Message-----
> From: Chanho Min [mailto:chanho0207@gmail.com]
> Sent: Monday, February 27, 2012 6:30 PM
> To: Russell King; Alan Cox; Greg Kroah-Hartman; Linus Walleij; Shreshtha
> Kumar Sahu; Kim, Jong-Sung
> Cc: linux-kernel@vger.kernel.org; linux-serial@vger.kernel.org
> Subject: [PATCH] Clear previous interrupts after fifo is disabled
>
> This is another workaroud of 'https://lkml.org/lkml/2012/1/17/104'
> with additional analysis.Bootloader can transfer control to kernel and
there
> are some pending interrupts. In this case, RXFE of the flag register is
set
> by clearing FEN(LCRH) even if rx data remains in the fifo. It seems that
the
> fifo's status is initiailized. Interrupt handler can not get any data from
> data register because of the below break condtion.
>
> pl011_fifo_to_tty
> while (max_count--) {
> if (status & UART01x_FR_RXFE)
> break;
>
> Then, Rx interrupt is never cleared. cpu is looping in ISR. System is
hang.
> If we don't guarantee that no interrupt is pended until fifo is disabled
by
> calling 'writew(0, uap->port.membase + uap->lcrh_rx)', this misbehave of
the
> interrupt handelr can be occurred. So, All pending interrupts should be
> cleared just after fifo is disabled under the protection from interrupt.
> Also,'clear error interrupts' routine can be removed becuase all
interrupts
> are cleared before.
>
> Signed-off-by: Chanho Min <chanho.min@lge.com>
May I suggest another approach at this point? The problematic condition you
reported could be considered as an exceptional Rx interrupt status. So, we
can handle it in the Rx ISR. Simply:
diff --git a/drivers/tty/serial/amba-pl011.c
b/drivers/tty/serial/amba-pl011.c
index 6800f5f..5b5358705 100644
--- a/drivers/tty/serial/amba-pl011.c
+++ b/drivers/tty/serial/amba-pl011.c
@@ -224,6 +224,10 @@ static int pl011_fifo_to_tty(struct uart_amba_port
*uap)
uart_insert_char(&uap->port, ch, UART011_DR_OE, ch, flag);
}
+ /* RXIS but RXFE? Just clear the interrupt */
+ if(unlikely(fifotaken == 0))
+ writew(UART011_RXIS, uap->port.membase + UART01x_ICR);
+
return fifotaken;
}
next prev parent reply other threads:[~2012-03-08 9:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 9:30 [PATCH] Clear previous interrupts after fifo is disabled Chanho Min
2012-02-27 10:45 ` Linus Walleij
2012-02-27 10:48 ` Russell King - ARM Linux
2012-02-27 11:02 ` Russell King - ARM Linux
2012-02-27 13:54 ` Linus Walleij
2012-02-28 1:35 ` Chanho Min
2012-02-28 8:35 ` Russell King - ARM Linux
2012-02-28 9:16 ` Chanho Min
2012-02-28 9:21 ` Russell King - ARM Linux
2012-02-28 9:46 ` Chanho Min
2012-02-28 10:23 ` Russell King - ARM Linux
2012-02-29 2:47 ` Chanho Min
2012-03-08 9:02 ` Kim, Jong-Sung [this message]
2012-03-08 18:49 ` Greg Kroah-Hartman
2012-03-09 16:34 ` Linus Walleij
2012-03-09 16:37 ` Greg Kroah-Hartman
2012-03-10 2:14 ` Chanho Min
2012-03-12 1:24 ` Kim, Jong-Sung
2012-03-12 8:29 ` Linus Walleij
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='00d901ccfd0a$3c268740$b47395c0$@lge.com' \
--to=neidhard.kim@lge.com \
--cc=alan@linux.intel.com \
--cc=chanho0207@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=shreshthakumar.sahu@stericsson.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).