Received: by 10.223.176.46 with SMTP id f43csp2610350wra; Mon, 22 Jan 2018 00:01:07 -0800 (PST) X-Google-Smtp-Source: AH8x225drtzBEyyv26gttoddW6b+3nCjnsXsjRl4qRyrJjW05JurNv9tdQ0Ynt0NbLO2o958gr51 X-Received: by 10.98.71.197 with SMTP id p66mr7685716pfi.3.1516608067268; Mon, 22 Jan 2018 00:01:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516608067; cv=none; d=google.com; s=arc-20160816; b=TgkZEp/mYISU28kD7e7hQRpF7TUV68JYsHitSwhBorDbmCtuczUQU6GGAKkn5fWfsb OW+LaPpMtl1yfJk/S5LaNtucFaj4qXm5EBydKa1Oxnap6MEoAAOn2XRQvP3NsxVG7tnZ Im97wpTSIX4sThdnkt88QNkkIaI38+VBR3exq475SzkLvZYqW16K3xtkoFrugJ3nhjS0 EdfOWBWBRTjLBB35X4z2d6mh6Qk7/grOm9xLy3+92BkUf2fnSH9/oOkUbGuZEUTlmcGI 7Dur7EVdiCQCdmW2/sLr+MtvBkQrhMsbO3bi2I+sN3aZe93wRtF6sTSNt63n+6s3W9jJ hDtQ== 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=GxjiwE7y0YyDOH/aY6Zza9WwgHLSEkJRBVYFDg7LblQ=; b=P+/mAt9u/kcrNivpc17pOyd/6AJZDGXSq8yjF17L2G2wiHPeyU2N4o4JQCiJI6J6Yq Yuq8Ari+SQT+kMhWxIEiQ79aKAONvHCGnTZeWjhg+HzL8NOuB3sdq7apHpy0G70VTlYx oCuctQvRquCwYljwrfgOvYlCN8MHr9em/CoiJp+TjMGNJKhwhQ9WcUedAPB87GmWxdA4 2ur6p7Ee9E2DNMbaP0L9L2D0cjwNcXwwP34PmZV6yEJ/8bWUjKK4RLS+Gmfm2E/b88J3 T/BhPK9VfnvNO/frH8A+NxNsy/o6Rhu0ZGTdCLjaiMGEZcAhtK6lLlLmaAh2vbKx4sz0 y2qA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=evyY4DmP; 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 s12si1764768pgp.693.2018.01.22.00.00.52; Mon, 22 Jan 2018 00:01:07 -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=evyY4DmP; 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 S1751287AbeAVIAI (ORCPT + 99 others); Mon, 22 Jan 2018 03:00:08 -0500 Received: from mail-pg0-f66.google.com ([74.125.83.66]:36352 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751258AbeAVIAG (ORCPT ); Mon, 22 Jan 2018 03:00:06 -0500 Received: by mail-pg0-f66.google.com with SMTP id k68so6494911pga.3 for ; Mon, 22 Jan 2018 00:00:06 -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=GxjiwE7y0YyDOH/aY6Zza9WwgHLSEkJRBVYFDg7LblQ=; b=evyY4DmP1Pn0jJ38LmI5BKt77HIUXgOGRVg7GGLH2cZBPI4cjBbgB+xjdgu+5WSxBn t63D8RZ5mw9/lhr4cnaUO7E0voxFNyYFCCHouSa7OMSA9UpNZQbE7ll9Jv8zOZa/eIYS 5vgn7b+SvvOBIF3pVniUnWINnNUdzpE7gfqcw= 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=GxjiwE7y0YyDOH/aY6Zza9WwgHLSEkJRBVYFDg7LblQ=; b=Fqxv4RPPskRjaVhu/Q5tucJbmWJ20CMgx8HWC3mJHdY1vMGJudUS9zeQOCJnJRLu4k YEBbfGP4eGHPJ1xUAyTis4m9h6p98XIX2ai4mg37hZ0XnRDtsPPaTD5IgI3JSKWtKT99 Yn8DdA0jGea3WVHX+xt2JdUx7cZh2q2EQr0VsTRctSte/dlsvJOV9Mf729GSUmHYi+2f 4nyQ4XV+a+AMOHErMxgN5WWnhrrolkxB+u64z9uRVeQlP59Ds2H5b6Lfj9qsTbcqUB7g myo6JWSAO7ZNT3f5w4KQeoeQxupxw3J1S00S3FwBvG5vX/ND17KiugRXxKKWswCt8Lv/ ByDw== X-Gm-Message-State: AKwxytdxL+rbpNGuh8NplWpGMcvTSqo5WV+t5q7/ZD5KPwmDdVdyqD2w cA1jfDXdnJaAifbRWTKrOfxN+A== X-Received: by 10.99.96.203 with SMTP id u194mr6598219pgb.167.1516608005752; Mon, 22 Jan 2018 00:00:05 -0800 (PST) Received: from ubt.spreadtrum.com ([117.18.48.82]) by smtp.gmail.com with ESMTPSA id g77sm29986258pfk.49.2018.01.21.23.59.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 22 Jan 2018 00:00:04 -0800 (PST) From: Chunyan Zhang To: Mark Brown , Rob Herring Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Ulf Hansson , Arnd Bergmann , Chunyan Zhang Subject: [PATCH V4 1/5] bindings: regulator: added support for suspend states Date: Mon, 22 Jan 2018 15:59:21 +0800 Message-Id: <1516607961-379-1-git-send-email-zhang.chunyan@linaro.org> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1515752305-15907-2-git-send-email-zhang.chunyan@linaro.org> References: <1515752305-15907-2-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 --- 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