From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Mark Brown" <broonie@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Nikola Milosavljević" <mnidza@outlook.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Restore voltages before rebooting of NVIDIA Tegra SoCs
Date: Fri, 14 May 2021 23:32:51 +0200 [thread overview]
Message-ID: <20210514213251.GB1969@qmqm.qmqm.pl> (raw)
In-Reply-To: <20210510220526.11113-1-digetx@gmail.com>
On Tue, May 11, 2021 at 01:05:24AM +0300, Dmitry Osipenko wrote:
> 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.
Which tree does this series apply to?
Best Regards
Michał Mirosław
next prev parent reply other threads:[~2021-05-14 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 22:05 [PATCH v1 0/2] Restore voltages before rebooting of NVIDIA Tegra SoCs Dmitry Osipenko
2021-05-10 22:05 ` [PATCH v1 1/2] regulator: core: Add regulator_sync_voltage_rdev() Dmitry Osipenko
2021-05-11 10:18 ` Mark Brown
2021-05-10 22:05 ` [PATCH v1 2/2] soc/tegra: regulators: Bump voltages on system reboot Dmitry Osipenko
2021-05-14 21:32 ` Michał Mirosław [this message]
2021-05-14 22:18 ` [PATCH v1 0/2] Restore voltages before rebooting of NVIDIA Tegra SoCs Dmitry Osipenko
2021-05-16 21:32 ` 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=20210514213251.GB1969@qmqm.qmqm.pl \
--to=mirq-linux@rere.qmqm.pl \
--cc=broonie@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--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).