From: Jeffrey Hugo <jhugo@codeaurora.org>
To: unlisted-recipients:; (no To-header on input)
Cc: bjorn.andersson@linaro.org, marc.w.gonzalez@free.fr,
andy.gross@linaro.org, david.brown@linaro.org,
mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Jeffrey Hugo <jhugo@codeaurora.org>
Subject: [PATCH v1 0/4] MSM8998 Multimedia Clock Controller
Date: Wed, 30 Jan 2019 09:35:02 -0700 [thread overview]
Message-ID: <1548866102-30224-1-git-send-email-jhugo@codeaurora.org> (raw)
The multimedia clock controller (mmcc) is the main clock controller for
the multimedia subsystem and is required to enable things like display and
camera.
The mmcc consumes a few external clocks inorder to configure the root clock
generators that it controls. We can use DT to grab XO (from rpmcc) and
gpll0 (from gcc), but we'll have to rely on the global namespace to consume
the plls from elsewhere in the mmss.
Jeffrey Hugo (4):
clk: qcom: smd: Add XO clock for MSM8998
dt-bindings: clock: Add support for the MSM8998 mmcc
clk: qcom: Add MSM8998 Multimedia Clock Controller (MMCC) driver
arm64: dts: qcom: msm8998: Add mmcc node
.../devicetree/bindings/clock/qcom,mmcc.txt | 7 +
arch/arm64/boot/dts/qcom/msm8998.dtsi | 15 +
drivers/clk/qcom/Kconfig | 9 +
drivers/clk/qcom/Makefile | 1 +
drivers/clk/qcom/clk-smd-rpm.c | 4 +
drivers/clk/qcom/mmcc-msm8998.c | 2937 ++++++++++++++++++++
include/dt-bindings/clock/qcom,mmcc-msm8998.h | 210 ++
7 files changed, 3183 insertions(+)
create mode 100644 drivers/clk/qcom/mmcc-msm8998.c
create mode 100644 include/dt-bindings/clock/qcom,mmcc-msm8998.h
--
Qualcomm Datacenter Technologies as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next reply other threads:[~2019-01-30 16:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 16:35 Jeffrey Hugo [this message]
2019-01-30 16:35 ` [PATCH v1 1/4] clk: qcom: smd: Add XO clock for MSM8998 Jeffrey Hugo
2019-02-05 22:01 ` Stephen Boyd
2019-02-05 22:15 ` Jeffrey Hugo
2019-02-05 22:32 ` Stephen Boyd
2019-02-05 22:37 ` Jeffrey Hugo
2019-02-06 13:55 ` Georgi Djakov
2019-02-06 17:04 ` Jeffrey Hugo
2019-01-30 16:35 ` [PATCH v1 2/4] dt-bindings: clock: Add support for the MSM8998 mmcc Jeffrey Hugo
2019-02-05 22:02 ` Stephen Boyd
2019-02-05 22:08 ` Jeffrey Hugo
2019-02-05 22:16 ` Stephen Boyd
2019-02-05 22:36 ` Jeffrey Hugo
2019-01-30 16:36 ` [PATCH v1 3/4] clk: qcom: Add MSM8998 Multimedia Clock Controller (MMCC) driver Jeffrey Hugo
2019-02-05 22:06 ` Stephen Boyd
2019-02-05 22:12 ` Jeffrey Hugo
2019-02-05 22:16 ` Stephen Boyd
2019-01-30 16:36 ` [PATCH v1 4/4] arm64: dts: qcom: msm8998: Add mmcc node Jeffrey Hugo
2019-02-05 22:03 ` Stephen Boyd
2019-02-05 22:10 ` 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=1548866102-30224-1-git-send-email-jhugo@codeaurora.org \
--to=jhugo@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.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=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).