<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/drivers/power/regulator/regulator-uclass.c, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2019-03-11T06:53:19Z</updated>
<entry>
<title>regulator: Add support for ramp delay</title>
<updated>2019-03-11T06:53:19Z</updated>
<author>
<name>Krzysztof Kozlowski</name>
</author>
<published>2019-03-06T18:37:54Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=e66d1cb3c2344ee5bbf2059e75fa94350aea9f5f'/>
<id>urn:sha1:e66d1cb3c2344ee5bbf2059e75fa94350aea9f5f</id>
<content type='text'>
Changing voltage and enabling regulator might require delays so the
regulator stabilizes at expected level.

Add support for "regulator-ramp-delay" binding which can introduce
required time to both enabling the regulator and to changing the
voltage.

Signed-off-by: Krzysztof Kozlowski &lt;krzk@kernel.org&gt;
Tested-by: Anand Moon &lt;linux.amoon@gmail.com&gt;
Signed-off-by: Minkyu Kang &lt;mk7.kang@samsung.com&gt;
</content>
</entry>
<entry>
<title>power: regulator: Introduce regulator_set_enable_if_allowed api</title>
<updated>2019-02-09T19:50:22Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2019-01-11T09:45:51Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=cc4a224af226b2ea818d32af26742aaad8a3983e'/>
<id>urn:sha1:cc4a224af226b2ea818d32af26742aaad8a3983e</id>
<content type='text'>
regulator_set_enable() api throws an error in the following three cases:
- when requested to disable an always-on regulator
- when set_enable() ops not provided by regulator driver
- when enabling is actually failed.(Error returned by the regulator driver)

Sometimes consumer drivers doesn't want to track the first two scenarios
and just need to worry about the case where enabling is actually failed.
But it is also a good practice to have an error value returned in the
first two cases.

So introduce an api regulator_set_enable_if_allowed() which ignores the
first two error cases and returns an error as given by regulator driver.
Consumer drivers can use this api need not worry about the first two
error conditions.

Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>Revert "power: regulator: Return success on attempt to disable an always-on regulator"</title>
<updated>2019-02-09T19:50:22Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2019-01-11T09:45:50Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=f93fab312615ce0bc9aac33f9dcd876a3fed1290'/>
<id>urn:sha1:f93fab312615ce0bc9aac33f9dcd876a3fed1290</id>
<content type='text'>
This reverts commit e17e0ceb83538c015a50b965547f2f4d38f81c5d.

