aboutsummaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorJiri Slaby <jirislaby@gmail.com>2011-06-05 22:51:49 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-01-27 20:46:29 -0800
commitc9d332c77f72e7d9643116e53ae0c1e2bebd3156 (patch)
tree80ef347e3003b9e3754d8c189241397260fcbd21 /arch
parenta6aa749906b92eaec6ca0469f90f35de26044d90 (diff)
downloadkernel_samsung_smdk4412-c9d332c77f72e7d9643116e53ae0c1e2bebd3156.zip
kernel_samsung_smdk4412-c9d332c77f72e7d9643116e53ae0c1e2bebd3156.tar.gz
kernel_samsung_smdk4412-c9d332c77f72e7d9643116e53ae0c1e2bebd3156.tar.bz2
serial: 8250, increase PASS_LIMIT
commit e7328ae1848966181a7ac47e8ae6cddbd2cf55f3 upstream. With virtual machines like qemu, it's pretty common to see "too much work for irq4" messages nowadays. This happens when a bunch of output is printed on the emulated serial console. This is caused by too low PASS_LIMIT. When ISR loops more than the limit, it spits the message. I've been using a kernel with doubled the limit and I couldn't see no problems. Maybe it's time to get rid of the message now? Signed-off-by: Jiri Slaby <jirislaby@gmail.com> Cc: Alan Cox <alan@linux.intel.com> Cc: Ram Gupta <ram.gupta5@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions