Received: by 10.223.176.46 with SMTP id f43csp822285wra; Fri, 26 Jan 2018 07:27:35 -0800 (PST) X-Google-Smtp-Source: AH8x224a9dkofxngb7peaAH6Eo+HsOREewZKR4Qg8eE4VuqJeNMIH1vYvQt+Fzkb6LgfU2QMLn/z X-Received: by 10.98.192.134 with SMTP id g6mr19405966pfk.91.1516980455600; Fri, 26 Jan 2018 07:27:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516980455; cv=none; d=google.com; s=arc-20160816; b=Cki3EkDcK+61nZXyQkGCwV0UrYOL3KzsyRmP1R5TAj6zFyBqQgGPi8wS8dA6Q0kzdL bsUpgTN2bhN7nO9Tvi+vxEQaaWyRA0uJoKTbht/aaFZfO3I4Hg26b1c/76W84QxIWNDw rPFOJQIV/yTXGAkJ4D3EfpooqPTn2iBUm/tt42yzyWHeSWRGRT5dsaTVODcyiIUz/T3i S9TEwqPX7chWr4JwraOccYfn79mC4KKgbfm/oCdlpjNj/jduq8nXQSnA/tdJtB5oqcpn jM42VcZ3nLyX8jLkF0tVO39/tQAZTb2DT9ayibYb8SyWIQcbcd9MxViDnnKHRbZ9uGin o03g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:message-id:in-reply-to:subject:cc:to :from:dkim-signature:arc-authentication-results; bh=fuMH223j7E6Cd2HQeJwZTdZ+X/j5IsCbKxNA5BZBZFQ=; b=f9lkluNMvSyNFJosmT3wxSaY+KPgnuuKLrBbI9lOISVSIUIHnSwMss3C64fc1HIOGy pBxZqDFIYH4bT2HQ5qnHA96NchlmcZbc7sVRt9B656VFcxo95x5yMhWuhmMZoFJYiJcn /GN7EP24LOrMKkaEws4zkBDufYIvnelrbck1qluUiIRuL0POK+jiI3SI2xpCwQURM42v qT8vazvStbNfQ20AYK9r6NFPjxPdndiEcf/mZ5ITumuN5l0eciIz2sRu/r7/YOlkrB+v KE+099Y+Nv9RONhxxs/tjxAdo6rKluALdWtX2mxfwbjwbdo7lcEyM6Z+sxX14tLOZCRv R4ag== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@sirena.org.uk header.s=20170815-heliosphere header.b=k1uyPQoL; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e1-v6si3822453pli.294.2018.01.26.07.27.21; Fri, 26 Jan 2018 07:27:35 -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=fail header.i=@sirena.org.uk header.s=20170815-heliosphere header.b=k1uyPQoL; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753534AbeAZP0p (ORCPT + 99 others); Fri, 26 Jan 2018 10:26:45 -0500 Received: from heliosphere.sirena.org.uk ([172.104.155.198]:38742 "EHLO heliosphere.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752745AbeAZP0O (ORCPT ); Fri, 26 Jan 2018 10:26:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sirena.org.uk; s=20170815-heliosphere; h=Date:Message-Id:In-Reply-To: Subject:Cc:To:From:Sender:Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:References: List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner: List-Archive; bh=fuMH223j7E6Cd2HQeJwZTdZ+X/j5IsCbKxNA5BZBZFQ=; b=k1uyPQoLYDZN 6LLE3F9+U5Km0ezjjiP8cjVMfBUWKGOyAcqP2sfDlZEIKSsV5SYOC08j9b6v8URd+qk400xmJGMAN QJZ+PkLkOxFFSTekNFFmQvA2GG4iC6IYfXlEgHDWbMNujABlEFO5eg+9qd4MdZ+0FD7PexQyfg5Ad rCLOA=; Received: from debutante.sirena.org.uk ([2001:470:1f1d:6b5::3] helo=debutante) by heliosphere.sirena.org.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ef5tM-0007EG-Ms; Fri, 26 Jan 2018 15:26:12 +0000 Received: from broonie by debutante with local (Exim 4.90) (envelope-from ) id 1ef5tM-0006fT-89; Fri, 26 Jan 2018 15:26:12 +0000 From: Mark Brown To: Chunyan Zhang Cc: Mark Brown , Mark Brown , Rob Herring , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Ulf Hansson , Arnd Bergmann , Chunyan Zhang , linux-kernel@vger.kernel.org Subject: Applied "regulator: added support for suspend states" to the regulator tree In-Reply-To: <1516607961-379-1-git-send-email-zhang.chunyan@linaro.org> Message-Id: Date: Fri, 26 Jan 2018 15:26:12 +0000 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The patch regulator: added support for suspend states has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark From 057c76440c791eb31eb68f3b003f67d00fcce51a Mon Sep 17 00:00:00 2001 From: Chunyan Zhang Date: Fri, 26 Jan 2018 21:08:43 +0800 Subject: [PATCH] regulator: added support for suspend states 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 Signed-off-by: Mark Brown --- 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 378f6dc8b8bd..e459226dfac9 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.15.1