From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ep93xx: properly wait for UART FIFO to be empty
Date: Wed, 12 Dec 2012 11:25:02 +1100 [thread overview]
Message-ID: <50C7CEDE.4030703@gmail.com> (raw)
In-Reply-To: <1836468.ZU3cPkV103@bender>
On 11/12/12 08:21, Florian Fainelli wrote:
> This patch changes the busy-waiting loop around in the decompressor
> putc() function on the UART FIFO register. Without a proper wait, the
> output of the decompressor was corrupted like this:
>
> Uncompressing Linx. done, booting th enl
>
> To highlight the issue more evidently, looping 100 times instead of 1000
> makes the issue appear much faster. This patch takes the approach of
> using an active while loop until the FIFO is empty (not FULL).
> This issue happened to me on Sim.One running at 200Mhz.
>
> Signed-off-by: Florian Fainelli <florian@openwrt.org>
> ---
> Ryan, this is based on your ep93xx-fixes branch, thanks!
Thank you,
Applied to ep93xx-fixes.
~Ryan
>
> arch/arm/mach-ep93xx/include/mach/uncompress.h | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/arch/arm/mach-ep93xx/include/mach/uncompress.h b/arch/arm/mach-ep93xx/include/mach/uncompress.h
> index 16026c2..d64274f 100644
> --- a/arch/arm/mach-ep93xx/include/mach/uncompress.h
> +++ b/arch/arm/mach-ep93xx/include/mach/uncompress.h
> @@ -47,13 +47,9 @@ static void __raw_writel(unsigned int value, unsigned int ptr)
>
> static inline void putc(int c)
> {
> - int i;
> -
> - for (i = 0; i < 1000; i++) {
> - /* Transmit fifo not full? */
> - if (!(__raw_readb(PHYS_UART_FLAG) & UART_FLAG_TXFF))
> - break;
> - }
> + /* Transmit fifo not full? */
> + while (__raw_readb(PHYS_UART_FLAG) & UART_FLAG_TXFF)
> + ;
>
> __raw_writeb(c, PHYS_UART_DATA);
> }
>
prev parent reply other threads:[~2012-12-12 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 21:21 [PATCH] ARM: ep93xx: properly wait for UART FIFO to be empty Florian Fainelli
2012-12-12 0:25 ` Ryan Mallon [this message]
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=50C7CEDE.4030703@gmail.com \
--to=rmallon@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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.