From patchwork Mon Oct 24 21:38:47 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lina Iyer X-Patchwork-Id: 9393319 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id B198860231 for ; Mon, 24 Oct 2016 21:40:37 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id A175729157 for ; Mon, 24 Oct 2016 21:40:37 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 93A8B2915F; Mon, 24 Oct 2016 21:40:37 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=2.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_MED, T_DKIM_INVALID autolearn=unavailable version=3.3.1 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.9]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id 1E7C629157 for ; Mon, 24 Oct 2016 21:40:37 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.85_2 #1 (Red Hat Linux)) id 1bymxk-0008BN-Ut; Mon, 24 Oct 2016 21:39:20 +0000 Received: from mail-pf0-x234.google.com ([2607:f8b0:400e:c00::234]) by bombadil.infradead.org with esmtps (Exim 4.85_2 #1 (Red Hat Linux)) id 1bymxg-00088H-Gv for linux-arm-kernel@lists.infradead.org; Mon, 24 Oct 2016 21:39:18 +0000 Received: by mail-pf0-x234.google.com with SMTP id r16so105406025pfg.1 for ; Mon, 24 Oct 2016 14:38:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=7UG+TzCsDAyAsRZ8sohuqi34MLiD6miuyDlAfFrUiPI=; b=a7pg9yp0il/RqAf4GnzdscJLNiwzYYj6fs/VhofPONEpSXBS27YpoI6iSzImxuw54o rE6AJATIcI++1cLyC1XDtR+CCNGD3GtrScYfPBu68mGKvthKfJ9v+QDTbf0sj8i0Is9B s6/Izr118eZl4N4SUg/IPLK5EbGE4fnMOlBHE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=7UG+TzCsDAyAsRZ8sohuqi34MLiD6miuyDlAfFrUiPI=; b=VUjKEJs/HamCbXMHQ8u15tHB7EJvrSNYV9pOZWVhS6DiuDuMoQeKnRqLm2DYzIhSjt ojf8N3czBwRgvMWKljZWr9Jj6I8ImMiZnct6Dl3rrB8qbyLY4mT+uQ0zoGVf8W37juzH JtO6t/YAyLOrmFTcYqQIHx4sozBQt6uJfPN4QIlBv+guKITndlUTnXIBAQksKScHGLj7 4/1+ZG9SsYHvhhjoAcgM+7OjcCNTTYMJi/CmXLCwInwFcUll2JL+n30ZoGm+YlDVle/q FYL9Jhwi+BkZWI+PSqTMtYSPdlNIlOcpTgaQNN7m7917N+s52aQM4328POaniROT6n0i +zhw== X-Gm-Message-State: ABUngve2vqcmnUO1XWtoygtzgGE38hCup58MdCakhTL85NZQ/n5cqh8rV5hFFzZwy9E/kRJB X-Received: by 10.98.36.219 with SMTP id k88mr32344491pfk.88.1477345134479; Mon, 24 Oct 2016 14:38:54 -0700 (PDT) Received: from ubuntu.localdomain (i-global254.qualcomm.com. [199.106.103.254]) by smtp.gmail.com with ESMTPSA id r77sm27592617pfb.2.2016.10.24.14.38.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 24 Oct 2016 14:38:53 -0700 (PDT) From: Lina Iyer To: ulf.hansson@linaro.org, khilman@kernel.org, rjw@rjwysocki.net, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 [fix-2]] PM / doc: Update device documentation for devices in IRQ safe PM domains Date: Mon, 24 Oct 2016 14:38:47 -0700 Message-Id: <1477345127-23839-1-git-send-email-lina.iyer@linaro.org> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1477090375-13814-1-git-send-email-lina.iyer@linaro.org> References: <1477090375-13814-1-git-send-email-lina.iyer@linaro.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20161024_143916_679430_EF989E47 X-CRM114-Status: GOOD ( 12.81 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: lorenzo.pieralisi@arm.com, Juri.Lelli@arm.com, linux-arm-msm@vger.kernel.org, sboyd@codeaurora.org, brendan.jackman@arm.com, sudeep.holla@arm.com, andy.gross@linaro.org, Lina Iyer MIME-Version: 1.0 Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org X-Virus-Scanned: ClamAV using ClamSMTP Update documentation to reflect the changes made to support IRQ safe PM domains. Signed-off-by: Lina Iyer Signed-off-by: Rafael J. Wysocki --- Changes since: - Updated the text per Rafael's suggestion. - Updated commit text with signed-off-by --- 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 ---------------------------------