diff options
author | 2016-08-09 12:36:41 -0300 | |
---|---|---|
committer | 2016-08-24 14:00:01 -0300 | |
commit | ba75faf43dc60744608ffa1412fdeceff2126cbc (patch) | |
tree | 905d98fd439ef80ae1ffa3eb567e80029d1c1a4b /drivers/media/pci/cx23885/cx23885-dvb.c | |
parent | [media] media: pci: pt3: don't print error when adding adapter fails (diff) | |
download | linux-dev-ba75faf43dc60744608ffa1412fdeceff2126cbc.tar.xz linux-dev-ba75faf43dc60744608ffa1412fdeceff2126cbc.zip |
[media] rcar-fcp: Make sure rcar_fcp_enable() returns 0 on success
When resuming from suspend-to-RAM on r8a7795/salvator-x:
dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns 1
PM: Device fe940000.fdp1 failed to resume noirq: error 1
dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns 1
PM: Device fe944000.fdp1 failed to resume noirq: error 1
dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns 1
PM: Device fe948000.fdp1 failed to resume noirq: error 1
According to its documentation, rcar_fcp_enable() returns 0 on success
or a negative error code if an error occurs. Hence
fdp1_pm_runtime_resume() and vsp1_pm_runtime_resume() forward its return
value to their callers.
However, rcar_fcp_enable() forwards the return value of
pm_runtime_get_sync(), which can actually be 1 on success, leading to
the resume failure above.
To fix this, consider only negative values returned by
pm_runtime_get_sync() to be failures.
Fixes: 7b49235e83b2347c ("[media] v4l: Add Renesas R-Car FCP driver")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'drivers/media/pci/cx23885/cx23885-dvb.c')
0 files changed, 0 insertions, 0 deletions