From: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
mturquette@baylibre.com, sboyd@kernel.org,
marc.w.gonzalez@free.fr, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Subject: [PATCH v4 0/2] MSM8998 GPUCC Support
Date: Tue, 1 Oct 2019 18:15:55 -0700 [thread overview]
Message-ID: <20191002011555.36571-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.
v4:
-rebase onto mmcc series
-remove clk_get from the clock provider
v3:
-drop accepted DT patch
-correct "avoid" typo
-expand comment on why XO is required
v2:
-drop dead code
Jeffrey Hugo (2):
clk: qcom: Add MSM8998 GPU Clock Controller (GPUCC) driver
arm64: dts: qcom: msm8998: Add gpucc node
arch/arm64/boot/dts/qcom/msm8998.dtsi | 14 ++
drivers/clk/qcom/Kconfig | 9 +
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/gpucc-msm8998.c | 346 ++++++++++++++++++++++++++
4 files changed, 370 insertions(+)
create mode 100644 drivers/clk/qcom/gpucc-msm8998.c
--
2.17.1
next reply other threads:[~2019-10-02 1:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 1:15 Jeffrey Hugo [this message]
2019-10-02 1:16 ` [PATCH v4 1/2] clk: qcom: Add MSM8998 GPU Clock Controller (GPUCC) driver Jeffrey Hugo
2019-10-17 21:50 ` Stephen Boyd
2019-10-17 23:16 ` Jeffrey Hugo
2019-10-18 21:11 ` Jeffrey Hugo
2019-10-27 21:36 ` Stephen Boyd
2019-10-28 14:17 ` Jeffrey Hugo
2019-10-18 4:11 ` Taniya Das
2019-10-18 14:24 ` Jeffrey Hugo
2019-10-02 1:17 ` [PATCH v4 2/2] 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=20191002011555.36571-1-jeffrey.l.hugo@gmail.com \
--to=jeffrey.l.hugo@gmail.com \
--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=marc.w.gonzalez@free.fr \
--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).