<feed xmlns='http://www.w3.org/2005/Atom'>
<title>user/sven/linux.git/include/linux/regulator, branch v2.6.37.2</title>
<subtitle>Linux Kernel
</subtitle>
<id>https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v2.6.37.2</id>
<link rel='self' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v2.6.37.2'/>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/'/>
<updated>2010-10-28T21:40:31Z</updated>
<entry>
<title>regulator: Add option for machine drivers to enable the dummy regulator</title>
<updated>2010-10-28T21:40:31Z</updated>
<author>
<name>Mark Brown</name>
<email>broonie@opensource.wolfsonmicro.com</email>
</author>
<published>2010-10-06T02:18:32Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=688fe99a439f7c9dfcc52fbf7cb347f140a2dc8b'/>
<id>urn:sha1:688fe99a439f7c9dfcc52fbf7cb347f140a2dc8b</id>
<content type='text'>
Allow machine drivers to explicitly enable the use of the dummy regulator,
enabling simpler support for systems with only a few specific supplies
visible to software.

It is strongly recommended that this is not used on systems with
substantial software control over their PMICs, for maximum functionality
constrints should be as fully specified as possible.

Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Signed-off-by: Liam Girdwood &lt;lrg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>Regulator: LP3972 PMIC regulator driver</title>
<updated>2010-10-28T21:40:31Z</updated>
<author>
<name>Axel Lin</name>
<email>axel.lin@gmail.com</email>
</author>
<published>2010-09-16T08:48:49Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=5976f0959d5251ae5b4db848eaa2f42a19e98652'/>
<id>urn:sha1:5976f0959d5251ae5b4db848eaa2f42a19e98652</id>
<content type='text'>
This patch adds regulator drivers for National Semiconductors LP3972 PMIC.
This LP3972 PMIC controller has 3 DC/DC voltage converters and 5 low drop-out
(LDO) regulators. LP3972 PMIC controller uses I2C interface.

Signed-off-by: Axel Lin &lt;axel.lin@gmail.com&gt;
Acked-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Signed-off-by: Liam Girdwood &lt;lrg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>MAX8952 PMIC Driver Initial Release</title>
<updated>2010-10-28T21:40:31Z</updated>
<author>
<name>MyungJoo Ham</name>
<email>myungjoo.ham@samsung.com</email>
</author>
<published>2010-08-20T05:43:56Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=202f4f53e503ae09b431459131b5b3a99fa6d839'/>
<id>urn:sha1:202f4f53e503ae09b431459131b5b3a99fa6d839</id>
<content type='text'>
MAX8952 PMIC is used to provide voltage output between 770mV - 1400mV
with DVS support. In this initial release, users can set voltages for
four DVS modes, RAMP delay values, and SYNC frequency.
Controlling FPWM/SYNC_MODE/Pull-Down/Ramp Modes and reading CHIP_ID
is not supported in this release.

If GPIO of EN is not valid in platform data, the driver assumes that it
is always-on. If GPIO of VID0 or VID1 is invalid, the driver pulls down
VID0 and VID1 to fix DVS mode as 0 and disables DVS support.

We assume that V_OUT is capable to provide every voltage from 770mV to
1.40V in 10mV steps although the data sheet has some ambiguity on it.

Signed-off-by: MyungJoo Ham &lt;myungjoo.ham@samsung.com&gt;
Signed-off-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;
Acked-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
--
v2:
	- Style correction
	- Can accept platform_data with invalid GPIOs
	- Removed unnecessary features
	- Improved error handling
Signed-off-by: Liam Girdwood &lt;lrg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>ab8500-mfd: add regulator support to ab8500 mfd device</title>
<updated>2010-08-11T10:38:01Z</updated>
<author>
<name>Sundar R Iyer</name>
<email>sundar.iyer@stericsson.com</email>
</author>
<published>2010-07-13T06:21:28Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=549931f99e030d63a437c23943fd8dc9b7c0e41c'/>
<id>urn:sha1:549931f99e030d63a437c23943fd8dc9b7c0e41c</id>
<content type='text'>
Acked-by: Linus Walleij &lt;linus.walleij@stericsson.com&gt;
Acked-By: Mattias Wallin &lt;mattias.wallin@stericsson.com&gt;
Acked-By: Bengt JONSSON &lt;bengt.g.jonsson@stericsson.com&gt;
Signed-off-by: Sundar R Iyer &lt;sundar.iyer@stericsson.com&gt;
Acked-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Acked-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
Signed-off-by: Liam Girdwood &lt;lrg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>regulator: tps6507x: allow driver to use DEFDCDC{2,3}_HIGH register</title>
<updated>2010-07-28T14:09:26Z</updated>
<author>
<name>Anuj Aggarwal</name>
<email>anuj.aggarwal@ti.com</email>
</author>
<published>2010-07-12T12:24:06Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=7d14831e21060fbfbfe8453460ac19205f4ce1c2'/>
<id>urn:sha1:7d14831e21060fbfbfe8453460ac19205f4ce1c2</id>
<content type='text'>
Acked-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;

