Hi Geert, On Monday 05 Sep 2016 10:20:52 Geert Uytterhoeven wrote: > On Mon, Sep 5, 2016 at 10:17 AM, Laurent Pinchart wrote: > >> BTW, it seems I missed a few more s2ram resume errors: > >> dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns -13 > >> PM: Device fe920000.vsp failed to resume noirq: error -13 > >> dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns -13 > >> PM: Device fe960000.vsp failed to resume noirq: error -13 > >> dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns -13 > >> PM: Device fe9a0000.vsp failed to resume noirq: error -13 > >> dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns -13 > >> PM: Device fe9b0000.vsp failed to resume noirq: error -13 > >> dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns -13 > >> PM: Device fe9c0000.vsp failed to resume noirq: error -13 > >> dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns -13 > >> PM: Device fea20000.vsp failed to resume noirq: error -13 > >> dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns -13 > >> PM: Device fea28000.vsp failed to resume noirq: error -13 > >> dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns -13 > >> PM: Device fea30000.vsp failed to resume noirq: error -13 > >> vsp1 fea38000.vsp: failed to reset wpf.0 > >> dpm_run_callback(): pm_genpd_resume_noirq+0x0/0x90 returns -110 > >> PM: Device fea38000.vsp failed to resume noirq: error -110 > >> > >> -13 == -EACCES, returned by rcar_fcp_enable() as pm_runtime_get_sync() > >> is called too early during system resume, > > > > Do you have a fix for this ? :-) > > Unfortuately not. Is this caused by the fact that pm_runtime_get_sync() is called on the FCP device before the FCP gets system-resumed ? Lovely PM order dependency :-/ -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
