From: lina.iyer@linaro.org (Lina Iyer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] PM / doc: Update device documentation for devices in IRQ safe PM domains
Date: Tue, 25 Oct 2016 08:26:36 -0700 [thread overview]
Message-ID: <1477409199-52182-2-git-send-email-lina.iyer@linaro.org> (raw)
In-Reply-To: <1477409199-52182-1-git-send-email-lina.iyer@linaro.org>
Update documentation to reflect the changes made to support IRQ safe PM
domains.
Signed-off-by: Lina Iyer <lina.iyer@linaro.org>
Signed-off-by: Rafael J. Wysocki <rjw@rjwysocki.net>
---
Documentation/power/devices.txt | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/Documentation/power/devices.txt b/Documentation/power/devices.txt
index 8ba6625..73ddea3 100644
--- a/Documentation/power/devices.txt
+++ b/Documentation/power/devices.txt
@@ -607,7 +607,9 @@ individually. Instead, a set of devices sharing a power resource can be put
into a low-power state together at the same time by turning off the shared
power resource. Of course, they also need to be put into the full-power state
together, by turning the shared power resource on. A set of devices with this
-property is often referred to as a power domain.
+property is often referred to as a power domain. A power domain may also be
+nested inside another power domain. The nested domain is referred to as the
+sub-domain of the parent domain.
Support for power domains is provided through the pm_domain field of struct
device. This field is a pointer to an object of type struct dev_pm_domain,
@@ -629,6 +631,16 @@ support for power domains into subsystem-level callbacks, for example by
modifying the platform bus type. Other platforms need not implement it or take
it into account in any way.
+Devices may be defined as IRQ-safe which indicates to the PM core that their
+runtime PM callbacks may be invoked with disabled interrupts (see
+Documentation/power/runtime_pm.txt for more information). If an IRQ-safe
+device belongs to a PM domain, the runtime PM of the domain will be
+disallowed, unless the domain itself is defined as IRQ-safe. However, it
+makes sense to define a PM domain as IRQ-safe only if all the devices in it
+are IRQ-safe. Moreover, if an IRQ-safe domain has a parent domain, the runtime
+PM of the parent is only allowed if the parent itself is IRQ-safe too with the
+additional restriction that all child domains of an IRQ-safe parent must also
+be IRQ-safe.
Device Low Power (suspend) States
---------------------------------
--
2.7.4
next prev parent reply other threads:[~2016-10-25 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 15:26 [PATCH 0/4] PM / Domains: DT bindings for domain idle states and doc updates Lina Iyer
2016-10-25 15:26 ` Lina Iyer [this message]
2016-11-01 4:15 ` [PATCH 1/4] PM / doc: Update device documentation for devices in IRQ safe PM domains Rafael J. Wysocki
2016-10-25 15:26 ` [PATCH 2/4] dt-bindings: add domain-idle-state compatible to arm, idle-state Lina Iyer
2016-10-25 15:26 ` [PATCH 3/4] dt-bindings: Update domain-idle-state binding to use correct compatibles Lina Iyer
2016-10-25 15:59 ` Sudeep Holla
2016-10-25 16:24 ` Lina Iyer
2016-10-25 16:52 ` Sudeep Holla
2016-10-25 20:49 ` Kevin Hilman
2016-10-26 8:57 ` Sudeep Holla
2016-10-31 2:50 ` Rob Herring
2016-10-25 15:26 ` [PATCH 4/4] PM / Domains: Use domain-idle-state compatible Lina Iyer
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=1477409199-52182-2-git-send-email-lina.iyer@linaro.org \
--to=lina.iyer@linaro.org \
--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).