From: Stephen Boyd <swboyd@chromium.org>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Taniya Das <tdas@codeaurora.org>
Subject: [PATCH 0/2] Introduce a 'protected-clocks' property
Date: Mon, 5 Nov 2018 11:40:09 -0800 [thread overview]
Message-ID: <20181105194011.43770-1-swboyd@chromium.org> (raw)
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
next reply other threads:[~2018-11-05 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 19:40 Stephen Boyd [this message]
2018-11-05 19:40 ` [PATCH 1/2] dt-bindings: clk: Introduce 'protected-clocks' property Stephen Boyd
2018-11-06 1:04 ` Bjorn Andersson
2018-11-08 5:44 ` Bjorn Andersson
2018-11-08 18:11 ` Stephen Boyd
2018-11-21 9:00 ` Stephen Boyd
2018-11-05 19:40 ` [PATCH 2/2] clk: qcom: Support " Stephen Boyd
2018-11-06 1:05 ` Bjorn Andersson
2018-11-21 9:00 ` Stephen Boyd
2018-11-06 5:50 ` [PATCH] arm64: dts: qcom: sdm845-mtp: Mark protected gcc clocks Bjorn Andersson
2018-11-09 23:21 ` Andy Gross
2018-11-21 9:01 ` Stephen Boyd
2018-11-22 7:30 ` Bjorn Andersson
2018-11-28 6:33 ` Stephen Boyd
2018-11-21 9:07 ` Stephen Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181105194011.43770-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tdas@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).