lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 25 Apr 2019 08:17:39 -0700 From: Stephen Boyd <sboyd@...nel.org> To: Dmitry Osipenko <digetx@...il.com>, Jonathan Hunter <jonathanh@...dia.com>, Michael Turquette <mturquette@...libre.com>, Peter De Schrijver <pdeschrijver@...dia.com>, Prashant Gaikwad <pgaikwad@...dia.com>, Thierry Reding <thierry.reding@...il.com> Cc: linux-clk@...r.kernel.org, linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v1 2/2] clk: tegra124: Remove lock-enable bit from PLLM Quoting Dmitry Osipenko (2019-04-11 14:48:35) > According to the Tegra124 TRM documentation, PLLM_MISC2 register doesn't > have the lock-enable bit as well as any other PLLM-related register. Hence > PLLM re-locking can't be initiated by software. The incorrect bit setting > should have been harmless since that bit is undefined according to TRM. > > Tested-by: Steev Klimaszewski <steev@...i.org> > Signed-off-by: Dmitry Osipenko <digetx@...il.com> > --- Applied to clk-next
Powered by blists - more mailing lists