<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/Documentation/devicetree/bindings/regulator/regulator.txt, branch linux-6.2.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-6.2.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-6.2.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2019-05-22T12:22:51Z</updated>
<entry>
<title>regulator: Convert regulator binding to json-schema</title>
<updated>2019-05-22T12:22:51Z</updated>
<author>
<name>Rob Herring</name>
<email>robh@kernel.org</email>
</author>
<published>2019-05-21T21:20:29Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=1914a996436b09186489da73b807e1df71259f67'/>
<id>urn:sha1:1914a996436b09186489da73b807e1df71259f67</id>
<content type='text'>
Convert the common regulator binding to DT schema format. Note that all
the properties with standard unit suffixes have type checks already, so
only a description is necessary.

As fixed-regulator has already been converted, update the references in
it. Otherwise, keep regulator.txt with a reference to the schema to
avoid a bunch of treewide updates. regulator.txt can be removed when all
the regulator bindings are converted.

Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>Merge branch 'topic/coupled' of https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator into regulator-4.21 for trivial conflict</title>
<updated>2018-11-19T13:16:15Z</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2018-11-19T13:16:15Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=ffb8c1e45e7ae648a3a1689aa71be50fb459316e'/>
<id>urn:sha1:ffb8c1e45e7ae648a3a1689aa71be50fb459316e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>regulator: Change regulator-coupled-max-spread property</title>
<updated>2018-11-19T12:33:52Z</updated>
<author>
<name>Dmitry Osipenko</name>
<email>digetx@gmail.com</email>
</author>
<published>2018-11-18T21:56:16Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a8d8ee437ea0bf21f840f33ca87f8e1641727aae'/>
<id>urn:sha1:a8d8ee437ea0bf21f840f33ca87f8e1641727aae</id>
<content type='text'>
Redefine binding for regulator-coupled-max-spread property in a way that
max-spread values are defined per regulator couple instead of defining
single max-spread for the whole group of coupled regulators.

With that change the following regulators coupling configuration will be
possible:

regA: regulatorA {
	regulator-coupled-with = &lt;&amp;regB &amp;regC&gt;;
	regulator-coupled-max-spread = &lt;100000 300000&gt;;
};

regB: regulatorB {
	regulator-coupled-with = &lt;&amp;regA &amp;regC&gt;;
	regulator-coupled-max-spread = &lt;100000 200000&gt;;
};

regC: regulatorC {
	regulator-coupled-with = &lt;&amp;regA &amp;regB&gt;;
	regulator-coupled-max-spread = &lt;300000 200000&gt;;
};

Note that the regulator-coupled-max-spread property does not have any
users yet, hence it's okay to change the binding.

Signed-off-by: Dmitry Osipenko &lt;digetx@gmail.com&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>regulator: dt-bindings: add regulator-state-standby bindings</title>
<updated>2018-11-13T17:28:49Z</updated>
<author>
<name>Andrei.Stefanescu@microchip.com</name>
<email>Andrei.Stefanescu@microchip.com</email>
</author>
<published>2018-11-13T14:47:33Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=5279e96ff8033500b6008be5925ae2d20f42c434'/>
<id>urn:sha1:5279e96ff8033500b6008be5925ae2d20f42c434</id>
<content type='text'>
For state-mem and state-disk regulators can have
various parameters applied such as enabled/disabled,
current mode, voltage etc.

This patch adds documentation on how to set these parameters
in the device tree for the standby state.

Signed-off-by: Andrei Stefanescu &lt;andrei.stefanescu@microchip.com&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>regulator: Document new regulator-max-step-microvolt property</title>
<updated>2018-11-08T16:20:48Z</updated>
<author>
<name>Dmitry Osipenko</name>
<email>digetx@gmail.com</email>
</author>
<published>2018-10-05T15:36:34Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a2dfe7c7dfb65c814cfa2777b46e687db1820cc4'/>
<id>urn:sha1:a2dfe7c7dfb65c814cfa2777b46e687db1820cc4</id>
<content type='text'>
Certain hardware may require supply voltage to be changed in steps. Define
new property that allow to describe such hardware.

Signed-off-by: Dmitry Osipenko &lt;digetx@gmail.com&gt;
Reviewed-by: Rob Herring &lt;robh@kernel.org&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>regulator: Change regulator-coupled-max-spread property</title>
<updated>2018-11-08T16:20:43Z</updated>
<author>
<name>Dmitry Osipenko</name>
<email>digetx@gmail.com</email>
</author>
<published>2018-10-05T15:36:32Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d3b687c58ad9343532b4a20e541934eb1b557453'/>
<id>urn:sha1:d3b687c58ad9343532b4a20e541934eb1b557453</id>
<content type='text'>
Redefine binding for regulator-coupled-max-spread property in a way that
max-spread values are defined per regulator couple instead of defining
single max-spread for the whole group of coupled regulators.

With that change the following regulators coupling configuration will be
possible:

regA: regulatorA {
	regulator-coupled-with = &lt;&amp;regB &amp;regC&gt;;
	regulator-coupled-max-spread = &lt;100000 300000&gt;;
};

regB: regulatorB {
	regulator-coupled-with = &lt;&amp;regA &amp;regC&gt;;
	regulator-coupled-max-spread = &lt;100000 200000&gt;;
};

regC: regulatorC {
	regulator-coupled-with = &lt;&amp;regA &amp;regB&gt;;
	regulator-coupled-max-spread = &lt;300000 200000&gt;;
};

Signed-off-by: Dmitry Osipenko &lt;digetx@gmail.com&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>regulator: bindings: Add properties for coupled regulators</title>
<updated>2018-05-17T07:05:04Z</updated>
<author>
<name>Maciej Purski</name>
<email>m.purski@samsung.com</email>
</author>
<published>2018-04-23T14:33:38Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f98618b34542706eddc3b66abc271f1c8d8c4a05'/>
<id>urn:sha1:f98618b34542706eddc3b66abc271f1c8d8c4a05</id>
<content type='text'>
Some regulators require keeping their voltage spread below defined
max_spread.

Add properties to provide information on regulators' coupling.

Signed-off-by: Maciej Purski &lt;m.purski@samsung.com&gt;
Reviewed-by: Rob Herring &lt;robh@kernel.org&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>regulator: of: add property for allowed modes specification</title>
<updated>2018-05-17T05:11:18Z</updated>
<author>
<name>David Collins</name>
<email>collinsd@codeaurora.org</email>
</author>
<published>2018-05-12T01:46:46Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d73e2842a3e236a1f58ba498e4d6ae58e18f660a'/>
<id>urn:sha1:d73e2842a3e236a1f58ba498e4d6ae58e18f660a</id>
<content type='text'>
Add a common device tree property for regulator nodes to support
the specification of allowed operating modes.

Signed-off-by: David Collins &lt;collinsd@codeaurora.org&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'regulator/topic/core' into regulator-next</title>
<updated>2018-01-26T17:56:59Z</updated>
<author>
<name>Mark Brown</name>
<email>broonie@kernel.org</email>
</author>
<published>2018-01-26T17:56:59Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=73d8003749ebfd9617076213c0033e11aacf823c'/>
<id>urn:sha1:73d8003749ebfd9617076213c0033e11aacf823c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>regulator: added support for suspend states</title>
<updated>2018-01-26T14:43:42Z</updated>
<author>
<name>Chunyan Zhang</name>
<email>zhang.chunyan@linaro.org</email>
</author>
<published>2018-01-26T13:08:43Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=057c76440c791eb31eb68f3b003f67d00fcce51a'/>
<id>urn:sha1:057c76440c791eb31eb68f3b003f67d00fcce51a</id>
<content type='text'>
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 &lt;zhang.chunyan@linaro.org&gt;
Reviewed-by: Rob Herring &lt;robh@kernel.org&gt;
Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;
</content>
</entry>
</feed>
