From: Dmitry Osipenko <digetx@gmail.com>
To: "Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Nikola Milosavljević" <mnidza@outlook.com>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: [PATCH v2 0/2] Restore voltages before rebooting of NVIDIA Tegra SoCs
Date: Mon, 17 May 2021 01:21:00 +0300 [thread overview]
Message-ID: <20210516222103.28595-1-digetx@gmail.com> (raw)
Hi,
Nikola Milosavljević reported that rebooting wasn't working properly on
Asus Transformer TF101, which is Tegra20-based tablet device. We found
that TF101 and some other devices have bootloader which doesn't re-initialize
voltages properly on a reboot. The problem is resolved by ensuring that
SoC voltages are at a levels that are suitable for the rebooting of the
SoC before reboot happens. This series adds reboot handler to the Tegra
regulator couplers, it bumps voltages on the reboot event.
Changelog:
v2: - Added ack from Mark Brown.
- Rebased patches properly, thanks to Michał Mirosław for noticing
this problem.
Dmitry Osipenko (2):
regulator: core: Add regulator_sync_voltage_rdev()
soc/tegra: regulators: Bump voltages on system reboot
drivers/regulator/core.c | 23 ++++++++
drivers/soc/tegra/regulators-tegra20.c | 75 ++++++++++++++++++++++++-
drivers/soc/tegra/regulators-tegra30.c | 78 +++++++++++++++++++++++++-
include/linux/regulator/driver.h | 1 +
4 files changed, 175 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2021-05-16 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 22:21 Dmitry Osipenko [this message]
2021-05-16 22:21 ` [PATCH v2 1/2] regulator: core: Add regulator_sync_voltage_rdev() Dmitry Osipenko
2021-05-16 22:21 ` [PATCH v2 2/2] soc/tegra: regulators: Bump voltages on system reboot Dmitry Osipenko
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=20210516222103.28595-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=mnidza@outlook.com \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).