From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] [media] rcar-fcp: Make sure rcar_fcp_enable() returns 0 on success
Date: Mon, 05 Sep 2016 11:25:46 +0300 [thread overview]
Message-ID: <2306869.36BMUujrVm@avalon> (raw)
In-Reply-To: <CAMuHMdUzEsPNuqTn0pc0SwocoT3o5c0bxtrwKvUxJ6VvKRS7Yg@mail.gmail.com>
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
next prev parent reply other threads:[~2016-09-05 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 15:36 [PATCH] [media] rcar-fcp: Make sure rcar_fcp_enable() returns 0 on success Geert Uytterhoeven
2016-08-17 12:55 ` Laurent Pinchart
2016-08-23 13:11 ` Geert Uytterhoeven
2016-09-05 8:17 ` Laurent Pinchart
2016-09-05 8:20 ` Geert Uytterhoeven
2016-09-05 8:25 ` Laurent Pinchart [this message]
2016-09-05 8:49 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2306869.36BMUujrVm@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox