All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	linux-pm@vger.kernel.org
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	linux-arm-kernel@lists.infradead.org,
	Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: [RFC PATCH 2/5] regulator: Document the regulator-allow-changes-at-runtime DT property
Date: Fri,  2 Dec 2016 14:57:13 +0100	[thread overview]
Message-ID: <1480687036-5037-3-git-send-email-boris.brezillon@free-electrons.com> (raw)
In-Reply-To: <1480687036-5037-1-git-send-email-boris.brezillon@free-electrons.com>

regulator-allow-changes-at-runtime is an extra property that can be
set in a regulator suspend state to tell whether the suspend state can
be entered at runtime or not.

Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
---
 Documentation/devicetree/bindings/regulator/regulator.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt
index 6ab5aef619d9..7b724650500a 100644
--- a/Documentation/devicetree/bindings/regulator/regulator.txt
+++ b/Documentation/devicetree/bindings/regulator/regulator.txt
@@ -37,6 +37,11 @@ Optional properties:
 	  The set of possible operating modes depends on the capabilities of
 	  every hardware so the valid modes are documented on each regulator
 	  device tree binding document.
+	- regulator-allow-changes-at-runtime: runtime changes are allowed when
+	  the regulator does not support programming a suspend state that will
+	  be applied later on when the system is suspended.
+	  Applying changes at runtime can be dangerous, and you should only
+	  add this property if you know what you're doing.
 - regulator-initial-mode: initial operating mode. The set of possible operating
   modes depends on the capabilities of every hardware so each device binding
   documentation explains which values the regulator supports.
-- 
2.7.4


WARNING: multiple messages have this Message-ID (diff)
From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/5] regulator: Document the regulator-allow-changes-at-runtime DT property
Date: Fri,  2 Dec 2016 14:57:13 +0100	[thread overview]
Message-ID: <1480687036-5037-3-git-send-email-boris.brezillon@free-electrons.com> (raw)
In-Reply-To: <1480687036-5037-1-git-send-email-boris.brezillon@free-electrons.com>

regulator-allow-changes-at-runtime is an extra property that can be
set in a regulator suspend state to tell whether the suspend state can
be entered at runtime or not.

Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
---
 Documentation/devicetree/bindings/regulator/regulator.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt
index 6ab5aef619d9..7b724650500a 100644
--- a/Documentation/devicetree/bindings/regulator/regulator.txt
+++ b/Documentation/devicetree/bindings/regulator/regulator.txt
@@ -37,6 +37,11 @@ Optional properties:
 	  The set of possible operating modes depends on the capabilities of
 	  every hardware so the valid modes are documented on each regulator
 	  device tree binding document.
+	- regulator-allow-changes-at-runtime: runtime changes are allowed when
+	  the regulator does not support programming a suspend state that will
+	  be applied later on when the system is suspended.
+	  Applying changes at runtime can be dangerous, and you should only
+	  add this property if you know what you're doing.
 - regulator-initial-mode: initial operating mode. The set of possible operating
   modes depends on the capabilities of every hardware so each device binding
   documentation explains which values the regulator supports.
-- 
2.7.4

  parent reply	other threads:[~2016-12-02 13:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 13:57 [RFC PATCH 0/5] ARM: at91: sama5d2_xplained: Put the PMIC a proper suspend state Boris Brezillon
2016-12-02 13:57 ` Boris Brezillon
2016-12-02 13:57 ` [RFC PATCH 1/5] regulator: Extend the power-management APIs Boris Brezillon
2016-12-02 13:57   ` Boris Brezillon
2017-01-09 19:17   ` Mark Brown
2017-01-09 19:17     ` Mark Brown
2017-01-10  8:33     ` Boris Brezillon
2017-01-10  8:33       ` Boris Brezillon
2017-01-10 12:10       ` Mark Brown
2017-01-10 12:10         ` Mark Brown
2017-01-10 13:05         ` Boris Brezillon
2017-01-10 13:05           ` Boris Brezillon
2017-01-25 15:02           ` Alexandre Belloni
2017-01-25 15:02             ` Alexandre Belloni
2017-02-01 17:51             ` Mark Brown
2017-02-01 17:51               ` Mark Brown
2017-02-07 17:06           ` Boris Brezillon
2017-02-07 17:06             ` Boris Brezillon
2016-12-02 13:57 ` Boris Brezillon [this message]
2016-12-02 13:57   ` [RFC PATCH 2/5] regulator: Document the regulator-allow-changes-at-runtime DT property Boris Brezillon
2016-12-02 13:57 ` [RFC PATCH 3/5] ARM: at91: Call regulator_suspend_{begin, end}() in the platform pm ops Boris Brezillon
2016-12-02 13:57   ` Boris Brezillon
2016-12-02 13:57 ` [RFC PATCH 4/5] regulator: act8945: Implement PM functionalities Boris Brezillon
2016-12-02 13:57   ` Boris Brezillon
2016-12-02 13:57 ` [RFC PATCH 5/5] ARM: at91/dt: sama5d2_xplained: Add proper regulator states for suspend-to-mem Boris Brezillon
2016-12-02 13:57   ` Boris Brezillon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1480687036-5037-3-git-send-email-boris.brezillon@free-electrons.com \
    --to=boris.brezillon@free-electrons.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=broonie@kernel.org \
    --cc=len.brown@intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.