<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/include/linux/regulator/consumer.h, branch v3.10.42</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v3.10.42</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v3.10.42'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2013-03-04T02:35:58+00:00</updated>
<entry>
<title>regulator: core: Mark all get and enable calls as __must_check</title>
<updated>2013-03-04T02:35:58+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@opensource.wolfsonmicro.com</email>
</author>
<published>2012-03-19T16:35:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=c8801a8e715d7793e1e7bcd2f6fe132234741753'/>
<id>urn:sha1:c8801a8e715d7793e1e7bcd2f6fe132234741753</id>
<content type='text'>
It's generally important that devices have power when they expect it so
drivers really ought to be checking for errors on the power up paths.

Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'regulator/topic/tol' into regulator-next</title>
<updated>2012-12-10T03:43:22+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@opensource.wolfsonmicro.com</email>
</author>
<published>2012-12-10T03:43:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=f4244c68fff39b28235c862d7533c825390e9020'/>
<id>urn:sha1:f4244c68fff39b28235c862d7533c825390e9020</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'regulator/topic/stub' into regulator-next</title>
<updated>2012-12-10T03:43:20+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@opensource.wolfsonmicro.com</email>
</author>
<published>2012-12-10T03:43:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=4247bfe20ab1cb8cf1874b811c0dc60bcd0249e8'/>
<id>urn:sha1:4247bfe20ab1cb8cf1874b811c0dc60bcd0249e8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>regulators: add regulator_can_change_voltage() function</title>
<updated>2012-12-06T06:13:34+00:00</updated>
<author>
<name>Marek Szyprowski</name>
<email>m.szyprowski@samsung.com</email>
</author>
<published>2012-12-04T14:01:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=d1e7de3007c6e34c5e6d5e1b707b5aba4a1cd57f'/>
<id>urn:sha1:d1e7de3007c6e34c5e6d5e1b707b5aba4a1cd57f</id>
<content type='text'>
Introduce a regulator_can_change_voltage() function for the subsytems or
drivers which might check if applying voltage change is possible and use
special workaround code when the driver is used with fixed regulators or
regulators with disabled ability to change the voltage.

Signed-off-by: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;
Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
</content>
</entry>
<entry>
<title>regulator: add missing prototype for regulator_is_supported_voltage</title>
<updated>2012-11-21T10:03:12+00:00</updated>
<author>
<name>Philip Rakity</name>
<email>prakity@nvidia.com</email>
</author>
<published>2012-11-20T17:07:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=1a8f85d402a2bf3b86c08c696a0adf36656f770a'/>
<id>urn:sha1:1a8f85d402a2bf3b86c08c696a0adf36656f770a</id>
<content type='text'>
avoids needs for CONFIG_REGULATOR in sdhci.c

Signed-off-by: Philip Rakity &lt;prakity@nvidia.com&gt;
Reviewed-by: Eric Miao &lt;eric.y.miao@gmail.com&gt;
Signed-off-by: Eric Miao &lt;eric.y.miao@gmail.com&gt;
Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
</content>
</entry>
<entry>
<title>regulator: core: Add regulator_is_supported_voltage_tol()</title>
<updated>2012-11-14T10:41:14+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@opensource.wolfsonmicro.com</email>
</author>
<published>2012-11-14T07:47:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=fe1e43f7190da98b396265639845a6cc0d748aad'/>
<id>urn:sha1:fe1e43f7190da98b396265639845a6cc0d748aad</id>
<content type='text'>
If consumers wish to set voltages based on a tolerance it stands to reason
that they will also want to query for support in the same manner.

Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Acked-by: Liam Girdwood &lt;lrg@ti.com&gt;
</content>
</entry>
<entry>
<title>Merge remote-tracking branches 'regulator/topic/core', 'regulator/topic/bypass', 'regulator/topic/tol', 'regulator/topic/drivers' and 'regulator/topic/tps6586x' into regulator-next</title>
<updated>2012-09-28T13:45:07+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@opensource.wolfsonmicro.com</email>
</author>
<published>2012-09-28T13:45:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=6a2027abd2048f7f7fdcc6e11ff10b3d9b0d0899'/>
<id>urn:sha1:6a2027abd2048f7f7fdcc6e11ff10b3d9b0d0899</id>
<content type='text'>
</content>
</entry>
<entry>
<title>regulator: core: Support bypass mode</title>
<updated>2012-09-10T03:25:10+00:00</updated>
<author>
<name>Mark Brown</name>
<email>broonie@opensource.wolfsonmicro.com</email>
</author>
<published>2012-08-31T17:36:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=f59c8f9fe689790248ae7aa7426579982050638c'/>
<id>urn:sha1:f59c8f9fe689790248ae7aa7426579982050638c</id>
<content type='text'>
Many regulators support a bypass mode where they simply switch their
input supply to the output. This is mainly used in low power retention
states where power consumption is extremely low so higher voltage or
less clean supplies can be used.

Support this by providing ops for the drivers and a consumer API which
allows the device to be put into bypass mode if all consumers enable it
and the machine enables permission for this.

This is not supported as a mode since the existing modes are rarely used
due to fuzzy definition and mostly redundant with modern hardware which is
able to respond promptly to load changes.

Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Reviewed-by: Graeme Gregory &lt;gg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>regulator: add a new API regulator_set_voltage_tol()</title>
<updated>2012-08-08T13:34:41+00:00</updated>
<author>
<name>Shawn Guo</name>
<email>shawn.guo@linaro.org</email>
</author>
<published>2012-08-05T15:05:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=3f1965776f6ec769192400810b6260fe48301bbb'/>
<id>urn:sha1:3f1965776f6ec769192400810b6260fe48301bbb</id>
<content type='text'>
There are some use cases where a voltage range could be reasonably
specified by a target voltage and tolerance.  Add a new API
regulator_set_voltage_tol() wrapping regulator_set_voltage() call
to ease the users.

Signed-off-by: Shawn Guo &lt;shawn.guo@linaro.org&gt;
Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
</content>
</entry>
<entry>
<title>regulator: add missing defintion regulator_is_supported_voltage</title>
<updated>2012-07-01T18:10:19+00:00</updated>
<author>
<name>Philip Rakity</name>
<email>prakity@marvell.com</email>
</author>
<published>2012-06-30T23:05:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=4fe23791a4052ad4c8ba79dab9ff5febc8095714'/>
<id>urn:sha1:4fe23791a4052ad4c8ba79dab9ff5febc8095714</id>
<content type='text'>
This definition is missing when CONFIG_REGULATOR is not defined.
This causes compiler errors when compiling sdhci.c.  This can
be worked around by adding #ifdef CONFIG_REGULATOR .. #endif
but since other definitions are there we have defined the missing
definition

Signed-off-by: Philip Rakity &lt;prakity@marvell.com&gt;
Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
</content>
</entry>
</feed>
