From: Taniya Das <tdas@codeaurora.org>
To: "Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette " <mturquette@baylibre.com>
Cc: David Brown <david.brown@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Gross <agross@kernel.org>,
devicetree@vger.kernel.org, robh@kernel.org, robh+dt@kernel.org,
Taniya Das <tdas@codeaurora.org>
Subject: [PATCH v1 0/3] Add GCC clock driver support
Date: Mon, 16 Mar 2020 16:24:39 +0530 [thread overview]
Message-ID: <1584356082-26769-1-git-send-email-tdas@codeaurora.org> (raw)
[v1]
* Add a new frequency of 51.2MHz for QUP clock.
* Add support for gcc_sec_ctrl_clk_src RCG for client to be able to request
various frequencies.
Taniya Das (3):
clk: qcom: gcc: Add support for a new frequency for SC7180
dt-bindings: clock: Add gcc_sec_ctrl_clk_src clock ID
clk: qcom: gcc: Add support for Secure control source clock
drivers/clk/qcom/gcc-sc7180.c | 94 ++++++++++++++++++-----------
include/dt-bindings/clock/qcom,gcc-sc7180.h | 1 +
2 files changed, 59 insertions(+), 36 deletions(-)
--
Qualcomm INDIA, on behalf of Qualcomm Innovation Center, Inc.is a member
of the Code Aurora Forum, hosted by the Linux Foundation.
next reply other threads:[~2020-03-16 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 10:54 Taniya Das [this message]
2020-03-16 10:54 ` [PATCH v1 1/3] clk: qcom: gcc: Add support for a new frequency for SC7180 Taniya Das
2020-03-16 17:49 ` Stephen Boyd
2020-05-17 10:01 ` Taniya Das
2020-03-16 10:54 ` [PATCH v1 2/3] dt-bindings: clock: Add gcc_sec_ctrl_clk_src clock ID Taniya Das
2020-03-16 10:54 ` [PATCH v1 3/3] clk: qcom: gcc: Add support for Secure control source clock Taniya Das
2020-03-16 17:49 ` Stephen Boyd
2020-05-17 10:02 ` Taniya Das
2020-03-16 17:06 ` [PATCH v1 0/3] Add GCC clock driver support 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=1584356082-26769-1-git-send-email-tdas@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=agross@kernel.org \
--cc=david.brown@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=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.