It is advised to return an error when trying to disable an always-on
regulator and let the consumer driver handle the error if needed.

Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>power: regulator: Return success on attempt to disable an always-on regulator</title>
<updated>2018-12-27T12:48:31Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2018-12-24T11:07:41Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=e17e0ceb83538c015a50b965547f2f4d38f81c5d'/>
<id>urn:sha1:e17e0ceb83538c015a50b965547f2f4d38f81c5d</id>
<content type='text'>
commit 4f86a724e82c0 ("power: regulator: denied disable on always-on
regulator") throws an error when requested to disable an always-on
regulator. It is right that an always-on regulator should not be
attempted to be disabled. But at the same time regulator framework
should not return an error when such request is received. Instead
it should just return success without attempting to disable the
specified regulator. This is because the requesting driver will
not have the idea if the regulator is always-on or not. The
requesting driver will always try to enable/disable regulator as
per the required flow. So it is upto regulator framework to not
break such scenarios.

Fixes: 4f86a724e82c0 ("power: regulator: denied disable on always-on regulator")
Reported-by: Jean-Jacques Hiblot &lt;jjhiblot@ti.com&gt;
Reviewed-by: Faiz Abbas &lt;faiz_abbas@ti.com&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>power: regulator: denied disable on always-on regulator</title>
<updated>2018-12-05T13:06:44Z</updated>
<author>
<name>Patrick Delaunay</name>
</author>
<published>2018-11-15T12:45:31Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=4f86a724e82c0b74d9ffb7b65f8ae4b011dd0b03'/>
<id>urn:sha1:4f86a724e82c0b74d9ffb7b65f8ae4b011dd0b03</id>
<content type='text'>
Don't disable regulator which are tagged as "regulator-always-on" in DT.

Signed-off-by: Patrick Delaunay &lt;patrick.delaunay@st.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Jack Mitchell &lt;jack@embed.me.uk&gt;
Tested-by: Jack Mitchell &lt;jack@embed.me.uk&gt;
Signed-off-by: Patrice Chotard &lt;patrice.chotard@st.com&gt;
Reviewed-by: Richard Röjfors &lt;richard@puffinpack.se&gt;
Tested-by: Richard Röjfors &lt;richard@puffinpack.se&gt;
Reviewed-by: Felix Brack &lt;fb@ltec.ch&gt;
Tested-by: Felix Brack &lt;fb@ltec.ch&gt;
</content>
</entry>
<entry>
<title>SPDX: Convert all of our single license tags to Linux Kernel style</title>
<updated>2018-05-07T13:34:12Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-05-06T21:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=83d290c56fab2d38cd1ab4c4cc7099559c1d5046'/>
<id>urn:sha1:83d290c56fab2d38cd1ab4c4cc7099559c1d5046</id>
<content type='text'>
When U-Boot started using SPDX tags we were among the early adopters and
there weren't a lot of other examples to borrow from.  So we picked the
area of the file that usually had a full license text and replaced it
with an appropriate SPDX-License-Identifier: entry.  Since then, the
Linux Kernel has adopted SPDX tags and they place it as the very first
line in a file (except where shebangs are used, then it's second line)
and with slightly different comment styles than us.

In part due to community overlap, in part due to better tag visibility
and in part for other minor reasons, switch over to that style.

This commit changes all instances where we have a single declared
license in the tag as both the before and after are identical in tag
contents.  There's also a few places where I found we did not have a tag
and have introduced one.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>Remove unnecessary instances of DECLARE_GLOBAL_DATA_PTR</title>
<updated>2018-04-27T18:54:48Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-04-18T17:50:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=d024236e5a31a2b4b82cbcc98b31b8170fc88d28'/>
<id>urn:sha1:d024236e5a31a2b4b82cbcc98b31b8170fc88d28</id>
<content type='text'>
We have a large number of places where while we historically referenced
gd in the code we no longer do, as well as cases where the code added
that line "just in case" during development and never dropped it.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>regulator: Change get_enable return type to integer from bool</title>
<updated>2017-07-19T10:13:59Z</updated>
<author>
<name>Keerthy</name>
</author>
<published>2017-06-13T04:23:45Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=06bdf6003b6951154bf1d0876fc7174c53df766c'/>
<id>urn:sha1:06bdf6003b6951154bf1d0876fc7174c53df766c</id>
<content type='text'>
Change get_enable return type to int so errors can be returned.

Signed-off-by: Keerthy &lt;j-keerthy@ti.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>power: regulator: Add more debugging and fix a missing newline</title>
<updated>2017-06-09T19:39:32Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2017-05-31T23:57:15Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=422f04b68f59a8348428a6a5628a00a5689d0168'/>
<id>urn:sha1:422f04b68f59a8348428a6a5628a00a5689d0168</id>
<content type='text'>
This file does not report a few possible errors and one message is missing
a newline. Fix these.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Jaehoon Chung &lt;jh80.chung@samsung.com&gt;
</content>
</entry>
<entry>
<title>dm: regulator: Convert regulator uclass to support livetree</title>
<updated>2017-06-01T13:03:13Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2017-05-19T02:09:34Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=f15cd4f131d1a705e053e975688043b109b67e97'/>
<id>urn:sha1:f15cd4f131d1a705e053e975688043b109b67e97</id>
<content type='text'>
Update the regulator uclass to support a live device tree.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
