summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBodo Eggert <7eggert@gmx.de>2019-12-26 22:28:45 +0100
committerMauro Carvalho Chehab <mchehab+huawei@kernel.org>2020-01-03 16:29:33 +0100
commita04930b7bf5986f3e1291d77c452cbed2aa2b3e4 (patch)
tree3dd4c901c2611c2acfbd37cb2a35fb24f6cb0355
parent31f715dd48de0acb3f57f7a83e1679c9dc50179d (diff)
downloadlinux-a04930b7bf5986f3e1291d77c452cbed2aa2b3e4.tar.bz2
media: serial_ir: change "ignoring spike" to debug level
At least on my system with a self-made IR receiver, my kernel log is filled with: serial_ir serial_ir.0: ignoring spike: 1 1 1419988034627194ns 1419956080709377ns These messages happen at random and do not prevent the receiver from working. Also I cannot change the features of the IC, therefore they are not useful. Probably they are not useful at all. However they fill the console, they accumulate and fill the dmesg log, by doing this, they prevent me from seeing important message. Signed-off-by: Bodo Eggert <7eggert@gmx.de> Signed-off-by: Sean Young <sean@mess.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
-rw-r--r--drivers/media/rc/serial_ir.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/media/rc/serial_ir.c b/drivers/media/rc/serial_ir.c
index 7652e982173f..d77507ba0fb5 100644
--- a/drivers/media/rc/serial_ir.c
+++ b/drivers/media/rc/serial_ir.c
@@ -353,7 +353,7 @@ static irqreturn_t serial_ir_irq_handler(int i, void *blah)
dcd = (status & hardware[type].signal_pin) ? 1 : 0;
if (dcd == last_dcd) {
- dev_err(&serial_ir.pdev->dev,
+ dev_dbg(&serial_ir.pdev->dev,
"ignoring spike: %d %d %lldns %lldns\n",
dcd, sense, ktime_to_ns(kt),
ktime_to_ns(serial_ir.lastkt));