[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0jAvvG2vDEOP=yrp11xzai0tiLUuZJCebHihQ-wbFM3PQ@mail.gmail.com>
Date: Fri, 18 Sep 2015 02:03:24 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Alan Stern <stern@...land.harvard.edu>,
Thierry Reding <thierry.reding@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Tomeu Vizoso <tomeu.vizoso@...labora.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] driver core: Ensure proper suspend/resume ordering
On Fri, Sep 18, 2015 at 1:59 AM, Rafael J. Wysocki <rafael@...nel.org> wrote:
> Hi,
>
> On Thu, Sep 17, 2015 at 5:48 PM, Grygorii Strashko
> <grygorii.strashko@...com> wrote:
[cut]
>
> In any case, maybe call that from dpm_suspend_start() after
> dpm_prepare() has run successfully? This is the point we need to
> start to block probing after all.
Actually, even before dpm_prepare().
>
>> + }
>> +
>> if (error)
>> thaw_processes();
>> return error;
>> @@ -190,6 +197,7 @@ void thaw_processes(void)
>> atomic_dec(&system_freezing_cnt);
>> pm_freezing = false;
>> pm_nosig_freezing = false;
>> + device_force_probe_deferral(false);
>
> And why don't you call that from dpm_resume_end()?
>
>>
>> oom_killer_enable();
>>
>> --
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists