<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/include/power, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2019-06-11T08:42:48Z</updated>
<entry>
<title>regulator: bd71837: copy the bd71837 pmic driver from NXP imx u-boot</title>
<updated>2019-06-11T08:42:48Z</updated>
<author>
<name>Matti Vaittinen</name>
</author>
<published>2019-05-07T07:43:39Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=1023c8739b8cb907f75692a8bd1792a6cacca0fc'/>
<id>urn:sha1:1023c8739b8cb907f75692a8bd1792a6cacca0fc</id>
<content type='text'>
https://source.codeaurora.org/external/imx/uboot-imx

cherry picked, styled and merged commits:
- MLK-18387 pmic: Add pmic driver for BD71837: e9a3bec2e95a
- MLK-18590 pmic: bd71837: Change to use new fdt API: acdc5c297a96

Signed-off-by: Ye Li &lt;ye.li@nxp.com&gt;
Signed-off-by: Matti Vaittinen &lt;matti.vaittinen@fi.rohmeurope.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>stpmic1: add NVM update support in fuse command</title>
<updated>2019-04-12T14:09:13Z</updated>
<author>
<name>Patrick Delaunay</name>
</author>
<published>2019-02-04T10:26:22Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=31e45a1a9ea07a9c36ada6401e4631a765398c75'/>
<id>urn:sha1:31e45a1a9ea07a9c36ada6401e4631a765398c75</id>
<content type='text'>
Add functions to read/update the non volatile memory of STPMIC1
(8 bytes-register at 0xF8 address) and allow access
with fuse command (bank=1, word &gt; 0xF8).

For example:

STM32MP&gt; fuse read 1 0xf8 8
Reading bank 1:

Word 0x000000f8: 000000ee 00000092 000000c0 00000002
Word 0x000000fc: 000000f2 00000080 00000002 00000033

Signed-off-by: Patrick Delaunay &lt;patrick.delaunay@st.com&gt;
</content>
</entry>
<entry>
<title>stpmic1: update register names</title>
<updated>2019-04-12T14:09:13Z</updated>
<author>
<name>Patrick Delaunay</name>
</author>
<published>2019-02-04T10:26:18Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=db4ff0df656f8ca8d363df64cddc7b5f835a7ecc'/>
<id>urn:sha1:db4ff0df656f8ca8d363df64cddc7b5f835a7ecc</id>
<content type='text'>
Alignment with  STPMIC1 datasheet
  s/MAIN_CONTROL_REG/MAIN_CR/g
  s/MASK_RESET_BUCK/BUCKS_MRST_CR/g
  s/MASK_RESET_LDOS/LDOS_MRST_CR/g
  s/BUCKX_CTRL_REG/BUCKX_MAIN_CR/g
  s/VREF_CTRL_REG/REFDDR_MAIN_CR/g
  s/LDOX_CTRL_REG/LDOX_MAIN_CR/g
  s/USB_CTRL_REG/BST_SW_CR/g
  s/STPMIC1_NVM_USER_STATUS_REG/STPMIC1_NVM_SR/g
  s/STPMIC1_NVM_USER_CONTROL_REG/STPMIC1_NVM_CR/g
and update all the associated defines.

Signed-off-by: Patrick Delaunay &lt;patrick.delaunay@st.com&gt;
</content>
</entry>
<entry>
<title>power: rename stpmu1 to official name stpmic1</title>
<updated>2019-04-12T14:09:13Z</updated>
<author>
<name>Patrick Delaunay</name>
</author>
<published>2019-02-04T10:26:17Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=42f01aacfd508ddaab5fbc21dd1d3c04dcf61990'/>
<id>urn:sha1:42f01aacfd508ddaab5fbc21dd1d3c04dcf61990</id>
<content type='text'>
Alignment with kernel driver name &amp; binding
introduced by https://patchwork.kernel.org/cover/10761943/
to use the final marketing name = STPMIC1.