In TPS6507x, depending on the status of DEFDCDC{2,3} pin either
DEFDCDC{2,3}_LOW or DEFDCDC{2,3}_HIGH register needs to be read or
programmed to change the output voltage.

The current driver assumes DEFDCDC{2,3} pins are always tied low
and thus operates only on DEFDCDC{2,3}_LOW register. This need
not always be the case (as is found on OMAP-L138 EVM).

Unfortunately, software cannot read the status of DEFDCDC{2,3} pins.
So, this information is passed through platform data depending on
how the board is wired.

Signed-off-by: Anuj Aggarwal &lt;anuj.aggarwal@ti.com&gt;
Signed-off-by: Sekhar Nori &lt;nsekhar@ti.com&gt;
Signed-off-by: Liam Girdwood &lt;lrg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>regulator: Allow regulator-regulator supplies to be specified by name</title>
<updated>2010-05-25T09:16:01Z</updated>
<author>
<name>Mark Brown</name>
<email>broonie@opensource.wolfsonmicro.com</email>
</author>
<published>2010-04-26T14:18:14Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=0178f3e28e2166664916265c5d4922b1376b9fa1'/>
<id>urn:sha1:0178f3e28e2166664916265c5d4922b1376b9fa1</id>
<content type='text'>
When one regulator supplies another allow the relationship to be specified
using names rather than struct regulators, in a similar manner to that
allowed for consumer supplies. This allows static configuration at compile
time, reducing the need for dynamic init code.

Also change the references to LINE supply to be system supply since line
is sometimes used for actual supplies and therefore potentially confusing.

Signed-off-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Signed-off-by: Liam Girdwood &lt;lrg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>regulator: Let drivers know when they use the stub API</title>
<updated>2010-04-19T12:17:10Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2010-04-03T15:37:45Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=be1a50d4eba4cdb3ebf9d97a0a8693c153436775'/>
<id>urn:sha1:be1a50d4eba4cdb3ebf9d97a0a8693c153436775</id>
<content type='text'>
Have the stub variant of regulator_get() return NULL, so that drivers
can (but still don't have to) handle this case specifically.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Cc: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Cc: Jerome Oufella &lt;jerome.oufella@savoirfairelinux.com&gt;
Acked-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Signed-off-by: Liam Girdwood &lt;lrg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>regulator: enable max8649 regulator driver</title>
<updated>2010-03-03T14:49:24Z</updated>
<author>
<name>Haojian Zhuang</name>
<email>haojian.zhuang@marvell.com</email>
</author>
<published>2010-01-25T15:24:09Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=a71b797fdc672714bfff1fdc142042a95e97d7ba'/>
<id>urn:sha1:a71b797fdc672714bfff1fdc142042a95e97d7ba</id>
<content type='text'>
Signed-off-by: Haojian Zhuang &lt;haojian.zhuang@marvell.com&gt;
Acked-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Signed-off-by: Liam Girdwood &lt;lrg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>regulator: Add 'start-up time' to fixed voltage regulators</title>
<updated>2010-03-03T14:49:23Z</updated>
<author>
<name>Adrian Hunter</name>
<email>adrian.hunter@nokia.com</email>
</author>
<published>2010-01-12T10:25:13Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=eda79a3041a2cada0d4ee9491c99c3874b322356'/>
<id>urn:sha1:eda79a3041a2cada0d4ee9491c99c3874b322356</id>
<content type='text'>
Add a field to specify a delay for the start-up time of
a fixed voltage regulator.

Signed-off-by: Adrian Hunter &lt;adrian.hunter@nokia.com&gt;
Acked-by: Mark Brown &lt;broonie@opensource.wolfsonmicro.com&gt;
Signed-off-by: Liam Girdwood &lt;lrg@slimlogic.co.uk&gt;
</content>
</entry>
<entry>
<title>regulator: Allow regulators to specify the time taken to ramp on enable</title>
<updated>2010-03-03T14:49:23Z</updated>
<author>
<name>Mark Brown</name>
<email>broonie@opensource.wolfsonmicro.com</email>
</author>
<published>2009-12-21T12:21:52Z</published>
<link rel='alternate' type='text/html' href='https://git.stealer.net/cgit.cgi/user/sven/linux.git/commit/?id=31aae2beeb3d601d556b6a8c39085940ad1e9f42'/>
<id>urn:sha1:31aae2beeb3d601d556b6a8c39085940ad1e9f42</id>
<content type='text'>
Regulators may sometimes take longer to enable than the control operation
used to do so, either because the regulator has ramp rate control used to
limit inrush current or because the control operation is very fast (GPIO
being the most common example of this).  In order to ensure that consumers
do not rely on the regulator before it is enabled provide an enable_time()
operation and have the core delay for that time before returning to the
caller.

This is implemented as a function since the ramp rate may be specified in
voltage per unit time and therefore the time depend on the configuration.
In future it would be desirable to allow the bulk operations to run the
delays for multiple enables in parallel but this is not currently supported.

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