From: Sricharan R <sricharan@codeaurora.org>
To: agross@kernel.org, devicetree@vger.kernel.org,
linus.walleij@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-soc@vger.kernel.org, robh+dt@kernel.org,
sivaprak@codeaurora.org, sricharan@codeaurora.org,
sboyd@kernel.org
Subject: [PATCH V2 0/2] Add Global clock controller support for IPQ6018
Date: Thu, 9 Jan 2020 13:35:19 +0530 [thread overview]
Message-ID: <1578557121-423-1-git-send-email-sricharan@codeaurora.org> (raw)
The IPQ6018 is Qualcomm’s 802.11ax/u2019s SoC for Routers,
Gateways and Access Points.
[V2]
* Addressed sparse warnings reported by Kbuild test robot.
This series adds Global clock controller support for ipq6018.
Sricharan R (2):
clk: qcom: Add DT bindings for ipq6018 gcc clock controller
clk: qcom: Add ipq6018 Global Clock Controller support
.../devicetree/bindings/clock/qcom,gcc.yaml | 3 +-
drivers/clk/qcom/Kconfig | 8 +
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/gcc-ipq6018.c | 4643 ++++++++++++++++++++
include/dt-bindings/clock/qcom,gcc-ipq6018.h | 262 ++
include/dt-bindings/reset/qcom,gcc-ipq6018.h | 157 +
6 files changed, 5073 insertions(+), 1 deletion(-)
create mode 100644 drivers/clk/qcom/gcc-ipq6018.c
create mode 100644 include/dt-bindings/clock/qcom,gcc-ipq6018.h
create mode 100644 include/dt-bindings/reset/qcom,gcc-ipq6018.h
--
1.9.1
next reply other threads:[~2020-01-09 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 8:05 Sricharan R [this message]
2020-01-09 8:05 ` [PATCH V2 1/2] clk: qcom: Add DT bindings for ipq6018 gcc clock controller Sricharan R
2020-01-10 0:11 ` Stephen Boyd
[not found] ` <1578557121-423-3-git-send-email-sricharan@codeaurora.org>
2020-01-10 0:11 ` [PATCH V2 2/2] clk: qcom: Add ipq6018 Global Clock Controller 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=1578557121-423-1-git-send-email-sricharan@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sivaprak@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).