It's perfectly normal for fw_cfg to be available, but ramfb not being
configured. Driver core handles -ENODEV silently to accommodate this
case. The initcall calling ramfb_probe does too, but ramfb_probe itself
prints an error. Replace that with a debug print.
Fixes: 1db52e5a1039 ("video: add support for QEMU ramfb")
Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx>
---
drivers/video/ramfb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/ramfb.c b/drivers/video/ramfb.c
index 26e01196fc02..3442e81b9e51 100644
--- a/drivers/video/ramfb.c
+++ b/drivers/video/ramfb.c
@@ -131,7 +131,7 @@ static int ramfb_probe(struct device *parent_dev, int fd)
ret = fw_cfg_find_file(parent_dev, fd, "etc/ramfb");
if (ret < 0) {
- dev_err(parent_dev, "ramfb: fw_cfg (etc/ramfb) file not found\n");
+ dev_dbg(parent_dev, "ramfb: fw_cfg (etc/ramfb) file not found\n");
return -ENODEV;
}
--
2.39.2
