diff options
| author | Andy Green <[email protected]> | 2010-02-01 13:28:54 +0100 |
|---|---|---|
| committer | Sascha Hauer <[email protected]> | 2010-02-16 17:16:47 +0100 |
| commit | 94d32f99c6aba8b702a9cf78cb328aeb7882b1e5 (patch) | |
| tree | a3544b4959da6e325c11d9cd568b07bdd4c0a94c /lib/memory-notifier-error-inject.c | |
| parent | e335c75cf32b7014f84c90bbe7ed9b7ecd8e7778 (diff) | |
imx-serial-excessive-status-clearing-on-break.patch
cc: Sasha Hauer <[email protected]>
We noticed that we were only able to communicate once with a GSM module
per session, if we powered down the module then the serial driver was
broken until reset, no traffic or /proc/interrupts activity could be
seen any more.
Volker noticed it was provoked by a long "break" seen on the wire when
the RX was not driven during powerdown, we discovered we could kill the
serial driver just by forcing RX low extenally for a little while.
I saw that the processing for BREAK in the driver gets too excited and
clears down all set bits in USR2, including that a character is pending.
This stops all further characters getting processed.
The attached one-liner makes the serial driver immortal against BREAK.
Signed-off-by: Andy Green <[email protected]>
Signed-off-by: Volker Ernst <[email protected]>
Signed-off-by: Sascha Hauer <[email protected]>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions