diff options
| author | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2013-12-19 16:10:13 +0200 |
|---|---|---|
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2014-01-13 12:19:55 +0200 |
| commit | ab7bf423af05542db94021cf9dbf1b0bf86226b1 (patch) | |
| tree | 6c2a1f1f7bf9eaca3f062124f512899437ced286 /drivers/video | |
| parent | 77601507bcfdd9845822458cd36327e592704c25 (diff) | |
| download | op-kernel-dev-ab7bf423af05542db94021cf9dbf1b0bf86226b1.zip op-kernel-dev-ab7bf423af05542db94021cf9dbf1b0bf86226b1.tar.gz | |
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')
| -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 27d6905..2ff9f03 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) goto cleanup; } + if (def_display) { + u16 w, h; + + def_display->driver->get_resolution(def_display, &w, &h); + + dev_info(fbdev->dev, "using display '%s' mode %dx%d\n", + def_display->name, w, h); + } + return 0; cleanup: |
