From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME
Date: Wed, 12 Nov 2014 09:56:38 +0100 [thread overview]
Message-ID: <1415782598.4247.2.camel@AMDC1943> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1411101346430.13641-100000@netrider.rowland.org>
On pon, 2014-11-10 at 13:59 -0500, Alan Stern wrote:
> [CC: list severely trimmed]
>
> On Mon, 10 Nov 2014, Ulf Hansson wrote:
>
> > >> There are an important advantage of using the pm_runtime_force_suspend() here.
> > >>
> > >> For the driver to handle clock gating at system PM suspend, it first
> > >> needs to bring the device into full power, through
> > >> pm_runtime_get_sync(). Otherwise it's not safe to gate the clock,
> > >> since it may already be gated.
> > >
> > > That's fine, but it has nothing to do with pm_runtime_force_suspend().
> > >
> > > Besides, if the real question is whether or not to gate the clock (or
> > > in other words, has the clock already been gated), why not just store a
> > > "clock_is_gated" flag somewhere?
> >
> > You could do that, but it's easier to not.
>
> I'm not convinced. And you haven't said how this is related to
> pm_runtime_force_suspend().
>
> > You will need to update the runtime PM status and disable runtime PM
> > anyway, done by the API.
>
> So what? And what API are you referring to: the runtime PM API or
> something else?
>
> I get the feeling that I'm missing a lot of important points here.
> What have you left out?
>
> As I understand the problem, you've got a bus type where some of the
> drivers have IRQ-safe runtime PM (and therefore carry out their
> suspend/resume operations in interrupt context) and others don't. The
> subsystem core wants to maximize the power saving by deconfiguring some
> clocks whenever a device is suspended, but this requires a process
> context and so it can't be done directly when IRQ-safe runtime PM is
> used.
>
> Is that a good summary? If it is, there are ways of dealing with this
> that don't involve messing around with the runtime PM internals, or
> using pm_runtime_force_suspend().
Thank you all for this precious feedback. I'll try the way with skipping
runtime PM stack completely during system suspend. Probably that will
add some complexity to the amba/bus and pl330 but there shouldn't be any
changes to PM core.
Best regards,
Krzysztof
next prev parent reply other threads:[~2014-11-12 8:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 8:36 [PATCH v10 0/5] amba/dmaengine: pl330: add Power Management support Krzysztof Kozlowski
2014-11-06 8:36 ` [PATCH v10 1/5] PM / Runtime: Allow accessing irq_safe if no PM_RUNTIME Krzysztof Kozlowski
2014-11-06 10:00 ` Ulf Hansson
2014-11-06 22:51 ` Rafael J. Wysocki
2014-11-07 8:06 ` Krzysztof Kozlowski
2014-11-07 14:50 ` Alan Stern
2014-11-07 23:45 ` Rafael J. Wysocki
2014-11-10 14:11 ` Ulf Hansson
2014-11-10 16:36 ` Alan Stern
2014-11-10 18:35 ` Ulf Hansson
2014-11-10 18:59 ` Alan Stern
2014-11-12 8:56 ` Krzysztof Kozlowski [this message]
2014-11-12 10:39 ` Ulf Hansson
2014-11-12 10:44 ` Krzysztof Kozlowski
2014-11-12 16:34 ` Alan Stern
2014-11-13 10:22 ` Ulf Hansson
2014-11-13 15:55 ` Alan Stern
2014-11-10 13:38 ` Ulf Hansson
2014-11-10 13:43 ` Srikanth K
2014-11-06 8:36 ` [PATCH v10 2/5] amba: Add helpers for (un)preparing AMBA clock Krzysztof Kozlowski
2014-11-06 8:36 ` [PATCH v10 3/5] amba: Don't unprepare the clocks if device driver wants IRQ safe runtime PM Krzysztof Kozlowski
2014-11-06 10:03 ` Ulf Hansson
2014-11-06 22:52 ` Rafael J. Wysocki
2014-11-07 8:01 ` Krzysztof Kozlowski
2014-11-07 23:52 ` Rafael J. Wysocki
2014-11-06 8:36 ` [PATCH v10 4/5] dmaengine: pl330: add Power Management support Krzysztof Kozlowski
2014-11-06 12:45 ` Vinod Koul
2014-11-06 8:36 ` [PATCH v10 5/5] amba: Remove unused amba_pclk_enable/disable macros Krzysztof Kozlowski
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=1415782598.4247.2.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
--cc=ulf.hansson@linaro.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).