[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171103173353.GJ28152@atomide.com>
Date: Fri, 3 Nov 2017 10:33:53 -0700
From: Tony Lindgren <tony@...mide.com>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: Charles Keepax <ckeepax@...nsource.cirrus.com>,
linux-gpio@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
ckeepax@...nsource.wolfsonmicro.com, swarren@...dia.com,
andy.shevchenko@...il.com, alcooperx@...il.com,
bcm-kernel-feedback-list@...adcom.com,
"Rafael J. Wysocki" <rjw@...ysocki.net>, linux-pm@...r.kernel.org
Subject: Re: [PATCH v2 0/2] pinctrl: Allow indicating loss of state across
suspend/resume
* Florian Fainelli <f.fainelli@...il.com> [171103 17:04]:
> On 11/03/2017 09:11 AM, Tony Lindgren wrote:
> The pinctrl provider is losing its state, hence these two patches.
OK
> > Anyways, the context lost flag should be managed in the PM core for
> > the device, so adding linux-pm and Rafael to Cc.
>
> I don't think it's that simple but sure, why not.
Just having bool context_lost in struct dev_pm_info would probably
be enough to allow drivers to deal with it. This flag could then
be set for a device by power domain related code that knows if
context got lost.
Anybody got better ideas?
Regards,
Tony
Powered by blists - more mailing lists