From patchwork Mon Apr 27 12:43:39 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Geert Uytterhoeven X-Patchwork-Id: 464983 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 64F9F140318 for ; Mon, 27 Apr 2015 22:46:42 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932748AbbD0Mps (ORCPT ); Mon, 27 Apr 2015 08:45:48 -0400 Received: from xavier.telenet-ops.be ([195.130.132.52]:58191 "EHLO xavier.telenet-ops.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932769AbbD0Mnx (ORCPT ); Mon, 27 Apr 2015 08:43:53 -0400 Received: from ayla.of.borg ([84.193.93.87]) by xavier.telenet-ops.be with bizsmtp id M0jr1q00L1t5w8s010jrx8; Mon, 27 Apr 2015 14:43:51 +0200 Received: from ramsan.of.borg ([192.168.97.29] helo=ramsan) by ayla.of.borg with esmtp (Exim 4.82) (envelope-from ) id 1YmiO7-00006p-Au; Mon, 27 Apr 2015 14:43:51 +0200 Received: from geert by ramsan with local (Exim 4.82) (envelope-from ) id 1YmiO8-0003fP-12; Mon, 27 Apr 2015 14:43:52 +0200 From: Geert Uytterhoeven To: "Rafael J. Wysocki" , Kevin Hilman , Ulf Hansson , Axel Haslam Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven Subject: [PATCH/RFC v6 4/7] PM / Domains: Add DT bindings for PM QoS device latencies Date: Mon, 27 Apr 2015 14:43:39 +0200 Message-Id: <1430138622-14029-5-git-send-email-geert+renesas@glider.be> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1430138622-14029-1-git-send-email-geert+renesas@glider.be> References: <1430138622-14029-1-git-send-email-geert+renesas@glider.be> Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org PM QoS device start/stop are properties of the hardware. In legacy code, they're specified from platform code. On DT platforms, their values should come from DT. Signed-off-by: Geert Uytterhoeven --- v6: - Rebased on top of v4.1-rc1 for new RFC, v4: - Drop save/restore state latencies, as they're Linux driver-specific, - Change state to RFC, as this is put on hold, v3: - No changes, v2: - New. --- Documentation/devicetree/bindings/power/power_domain.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/devicetree/bindings/power/power_domain.txt b/Documentation/devicetree/bindings/power/power_domain.txt index d659e5cb39be6057..32d1d3a399fe2a48 100644 --- a/Documentation/devicetree/bindings/power/power_domain.txt +++ b/Documentation/devicetree/bindings/power/power_domain.txt @@ -73,12 +73,18 @@ Required properties: - power-domains : A phandle and PM domain specifier as defined by bindings of the power controller specified by phandle. +Optional properties: + - stop-latency: Stop latency of the device, in ns, + - start-latency: Start latency of the device, in ns, + Example: leaky-device@12350000 { compatible = "foo,i-leak-current"; reg = <0x12350000 0x1000>; power-domains = <&power 0>; + stop-latency = <250000>; + start-latency = <250000>; }; The node above defines a typical PM domain consumer device, which is located