From: Samuel Holland <samuel@sholland.org>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Maxime Ripard <mripard@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Samuel Holland <samuel@sholland.org>
Subject: [PATCH RESEND 0/2] Common protected-clocks implementation
Date: Wed, 2 Sep 2020 23:00:13 -0500 [thread overview]
Message-ID: <20200903040015.5627-1-samuel@sholland.org> (raw)
Stephen, Maxime,
You previously asked me to implement the protected-clocks property in a
driver-independent way:
https://www.spinics.net/lists/arm-kernel/msg753832.html
I provided an implementation 6 months ago, which I am resending now:
https://patchwork.kernel.org/patch/11398629/
Do you have any comments on it?
Thanks,
Samuel
Samuel Holland (2):
clk: Implement protected-clocks for all OF clock providers
Revert "clk: qcom: Support 'protected-clocks' property"
drivers/clk/clk-conf.c | 54 +++++++++++++++++++++++++++++++++++++++
drivers/clk/clk.c | 31 ++++++++++++++++++++++
drivers/clk/clk.h | 2 ++
drivers/clk/qcom/common.c | 18 -------------
4 files changed, 87 insertions(+), 18 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-03 4:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 4:00 Samuel Holland [this message]
2020-09-03 4:00 ` [PATCH RESEND 1/2] clk: Implement protected-clocks for all OF clock providers Samuel Holland
2020-09-03 7:31 ` Maxime Ripard
2020-09-03 4:00 ` [PATCH RESEND 2/2] Revert "clk: qcom: Support 'protected-clocks' property" Samuel Holland
2021-03-09 8:03 ` [PATCH RESEND 0/2] Common protected-clocks implementation Rasmus Villemoes
2021-03-10 8:56 ` Maxime Ripard
2021-03-10 14:12 ` Samuel Holland
2021-03-10 20:13 ` Bjorn Andersson
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=20200903040015.5627-1-samuel@sholland.org \
--to=samuel@sholland.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.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).