diff options
author | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2013-12-19 09:10:13 -0500 |
---|---|---|
committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2014-01-13 05:19:55 -0500 |
commit | ab7bf423af05542db94021cf9dbf1b0bf86226b1 (patch) | |
tree | 6c2a1f1f7bf9eaca3f062124f512899437ced286 /drivers/video/omap2/omapfb | |
parent | 77601507bcfdd9845822458cd36327e592704c25 (diff) |
OMAPFB: give informative print when probe succeeds
It is quite common to have omapfb probe deferred because of a missing
resource, and to get omapfb probed succesfully a bit later. This works
fine. However, omapfb does not give any print on a successful probe, so
if the omapfb is actually never probed again after deferral, this is not
shown in the log.
To help debugging, add a simple print from omapfb at the end of its
probe, saying which display it is using and in which resolution.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'drivers/video/omap2/omapfb')
-rw-r--r-- | drivers/video/omap2/omapfb/omapfb-main.c | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/drivers/video/omap2/omapfb/omapfb-main.c b/drivers/video/omap2/omapfb/omapfb-main.c index 27d6905683f3..2ff9f039b7cb 100644 --- a/drivers/video/omap2/omapfb/omapfb-main.c +++ b/drivers/video/omap2/omapfb/omapfb-main.c | |||
@@ -2557,6 +2557,15 @@ static int omapfb_probe(struct platform_device *pdev) | |||
2557 | goto cleanup; | 2557 | goto cleanup; |
2558 | } | 2558 | } |
2559 | 2559 | ||
2560 | if (def_display) { | ||
2561 | u16 w, h; | ||
2562 | |||
2563 | def_display->driver->get_resolution(def_display, &w, &h); | ||
2564 | |||
2565 | dev_info(fbdev->dev, "using display '%s' mode %dx%d\n", | ||
2566 | def_display->name, w, h); | ||
2567 | } | ||
2568 | |||
2560 | return 0; | 2569 | return 0; |
2561 | 2570 | ||
2562 | cleanup: | 2571 | cleanup: |