From: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: agross@kernel.org, david.brown@linaro.org,
bjorn.andersson@linaro.org, mturquette@baylibre.com,
sboyd@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
marc.w.gonzalez@free.fr, jcrouse@codeaurora.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Subject: [PATCH 0/3] MSM8998 GPUCC Support
Date: Tue, 28 May 2019 09:46:16 -0700 [thread overview]
Message-ID: <20190528164616.38517-1-jeffrey.l.hugo@gmail.com> (raw)
The Adreno GPU on MSM8998 has its own clock controller, which is a
dependency for bringing up the GPU. This series gets the gpucc all in
place as another step on the road to getting the GPU enabled.
Jeffrey Hugo (3):
dt-bindings: clock: Document gpucc for msm8998
clk: qcom: Add MSM8998 GPU Clock Controller (GPUCC) driver
arm64: dts: qcom: msm8998: Add gpucc node
.../devicetree/bindings/clock/qcom,gpucc.txt | 4 +-
arch/arm64/boot/dts/qcom/msm8998.dtsi | 15 +
drivers/clk/qcom/Kconfig | 8 +
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/gpucc-msm8998.c | 364 ++++++++++++++++++
.../dt-bindings/clock/qcom,gpucc-msm8998.h | 29 ++
6 files changed, 420 insertions(+), 1 deletion(-)
create mode 100644 drivers/clk/qcom/gpucc-msm8998.c
create mode 100644 include/dt-bindings/clock/qcom,gpucc-msm8998.h
--
2.17.1
next reply other threads:[~2019-05-28 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 16:46 Jeffrey Hugo [this message]
2019-05-28 16:47 ` [PATCH 1/3] dt-bindings: clock: Document gpucc for msm8998 Jeffrey Hugo
2019-06-06 23:27 ` Stephen Boyd
2019-05-28 16:48 ` [PATCH 2/3] clk: qcom: Add MSM8998 GPU Clock Controller (GPUCC) driver Jeffrey Hugo
2019-06-06 23:00 ` Stephen Boyd
2019-06-07 14:08 ` Jeffrey Hugo
2019-06-07 20:32 ` Stephen Boyd
2019-06-07 21:34 ` Jeffrey Hugo
2019-05-28 16:48 ` [PATCH 3/3] arm64: dts: qcom: msm8998: Add gpucc node Jeffrey Hugo
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=20190528164616.38517-1-jeffrey.l.hugo@gmail.com \
--to=jeffrey.l.hugo@gmail.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jcrouse@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@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).