From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: a.zummo@towertech.it, Philipp Rosenberger <p.rosenberger@kunbus.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
dan.carpenter@oracle.com, bruno.thomsen@gmail.com,
u.kleine-koenig@pengutronix.de, biwen.li@nxp.com,
linux-kernel@vger.kernel.org, l.sanfilippo@kunbus.com,
linux-rtc@vger.kernel.org, lvb@xiphos.com
Subject: Re: [PATCH v3 0/2] rtc: pcf2127: proper initialization after power loss
Date: Tue, 26 Jan 2021 00:28:21 +0100 [thread overview]
Message-ID: <161161723905.1969074.4659584824562876901.b4-ty@bootlin.com> (raw)
In-Reply-To: <20210118085752.5759-1-p.rosenberger@kunbus.com>
On Mon, 18 Jan 2021 09:57:50 +0100, Philipp Rosenberger wrote:
> If the PCF2127/2129 loses power it needs some initialization to work
> correctly. A bootloader/firmware might do this. If not we should do this
> in the driver.
>
> Changes for v3:
> - drop the test if clearing PORO was successful
> - only run OTP refresh if OTPR bit is not already set
>
> [...]
Applied, thanks!
[1/2] rtc: pcf2127: Disable Power-On Reset Override
commit: b9ac079abefc1f1cbee8a0f7195bad1d32dc72c7
[2/2] rtc: pcf2127: Run a OTP refresh if not done before
commit: 15f57b3e3130790b6d06ea04f0c1edf0e5455bdd
Best regards,
--
Alexandre Belloni <alexandre.belloni@bootlin.com>
prev parent reply other threads:[~2021-01-25 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 8:57 [PATCH v3 0/2] rtc: pcf2127: proper initialization after power loss Philipp Rosenberger
2021-01-18 8:57 ` [PATCH v3 1/2] rtc: pcf2127: Disable Power-On Reset Override Philipp Rosenberger
2021-01-18 9:27 ` Uwe Kleine-König
2021-01-18 8:57 ` [PATCH v3 2/2] rtc: pcf2127: Run a OTP refresh if not done before Philipp Rosenberger
2021-01-25 23:28 ` Alexandre Belloni [this message]
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=161161723905.1969074.4659584824562876901.b4-ty@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=biwen.li@nxp.com \
--cc=bruno.thomsen@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=lvb@xiphos.com \
--cc=p.rosenberger@kunbus.com \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).