summaryrefslogtreecommitdiff
path: root/include/dt-bindings/reset
diff options
context:
space:
mode:
authorPeter De Schrijver <pdeschrijver@nvidia.com>2017-03-14 17:12:49 +0300
committerThierry Reding <treding@nvidia.com>2017-03-20 16:18:30 +0300
commite745f992cf4b030ef73c5cdceecd03d9d3c727e9 (patch)
treec5dd92a5d9b729ef8f255430648af5a703f4ec75 /include/dt-bindings/reset
parent4236e752f19d4dae372336859a18ca8a5bed9374 (diff)
downloadlinux-e745f992cf4b030ef73c5cdceecd03d9d3c727e9.tar.xz
clk: tegra: Rework pll_u
In normal operation pll_u is under hardware control and has a fixed rate of 480MHz. Hardware will turn on pll_u on whenever any of the XUSB powerdomains is on. From a software point of view we model this is if pll_u is always on using a fixed rate clock. However the bootloader might or might not have configured pll_u this way. So we will check the current state of pll_u at boot and reconfigure it if required. There are 3 possiblities at kernel boot: 1) pll_u is under hardware control: do nothing 2) pll_u is under hardware control and enabled: enable hardware control 3) pll_u is disabled: enable pll_u and enable hardware control In all cases we also check if UTMIPLL is under hardware control at boot and configure it for hardware control if that is not the case. The same is done during SC7 resume. Thanks to Joseph Lo <josephl@nvidia.com> for bug fixes. Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com> Signed-off-by: Thierry Reding <treding@nvidia.com>
Diffstat (limited to 'include/dt-bindings/reset')
0 files changed, 0 insertions, 0 deletions