summaryrefslogtreecommitdiffstats
path: root/drivers/tty/serial/8250/8250_pxa.c
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2016-10-24 17:00:30 +0900
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-11-10 14:30:09 +0100
commitda7fa058a36cd8d4ebd42001fa72a40c0aefd6e3 (patch)
tree614752aebce84ab25854f5c87042a1caa79b586d /drivers/tty/serial/8250/8250_pxa.c
parent94cbb6978b63d004502eed24417aceb7b36bc10a (diff)
downloadlinux-stable-da7fa058a36cd8d4ebd42001fa72a40c0aefd6e3.tar.gz
linux-stable-da7fa058a36cd8d4ebd42001fa72a40c0aefd6e3.tar.bz2
linux-stable-da7fa058a36cd8d4ebd42001fa72a40c0aefd6e3.zip
serial: 8250_uniphier: avoid locking for FCR register write
The hardware book says, the FCR is combined with a register called CHAR (it will trigger interrupt when a specific character is received). At first, I used lock/read/modify/write/unlock dance for the FCR to not affect the upper bits, but the CHAR is actually never used. It should not hurt to always clear the CHAR and to handle the FCR as a normal case. It can save the costly locking. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Suggested-by: Denys Vlasenko <dvlasenk@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/tty/serial/8250/8250_pxa.c')
0 files changed, 0 insertions, 0 deletions