diff options
| author | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2012-06-27 16:37:18 +0300 |
|---|---|---|
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2012-06-29 09:09:49 +0300 |
| commit | 5be3aebd09f384fa2db8dda4fd99b73fc4be64f1 (patch) | |
| tree | eca71eceffd74b3271a098ddf8e728e531ed6f10 /drivers/video/omap2/dss/dss.c | |
| parent | 2b8501d777346ce1d4fe99167e9b3c0e42aae7a8 (diff) | |
| download | linux-stable-5be3aebd09f384fa2db8dda4fd99b73fc4be64f1.tar.gz linux-stable-5be3aebd09f384fa2db8dda4fd99b73fc4be64f1.tar.bz2 linux-stable-5be3aebd09f384fa2db8dda4fd99b73fc4be64f1.zip | |
OMAPDSS: fix warnings if CONFIG_PM_RUNTIME=n
If runtime PM is not enabled in the kernel config, pm_runtime_get_sync()
will always return 1 and pm_runtime_put_sync() will always return
-ENOSYS. pm_runtime_get_sync() returning 1 presents no problem to the
driver, but -ENOSYS from pm_runtime_put_sync() causes the driver to
print a warning.
One option would be to ignore errors returned by pm_runtime_put_sync()
totally, as they only say that the call was unable to put the hardware
into suspend mode.
However, I chose to ignore the returned -ENOSYS explicitly, and print a
warning for other errors, as I think we should get notified if the HW
failed to go to suspend properly.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Jassi Brar <jaswinder.singh@linaro.org>
Cc: Grazvydas Ignotas <notasas@gmail.com>
Diffstat (limited to 'drivers/video/omap2/dss/dss.c')
| -rw-r--r-- | drivers/video/omap2/dss/dss.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/video/omap2/dss/dss.c b/drivers/video/omap2/dss/dss.c index 770632359a17..d2b57197b292 100644 --- a/drivers/video/omap2/dss/dss.c +++ b/drivers/video/omap2/dss/dss.c @@ -731,7 +731,7 @@ static void dss_runtime_put(void) DSSDBG("dss_runtime_put\n"); r = pm_runtime_put_sync(&dss.pdev->dev); - WARN_ON(r < 0 && r != -EBUSY); + WARN_ON(r < 0 && r != -ENOSYS && r != -EBUSY); } /* DEBUGFS */ |