lkml.org 
[lkml]   [2018]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH 0/2] Introduce a 'protected-clocks' property
Date
See full explanation in patch #1. It looks like on qcom platforms
we're increasing the number of situations where we need to have
a set of clks that aren't touched by the OS because firmware
wants them for itself. This series introduces a method to do that
by specifying in DT what clks shouldn't be read or written and
then having the qcom clk driver neve register the ones that
are protected.

Cc: Rob Herring <robh+dt@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Taniya Das <tdas@codeaurora.org>

Stephen Boyd (2):
dt-bindings: clk: Introduce 'protected-clocks' property
clk: qcom: Support 'protected-clocks' property

.../bindings/clock/clock-bindings.txt | 16 ++++++++++++++++
drivers/clk/qcom/common.c | 18 ++++++++++++++++++
2 files changed, 34 insertions(+)

--
Sent by a computer through tubes

\
 
 \ /
  Last update: 2018-11-05 20:41    [W:0.236 / U:0.116 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site