media: atomisp: reduce debug printk rate when IRQs are received
authorMauro Carvalho Chehab <mchehab+huawei@kernel.org>
Thu, 21 May 2020 07:05:11 +0000 (09:05 +0200)
committerMauro Carvalho Chehab <mchehab+huawei@kernel.org>
Thu, 11 Jun 2020 15:58:26 +0000 (17:58 +0200)
commitaaebb6547610e7c739507e389296eb36aacc7908
treebff4c7838e324f1ebe5bd3daf7502df897019194
parent8ef6b8a67b015b4abe74d0488569a47e1f729a9b
media: atomisp: reduce debug printk rate when IRQs are received

Currently, when an EOF IRQ is received, it generates two messages:

[   59.191893] atomisp-isp2 0000:00:03.0: irq:0x200000
[   59.191913] atomisp-isp2 0000:00:03.0: atomisp_isr EOF exp_id 142, asd 0

Flooding the dmesg with lots of messages per second. The same
pattern happens for all other IRQs.

Change the logic for printing just one message per IRQ and
rate-limit those, as, for debugging purposes, it is usually
interesting to know that IRQs are being received, but not
displaying every single one.

Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
drivers/staging/media/atomisp/pci/atomisp_cmd.c