From: Phil Sutter <n0-1@freewrt.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Dmitry Torokhov <dtor@mail.ru>,
linux-input@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, Florian Fainelli <florian@openwrt.org>
Subject: Re: [PATCH 2/2] input: add driver for S1 button of rb532
Date: Sat, 24 Jan 2009 15:20:27 +0100 [thread overview]
Message-ID: <20090124141705.96C694CEAE@mail.nwl.cc> (raw)
In-Reply-To: <Pine.LNX.4.64.0901240934040.13803@anakin>
Hi,
On Sat, Jan 24, 2009 at 09:34:43AM +0100, Geert Uytterhoeven wrote:
> What happens when you receive UART input while the UART is disabled? Is it
> lost?
Yes, the input is lost, as well as any output sent by the device while
UART0 is disabled. I've tested this adding a msleep() of 5s in between
the calls to set_latch_u5() and increasing the delay between polls to
10s.
I've tried to reproduce this behaviour without the changes from above
using a loop flooding the output of the serial console with increasing
numbers, with somehow strange results. Instead of missing some output,
occasionally the log shows additional characters (some non-printable).
Also (seldomly) digits are replaced by other chars (also not necesarily
printable).
So I can at least assume the two drivers interfere with each other,
which could lead to bad results when using the UART for more advanced
stuff. Although it may be possible to introduce some kind of locking for
the serial output, I doubt this can be done with the input part, as the
device is turned off while polling so data shouldn't even reach the device.
Any ideas?
Greetings, Phil
prev parent reply other threads:[~2009-01-24 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1232651528-19870-1-git-send-email-n0-1@freewrt.org>
2009-01-22 19:12 ` [PATCH 1/2] MIPS: rb532: prepare board support for rb532-button Phil Sutter
[not found] ` <1232651528-19870-2-git-send-email-n0-1@freewrt.org>
2009-01-22 19:12 ` [PATCH 2/2] input: add driver for S1 button of rb532 Phil Sutter
2009-01-24 8:34 ` Geert Uytterhoeven
2009-01-24 14:20 ` Phil Sutter [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=20090124141705.96C694CEAE@mail.nwl.cc \
--to=n0-1@freewrt.org \
--cc=dtor@mail.ru \
--cc=florian@openwrt.org \
--cc=geert@linux-m68k.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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).