Received: by 10.223.176.46 with SMTP id f43csp673916wra; Fri, 26 Jan 2018 05:11:46 -0800 (PST) X-Google-Smtp-Source: AH8x224ZlTHzL852VjZVb2/iBG/PMFVegDPSipdT/hOB3yR2g+GAfFDopypZnNxWI0wKL67GA9l0 X-Received: by 2002:a17:902:123:: with SMTP id 32-v6mr14413810plb.278.1516972305819; Fri, 26 Jan 2018 05:11:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516972305; cv=none; d=google.com; s=arc-20160816; b=N+DJP4p17wWtOf2jDJOTToLVp+CCwISN7J0NMuqVl4ou7HSNMqCpgGV6gw9oKYYihO nLhfdUaDYk9Vzguj7UCp5LZp+llZAwYfuhO/aiEn5n/og4RbrJ/FgQ87RuX1gvuKbxQ/ cbfuVBNdn4f0iyYuqwWgX5OXXjB9nsUNrysyFWY57nFyo/LSTIMCYp1ghEmDFKqLjCJV ghYYCK+aHJuogQK/s3Iak4zWpRyMIT4PZBgaX4xKMFLUbaF+5HOB+Z0OuEvQ/RpD7whe EFm8nDQiKgEG5peqKf66BrD1iZzgQUtLwLYWN6+A/4EczltSH4mcc9ceIjyP0Bcowdew 0o+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature:arc-authentication-results; bh=JvNSlIMTyVFAQEYAKhkukqbzC538/hhFEd2DI7mvImM=; b=c1Q4UgJT2+/kj7pqZoJHLtmKMXoBrXx09frxU6/8HTgUDBmJAS0E1VYEqx5qG42eru 3hGKjyxD+XUVnS4puR0CaQI5dhRyzoFqW3EiG8h9tdiA6YO1ByyTejxapYgYFepBNIR2 CgPJKYRfGgG0UdyDj2HYbmF69g2LaR58fNYwgFgXXRl1FWDCU0u4JF7wJvWvJg88kqeV H5vBRgAa6ZC7XbrzxpbJSD1RiG8HAzjnwsup4dn4V6EjaRDALyg8eXI4wQWt65ND1zwP eyen70MzSoOfaa3bf9tC84OoZWUAD1/X2v90Sc4q5VPMgypn4axW1fyg/ppeHmsvDAXp x3gQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=GX7imlsh; 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 sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r3-v6si3230876plb.232.2018.01.26.05.11.31; Fri, 26 Jan 2018 05:11:45 -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 header.s=google header.b=GX7imlsh; 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 sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751609AbeAZNJN (ORCPT + 99 others); Fri, 26 Jan 2018 08:09:13 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:46832 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751531AbeAZNJJ (ORCPT ); Fri, 26 Jan 2018 08:09:09 -0500 Received: by mail-pg0-f68.google.com with SMTP id s9so235144pgq.13 for ; Fri, 26 Jan 2018 05:09:09 -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; bh=JvNSlIMTyVFAQEYAKhkukqbzC538/hhFEd2DI7mvImM=; b=GX7imlshpDEJmErHJovp35i6klOjYgjG1Nza33wwkHQE6zD1jhrI60vlrVnjePrS0/ RhBbgSJAEDvSoNmg667+IADK9g/M3HfcTOeEN4HbGwY5GPZG9cNd9cWRmHJ1cYpJnPN2 ylJ/EzpsfyVvSquUDX0nLukPQqebRsBBJGQ1s= 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:in-reply-to :references; bh=JvNSlIMTyVFAQEYAKhkukqbzC538/hhFEd2DI7mvImM=; b=ic0U7MnZulBCzk0PJYQg/M2Uzynzx8Qd0ZYdErefydvQZcH5qGbHkGCMDrOjyHuF+l o+96zyTyDai7MP0CFjTxGdtVguXEpC5b4adu7omoWB8qEaxFkjDiVfn7YB2S2v66bYKp w+ru4t80He5OHF+seC65JwnU3ZPWq1vTtqSq2R/4zDGrUbERA7mdjwN/17XAFLiTWJrv 9zgF7D2VcZrd5O9pk1FX38LK71fsbN0BR2TgxxfdOJq46rjRYRpedE8z+TmH2myb0ccU GiLLp9vJwlvk+sqtR49ltiqGVVkZ5J0WNno2FW3VVtIrMaa24qnf+YzegeXj9hgqb/ob EhTw== X-Gm-Message-State: AKwxytd32g/JSi6xnWxLueI8gTg7BRh8wW4xmsHzQZASWj3ft54li3/X HlHHEJVFyuTn1lKPMIYrMP4omw== X-Received: by 10.98.80.20 with SMTP id e20mr19017594pfb.148.1516972149058; Fri, 26 Jan 2018 05:09:09 -0800 (PST) Received: from ubt.spreadtrum.com ([117.18.48.82]) by smtp.gmail.com with ESMTPSA id b6sm18663238pfe.85.2018.01.26.05.09.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 26 Jan 2018 05:09:08 -0800 (PST) From: Chunyan Zhang To: Mark Brown , Rob Herring Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Chunyan Zhang Subject: [PATCH V5 1/5] bindings: regulator: added support for suspend states Date: Fri, 26 Jan 2018 21:08:43 +0800 Message-Id: <1516972127-972-2-git-send-email-zhang.chunyan@linaro.org> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1516972127-972-1-git-send-email-zhang.chunyan@linaro.org> References: <1516972127-972-1-git-send-email-zhang.chunyan@linaro.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Some systems need to set regulators to specific states when they enter low power modes, especially around CPUs. There are many of these modes depending on the particular runtime state. Currently the regulator consumers are not granted permission to change suspend state of regulator devices, the constraints are configured at startup. In order to allow changes in a vlotage range, we need to add new properties for voltage range and a flag to give permission to change the suspend voltage and suspend on/off in suspend mode. Signed-off-by: Chunyan Zhang Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/regulator/regulator.txt | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt index 378f6dc..e459226 100644 --- a/Documentation/devicetree/bindings/regulator/regulator.txt +++ b/Documentation/devicetree/bindings/regulator/regulator.txt @@ -42,8 +42,16 @@ Optional properties: - regulator-state-[mem/disk] node has following common properties: - regulator-on-in-suspend: regulator should be on in suspend state. - regulator-off-in-suspend: regulator should be off in suspend state. - - regulator-suspend-microvolt: regulator should be set to this voltage - in suspend. + - regulator-suspend-min-microvolt: minimum voltage may be set in + suspend state. + - regulator-suspend-max-microvolt: maximum voltage may be set in + suspend state. + - regulator-suspend-microvolt: the default voltage which regulator + would be set in suspend. This property is now deprecated, instead + setting voltage for suspend mode via the API which regulator + driver provides is recommended. + - regulator-changeable-in-suspend: whether the default voltage and + the regulator on/off in suspend can be changed in runtime. - regulator-mode: operating mode in the given suspend state. The set of possible operating modes depends on the capabilities of every hardware so the valid modes are documented on each regulator -- 2.7.4