From: Fabio Estevam <festevam@denx.de>
To: Marek Vasut <marex@denx.de>
Cc: u-boot@lists.denx.de, "NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
Fabio Estevam <festevam@gmail.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Manoj Sai <abbaraju.manojsai@amarulasolutions.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Matteo Lisi <matteo.lisi@engicam.com>,
Peng Fan <peng.fan@nxp.com>,
Rickard x Andersson <rickaran@axis.com>,
Stefano Babic <sbabic@denx.de>,
Tim Harvey <tharvey@gateworks.com>
Subject: Re: [PATCH 1/2] pmic: pca9450: Make warm reset on WDOG_B assertion
Date: Sat, 10 Dec 2022 11:33:01 -0300 [thread overview]
Message-ID: <796313127c5fbef3146738002326fa82@denx.de> (raw)
In-Reply-To: <20221209193547.170768-1-marex@denx.de>
On 09/12/2022 16:35, Marek Vasut wrote:
> The default configuration of the PMIC behavior makes the PMIC
> power cycle most regulators on WDOG_B assertion. This power
> cycling causes the memory contents of OCRAM to be lost.
> Some systems neeeds some memory that survives reset and
> reboot, therefore this patch is created.
>
> The implementation is taken almost verbatim from Linux commit
> 2364a64d0673f ("regulator: pca9450: Make warm reset on WDOG_B
> assertion")
>
> Signed-off-by: Marek Vasut <marex@denx.de>
Reviewed-by: Fabio Estevam <festevam@denx.de>
next prev parent reply other threads:[~2022-12-10 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 19:35 [PATCH 1/2] pmic: pca9450: Make warm reset on WDOG_B assertion Marek Vasut
2022-12-09 19:35 ` [PATCH 2/2] ARM: imx: Remove PMIC reset configuration from board files Marek Vasut
2022-12-10 14:33 ` Fabio Estevam
2022-12-13 7:44 ` Peng Fan
2023-01-31 9:50 ` sbabic
2022-12-10 14:33 ` Fabio Estevam [this message]
2022-12-13 7:44 ` [PATCH 1/2] pmic: pca9450: Make warm reset on WDOG_B assertion Peng Fan
2023-01-31 9:50 ` sbabic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=796313127c5fbef3146738002326fa82@denx.de \
--to=festevam@denx.de \
--cc=abbaraju.manojsai@amarulasolutions.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=matteo.lisi@engicam.com \
--cc=paul.liu@linaro.org \
--cc=peng.fan@nxp.com \
--cc=rickaran@axis.com \
--cc=sbabic@denx.de \
--cc=tharvey@gateworks.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox