diff options
| author | Dmitry Osipenko <digetx@gmail.com> | 2021-05-16 19:30:35 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-07-20 16:17:43 +0200 |
| commit | af23af93e89c5d79d9d6e5992fc388d7c385d774 (patch) | |
| tree | 756c6cebb11858f0054e6ba850efd23ba5598c2a /net | |
| parent | d1401c2c8482962a41d41eb164efe6e5a7f95ffb (diff) | |
| download | linux-stable-af23af93e89c5d79d9d6e5992fc388d7c385d774.tar.gz linux-stable-af23af93e89c5d79d9d6e5992fc388d7c385d774.tar.bz2 linux-stable-af23af93e89c5d79d9d6e5992fc388d7c385d774.zip | |
clk: tegra: Ensure that PLLU configuration is applied properly
[ Upstream commit a7196048cd5168096c2c4f44a3939d7a6dcd06b9 ]
The PLLU (USB) consists of the PLL configuration itself and configuration
of the PLLU outputs. The PLLU programming is inconsistent on T30 vs T114,
where T114 immediately bails out if PLLU is enabled and T30 re-enables
a potentially already enabled PLL (left after bootloader) and then fully
reprograms it, which could be unsafe to do. The correct way should be to
skip enabling of the PLL if it's already enabled and then apply
configuration to the outputs. This patch doesn't fix any known problems,
it's a minor improvement.
Acked-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions