From patchwork Fri Nov 18 09:23:12 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Viresh Kumar X-Patchwork-Id: 82851 Delivered-To: patch@linaro.org Received: by 10.140.97.165 with SMTP id m34csp1239721qge; Fri, 18 Nov 2016 01:24:08 -0800 (PST) X-Received: by 10.129.53.194 with SMTP id c185mr6482440ywa.205.1479461048861; Fri, 18 Nov 2016 01:24:08 -0800 (PST) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t59si1475594ybi.234.2016.11.18.01.24.07; Fri, 18 Nov 2016 01:24:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753240AbcKRJXt (ORCPT + 26 others); Fri, 18 Nov 2016 04:23:49 -0500 Received: from mail-pf0-f172.google.com ([209.85.192.172]:36118 "EHLO mail-pf0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752758AbcKRJXg (ORCPT ); Fri, 18 Nov 2016 04:23:36 -0500 Received: by mail-pf0-f172.google.com with SMTP id 189so54194094pfz.3 for ; Fri, 18 Nov 2016 01:23:35 -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:in-reply-to:references :in-reply-to:references; bh=wz5HwhQhuNDMG8H4g1191q1rwlk6nDg8us8EYQB5/qs=; b=DAOeltNuaHugefDM/2v2DOvOyipLMu8yqcSdkHy4K2TrtXZmlGfGp/kp4uLMfzJ5Oz 2ofQ3DD9SaPIqITWZsSYsfClCTGB7VCK5z7HjeV+9simf8CzuYthYEOxo7TryMcCZ2Fg bqkXwOvmgVp35aaOh0kztRzCokQLJtHdRGtMY= 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:in-reply-to:references; bh=wz5HwhQhuNDMG8H4g1191q1rwlk6nDg8us8EYQB5/qs=; b=enosSisvkNEmIEWqb9L26G4RR866tevCn4TEteeHRlzmrfL/1iCnKdFBxdOtajVobE t+FfCOjqvkFobEPihyTTegoOSgW07FQDXYUlxjLtud2A5j8E+LDc2u4FKNq/1GC6ems7 vbv7p3S/CjP3oXpal39CsodadKSjfnwvktqXPIAdhvNNRPBfyzat6Rsrpd+fcdHZX7g8 CR87W2/R54xeiNEXNn8jafej58Hsqxsv9tVXGrMPds0dUuqYy0Nm1LM5XViRAHjUIzpK NE/CRUVU4M7iuvXWQomM1lE0hzbsS9PS48upIdcvVdlXW3KKpojyDfa71ELd5ALF6r3f VN8A== X-Gm-Message-State: ABUngvf8NnjUh9EM/eJyW76/OP+UGy+Bkj7tyr71bxIlHnB2mhDo9BjljOtCHbZlC59L+bTp X-Received: by 10.98.30.1 with SMTP id e1mr10586005pfe.28.1479461015123; Fri, 18 Nov 2016 01:23:35 -0800 (PST) Received: from localhost ([122.172.89.192]) by smtp.gmail.com with ESMTPSA id v76sm15610513pfk.77.2016.11.18.01.23.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Nov 2016 01:23:34 -0800 (PST) From: Viresh Kumar To: Rafael Wysocki Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , Mark Rutland , Kevin Hilman , Ulf Hansson , Vincent Guittot , Lina Iyer , devicetree@vger.kernel.org, Stephen Boyd , Nayak Rajendra , Viresh Kumar Subject: [PATCH 1/2] PM / Domains: Introduce domain-performance-state binding Date: Fri, 18 Nov 2016 14:53:12 +0530 Message-Id: X-Mailer: git-send-email 2.7.1.410.g6faf27b In-Reply-To: References: In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Some platforms have the capability to configure the performance state of their Power Domains. The performance levels are represented by positive integer values, a lower value represents lower performance state. The power-domains until now were only concentrating on the idle state management of the device and this needs to change in order to reuse the infrastructure of power domains for active state management. This patch introduces a new optional property for the consumers of the power-domains: domain-performance-state. If the consumers don't need the capability of switching to different domain performance states at runtime, then they can simply define their required domain performance state in their node directly. Otherwise the consumers can define their requirements with help of other infrastructure, for example the OPP table. Signed-off-by: Viresh Kumar --- Documentation/devicetree/bindings/power/power_domain.txt | 6 ++++++ 1 file changed, 6 insertions(+) -- 2.7.1.410.g6faf27b diff --git a/Documentation/devicetree/bindings/power/power_domain.txt b/Documentation/devicetree/bindings/power/power_domain.txt index e1650364b296..db42eacf8b5c 100644 --- a/Documentation/devicetree/bindings/power/power_domain.txt +++ b/Documentation/devicetree/bindings/power/power_domain.txt @@ -106,6 +106,12 @@ domain provided by the 'parent' power controller. - power-domains : A phandle and PM domain specifier as defined by bindings of the power controller specified by phandle. +Optional properties: +- domain-performance-state: A positive integer value representing the minimum + performance level (of the parent domain) required by the consumer for its + working. The integer value '1' represents the lowest performance level and the + highest value represents the highest performance level. + Example: leaky-device@12350000 {