From: Tony Lindgren <tony@atomide.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
ckeepax@opensource.wolfsonmicro.com, swarren@nvidia.com,
andy.shevchenko@gmail.com, alcooperx@gmail.com,
bcm-kernel-feedback-list@broadcom.com,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 0/2] pinctrl: Allow indicating loss of state across suspend/resume
Date: Fri, 3 Nov 2017 10:33:53 -0700 [thread overview]
Message-ID: <20171103173353.GJ28152@atomide.com> (raw)
In-Reply-To: <da808465-dc64-6c33-0be6-e038e0f84bce@gmail.com>
* Florian Fainelli <f.fainelli@gmail.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
next prev parent reply other threads:[~2017-11-03 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171102231551.16220-1-f.fainelli@gmail.com>
[not found] ` <20171103103707.3e5wb3c7foxbuvvg@localhost.localdomain>
2017-11-03 16:11 ` [PATCH v2 0/2] pinctrl: Allow indicating loss of state across suspend/resume Tony Lindgren
2017-11-03 17:02 ` Florian Fainelli
2017-11-03 17:33 ` Tony Lindgren [this message]
2017-11-04 8:37 ` Charles Keepax
[not found] ` <20171104083707.gtmnhbrzlqjulwe4-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2017-11-07 16:00 ` Tony Lindgren
[not found] ` <20171103173353.GJ28152-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-11-04 12:25 ` Rafael J. Wysocki
2017-11-04 17:19 ` Florian Fainelli
2017-11-07 16:00 ` Tony Lindgren
2017-11-08 0:23 ` Rafael J. Wysocki
2017-11-08 0:28 ` Florian Fainelli
2017-11-08 0:45 ` Rafael J. Wysocki
2017-11-08 1:04 ` Tony Lindgren
2017-11-08 1:02 ` Tony Lindgren
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=20171103173353.GJ28152@atomide.com \
--to=tony@atomide.com \
--cc=alcooperx@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=swarren@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).