aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/media/i2c/ccs/ccs-core.c
diff options
context:
space:
mode:
authorStanislaw Gruszka <[email protected]>2024-12-12 11:37:53 +0000
committerMauro Carvalho Chehab <[email protected]>2024-12-19 11:50:15 +0000
commit733d41af75d1eb1af046ab47053cd86465e10436 (patch)
tree378322797b3a9e876c32f1dbbd2c2d4c745d3e6c /drivers/media/i2c/ccs/ccs-core.c
parentmedia: rcar-csi2: Update D-PHY startup on V4M (diff)
downloadkernel-733d41af75d1eb1af046ab47053cd86465e10436.tar.gz
kernel-733d41af75d1eb1af046ab47053cd86465e10436.zip
media: intel/ipu6: move some boot messages to debug level
When ipu6 driver is waiting for the ivsc driver to probe, which can fail or take long time, we can get plenty of ipu6 messages like this: [ 15.454049] intel-ipu6 0000:00:05.0: IPU6 in non-secure mode touch 0x0 mask 0xff [ 15.456600] intel-ipu6 0000:00:05.0: FW version: 20230925 [ 15.458292] intel-ipu6 0000:00:05.0: IPU6 in non-secure mode touch 0x0 mask 0xff [ 15.461186] intel-ipu6 0000:00:05.0: FW version: 20230925 [ 15.463616] intel-ipu6 0000:00:05.0: IPU6 in non-secure mode touch 0x0 mask 0xff [ 15.466490] intel-ipu6 0000:00:05.0: FW version: 20230925 Print them only when debugging is enabled to do not flood dmesg. Reviewed-by: Hans de Goede <[email protected]> Signed-off-by: Stanislaw Gruszka <[email protected]> Signed-off-by: Sakari Ailus <[email protected]> Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'drivers/media/i2c/ccs/ccs-core.c')
0 files changed, 0 insertions, 0 deletions