From: grygorii.strashko@ti.com (Grygorii Strashko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PM / Domains: restore calling of .suspend/resume_noirq() callbacks
Date: Thu, 13 Nov 2014 20:43:24 +0200 [thread overview]
Message-ID: <5464FBCC.7060307@ti.com> (raw)
In-Reply-To: <2997289.NEH22PNoYM@vostro.rjw.lan>
Hi Rafael,
On 11/13/2014 03:33 AM, Rafael J. Wysocki wrote:
> On Wednesday, November 12, 2014 06:00:47 PM Grygorii Strashko wrote:
>> Now .suspend/resume_noirq() callbacks will not be called during
>> system wide suspend/resume for devices which belongs to some GPD.
>> It seems, that this change was accidentally introduced by
>> commit d23b9b00cdde ("PM / Domains: Rework system suspend callback
>> routines (v2)").
>
> I'm not sure if that was really accidentally.
>
> Can you describe the problem that the change below is attempting to
> address, without going to much into the history? IOW, what's that
> doesn't work right now?
There are no real issues - now in Kernel there are no users of GPD
which use "noirq" callbacks.
As of now, I'm trying to use GPD for Keyatone2, so
I'm studying it and playing with it to understand all benefits and
disadvantages of such solution.
So, I've found this issue, but not found any description of why
calls of these callbacks have been removed.
I'd very appreciate if can point me on?
>
>> This patch restores calling of .suspend/resume_noirq() callbacks
>> for devices from GPD during system wide suspend/resume.
>>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>> ---
>> drivers/base/power/domain.c | 14 +++++++++++---
>> 1 file changed, 11 insertions(+), 3 deletions(-)
>>
...
Regards,
-grygorii
next prev parent reply other threads:[~2014-11-13 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 16:00 [PATCH] PM / Domains: restore calling of .suspend/resume_noirq() callbacks Grygorii Strashko
2014-11-13 1:33 ` Rafael J. Wysocki
2014-11-13 18:43 ` Grygorii Strashko [this message]
2014-11-13 19:11 ` Geert Uytterhoeven
2014-11-13 19:30 ` Grygorii Strashko
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=5464FBCC.7060307@ti.com \
--to=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).