Quoting Stephen Boyd (2018-11-05 11:40:11) > Certain firmware configurations "protect" clks and cause the entire > system to reboot when a non-secure OS such as Linux tries to read or > write protected clk registers. But other firmware configurations allow > reading or writing the same registers, and they may actually require > that the OS use the otherwise locked down clks. Support the > 'protected-clocks' property by never registering these protected clks > with the common clk framework. This way, when firmware is protecting > these clks we won't have the chance to ever read or write these > registers and take down the entire system. > > Cc: Taniya Das <t...@codeaurora.org> > Cc: Bjorn Andersson <bjorn.anders...@linaro.org> > Signed-off-by: Stephen Boyd <swb...@chromium.org> > ---
Applied to clk-next
