From patchwork Wed Feb 8 16:34:49 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lina Iyer X-Patchwork-Id: 93643 Delivered-To: patch@linaro.org Received: by 10.140.20.99 with SMTP id 90csp2768478qgi; Wed, 8 Feb 2017 08:35:48 -0800 (PST) X-Received: by 10.84.231.205 with SMTP id g13mr35246012pln.118.1486571747960; Wed, 08 Feb 2017 08:35:47 -0800 (PST) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m18si7490273pgd.142.2017.02.08.08.35.47; Wed, 08 Feb 2017 08:35:47 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-arm-msm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@linaro.org; spf=pass (google.com: best guess record for domain of linux-arm-msm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-arm-msm-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751654AbdBHQfp (ORCPT + 9 others); Wed, 8 Feb 2017 11:35:45 -0500 Received: from mail-pg0-f46.google.com ([74.125.83.46]:34126 "EHLO mail-pg0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752003AbdBHQfo (ORCPT ); Wed, 8 Feb 2017 11:35:44 -0500 Received: by mail-pg0-f46.google.com with SMTP id 14so50273123pgg.1 for ; Wed, 08 Feb 2017 08:35:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=G2TWlHEPLyw117pul4S3GjzRBblPRy2Kw2dUmvNcgow=; b=KWgbj4lMdIoqV0VLjpQAS0/C+aP6Uwb0r8VaX6m2QlRa0Md9d8mPFqiXnDKY7pYzBs jsdf5faG5plaL5/7ovI6uV/yvfO0pbLEJclrcV6re5mwCmvXeqjQfcfJztRIGiskirmh J9kX3t6bu5MBZ2BsHqjLV4h08yvzPlbowVLEc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=G2TWlHEPLyw117pul4S3GjzRBblPRy2Kw2dUmvNcgow=; b=UR1XRhb4HQFK8Msq+D07Dp5NQI65yatEbpCsE6VSBQ0REox+uz/R43oo6icLOIkCfF l2a55jogjJLUHJvfcIh62Knq9/7RY/1Z65F4xdtgaBgIf8UC+xhn3g/htwDJ0cVBzHgb gF6Nrkcv7pFe8jA0cIxB44ZL9TqTxqw5Z//qgE1uocTF0ImVR2mdelTLOkRJ9PFaNlOE g83/vMcDL4RPtosASvDgZUb/9AxEhpA83KBrsBenBZaFjELPkXGVT5Yo78QckVppFEdo xIlSr2CA5eV5qp0Quc9KD1sC+HLoCJfmuZViF5OdPGpFKIyKpBtl+6diWRk4ks3h89Ds 2IYA== X-Gm-Message-State: AIkVDXLECnffM4AAjcAZpEM3aZVX17mPKhbCsVDgEtfPujlfIlr38DII05e8a3C/V3dFdJEN X-Received: by 10.84.131.2 with SMTP id 2mr34865090pld.45.1486571702389; Wed, 08 Feb 2017 08:35:02 -0800 (PST) Received: from ubuntu.localdomain (i-global254.qualcomm.com. [199.106.103.254]) by smtp.gmail.com with ESMTPSA id y23sm21653325pfi.66.2017.02.08.08.34.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 08 Feb 2017 08:35:00 -0800 (PST) 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 Cc: andy.gross@linaro.org, sboyd@codeaurora.org, linux-arm-msm@vger.kernel.org, brendan.jackman@arm.com, lorenzo.pieralisi@arm.com, sudeep.holla@arm.com, Juri.Lelli@arm.com, Lina Iyer Subject: [PATCH 0/2] PM / Domains: Updates to IRQ safe PM domains Date: Wed, 8 Feb 2017 08:34:49 -0800 Message-Id: <1486571692-33212-1-git-send-email-lina.iyer@linaro.org> X-Mailer: git-send-email 2.7.4 Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org Hi, This follows the discussions at Linux Plumbers Conference on PM domains and idle states. In the context of CPU hierarchy, the CPU's idle states may be presented using the property domain-idle-states if the domain is considered as the boundary that powers on/off an individual CPU. To that effect, domain idle states may not be specified but not compatible with what PM domains expects. Hence ignore the idle states that are not "domain-idle-state" compatible. The second patch covers the case, where the hierarchy of PM domains is not powered off in the same context. Currently, a workqueue is scheduled to power off the parent domains in the hierarchy. In case of CPU PM domains, this will not work, since we are running with interrupts disabled. Hence for IRQ safe PM domains, power off the parent domains in the same context as the caller. I understand Ulf is working on some argument changes in the same area of functions. Will work with him to resolve conflicts before the merge. This is based on the tip of Rafel's next. Thanks, Lina Lina Iyer (2): PM / Domains: Ignore domain-idle-states that are not compatible PM / Domains: Support in context powering off parent domain .../devicetree/bindings/power/power_domain.txt | 4 ++- drivers/base/power/domain.c | 37 +++++++++++++++------- 2 files changed, 28 insertions(+), 13 deletions(-) -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html