media: fdp1: Reduce FCP not found message level to debug
When support for the IPMMU is not enabled, the FDP driver may be
probe-deferred multiple times, causing several messages to be printed
like:
rcar_fdp1 fe940000.fdp1: FCP not found (-517)
rcar_fdp1 fe944000.fdp1: FCP not found (-517)
Fix this by reducing the message level to debug level, as is done in the
VSP1 driver.
Fixes: 4710b752e0
("[media] v4l: Add Renesas R-Car FDP1 Driver")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
This commit is contained in:
parent
5db8a692fe
commit
4fd2293856
|
@ -2306,7 +2306,7 @@ static int fdp1_probe(struct platform_device *pdev)
|
||||||
fdp1->fcp = rcar_fcp_get(fcp_node);
|
fdp1->fcp = rcar_fcp_get(fcp_node);
|
||||||
of_node_put(fcp_node);
|
of_node_put(fcp_node);
|
||||||
if (IS_ERR(fdp1->fcp)) {
|
if (IS_ERR(fdp1->fcp)) {
|
||||||
dev_err(&pdev->dev, "FCP not found (%ld)\n",
|
dev_dbg(&pdev->dev, "FCP not found (%ld)\n",
|
||||||
PTR_ERR(fdp1->fcp));
|
PTR_ERR(fdp1->fcp));
|
||||||
return PTR_ERR(fdp1->fcp);
|
return PTR_ERR(fdp1->fcp);
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue