From: Taniya Das <tdas@codeaurora.org>
To: "Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette " <mturquette@baylibre.com>
Cc: 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,
devicetree@vger.kernel.org, robh@kernel.org, robh+dt@kernel.org,
Taniya Das <tdas@codeaurora.org>
Subject: [PATCH v1 0/2] Add Global Clock controller (GCC) driver for SC7280
Date: Wed, 16 Dec 2020 00:18:32 +0530 [thread overview]
Message-ID: <1608058114-29025-1-git-send-email-tdas@codeaurora.org> (raw)
Add driver support for Global Clock controller for SC7280 and also update
device tree bindings for the various clocks supported in the clock controller.
Taniya Das (2):
dt-bindings: clock: Add SC7280 GCC clock binding
clk: qcom: Add Global Clock controller (GCC) driver for SC7280
.../devicetree/bindings/clock/qcom,gcc-sc7280.yaml | 85 +
drivers/clk/qcom/Kconfig | 9 +
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/gcc-sc7280.c | 3361 ++++++++++++++++++++
include/dt-bindings/clock/qcom,gcc-sc7280.h | 215 ++
5 files changed, 3671 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/qcom,gcc-sc7280.yaml
create mode 100644 drivers/clk/qcom/gcc-sc7280.c
create mode 100644 include/dt-bindings/clock/qcom,gcc-sc7280.h
--
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-12-15 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 18:48 Taniya Das [this message]
2020-12-15 18:48 ` [PATCH v1 1/2] dt-bindings: clock: Add SC7280 GCC clock binding Taniya Das
2020-12-21 19:00 ` Rob Herring
2021-02-10 18:21 ` Taniya Das
2021-01-12 20:06 ` Stephen Boyd
2021-02-10 18:22 ` Taniya Das
2020-12-15 18:48 ` [PATCH v1 2/2] clk: qcom: Add Global Clock controller (GCC) driver for SC7280 Taniya Das
2021-01-12 20:04 ` Stephen Boyd
2021-02-10 18:24 ` Taniya Das
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=1608058114-29025-1-git-send-email-tdas@codeaurora.org \
--to=tdas@codeaurora.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 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).