Signed-off-by: Patrick Delaunay &lt;patrick.delaunay@st.com&gt;
Reviewed-by: Lukasz Majewski &lt;lukma@denx.de&gt;
</content>
</entry>
<entry>
<title>power: stpmu1: rename files to stpmic1</title>
<updated>2019-04-12T14:09:13Z</updated>
<author>
<name>Patrick Delaunay</name>
</author>
<published>2019-02-04T10:26:16Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=d46c22b3fdb58623f1bf372d028313a5d3e7b79b'/>
<id>urn:sha1:d46c22b3fdb58623f1bf372d028313a5d3e7b79b</id>
<content type='text'>
Prepare file modification for kernel alignment and
rename driver to stpmic1.

Signed-off-by: Patrick Delaunay &lt;patrick.delaunay@st.com&gt;
Reviewed-by: Lukasz Majewski &lt;lukma@denx.de&gt;
</content>
</entry>
<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-03.infra.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-03.infra.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>power: make most tps drivers and the twl4030 driver compatible with DM_I2C</title>
<updated>2018-12-10T05:17:30Z</updated>
<author>
<name>Jean-Jacques Hiblot</name>
</author>
<published>2018-12-07T13:50:46Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=fb1b7712ad3f375f83e74629f03236c300b0b896'/>
<id>urn:sha1:fb1b7712ad3f375f83e74629f03236c300b0b896</id>
<content type='text'>
Those driver are not DM drivers per se (not using the PMIC/regulator
framework) and are using the legacy I2C API. Make them compatible with
the DM_I2C API.

This impacts the following drivers:
- palmas (used by am57xx/dra7xx evms)
- tps65218 (used by am43xx evms)
- tps65217 and tps65910 (used by am335x evms and am335x boneblack vboot)
- twl4030 (used by omap3_logicpd)
- tps65217 (used by brppt1)
- twl6030

Signed-off-by: Jean-Jacques Hiblot &lt;jjhiblot@ti.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Heiko Schocher &lt;hs@denx.de&gt;
</content>
</entry>
<entry>
<title>power: regulator: stpmu1: add power off delay</title>
<updated>2018-07-19T20:31:36Z</updated>
<author>
<name>Christophe Kerello</name>
</author>
<published>2018-06-27T09:59:47Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=844f9bf1eea75ff1ac1b1552ec4cac32ba829abb'/>
<id>urn:sha1:844f9bf1eea75ff1ac1b1552ec4cac32ba829abb</id>
<content type='text'>
This patch adds a delay when regulators are disabled.
This delay is set to 5 ms to cover all use cases.
The worst use case actually seen is during a SD card power cycle.

Signed-off-by: Christophe Kerello &lt;christophe.kerello@st.com&gt;
Signed-off-by: Patrice Chotard &lt;patrice.chotard@st.com&gt;
</content>
</entry>
<entry>
<title>power: pmic: Let PFUZE3000 see all 256 registers</title>
<updated>2018-06-27T07:47:46Z</updated>
<author>
<name>Trent Piepho</name>
</author>
<published>2018-04-25T17:06:00Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=7da7ff54914ca58a289bd8e0fda6e7240c545826'/>
<id>urn:sha1:7da7ff54914ca58a289bd8e0fda6e7240c545826</id>
<content type='text'>
The PFUZE3000 uses registers addresses up to 0xff.

The DM pfuze100 driver supports both pfuze100 and pfuze3000.  Allow it
to use the device type to return the correct number of registers.

Also rename the too generic PMIC_NUM_OF_REGS enumeration value for
pfuze3000 to match the other "PFUZE3000_" prefixed enumerations and the
pfuze100 enumeration value PFUZE100_NUM_OF_REGS.

Cc: Peng Fan &lt;Peng.Fan@freescale.com&gt;
Cc: Jaehoon Chung &lt;jh80.chung@samsung.com&gt;
Cc: Stefano Babic &lt;sbabic@denx.de&gt;
Cc: Fabio Estevam &lt;fabio.estevam@nxp.com&gt;
Signed-off-by: Trent Piepho &lt;tpiepho@impinj.com&gt;
Reviewed-by: Fabio Estevam &lt;fabio.estevam@nxp.com&gt;
</content>
</entry>
</feed>
