From: Jeffrey Hugo <jhugo@codeaurora.org>
To: sboyd@kernel.org
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
marc.w.gonzalez@free.fr, mturquette@baylibre.com,
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
Subject: Re: [PATCH v5 0/6] MSM8998 Multimedia Clock Controller
Date: Wed, 19 Jun 2019 09:45:44 -0600 [thread overview]
Message-ID: <f151d380-4ac5-cb1a-4244-9e4e8e2134d8@codeaurora.org> (raw)
In-Reply-To: <1560366600-5826-1-git-send-email-jhugo@codeaurora.org>
On 6/12/2019 1:10 PM, Jeffrey Hugo wrote:
> The multimedia clock controller (mmcc) is the main clock controller for
> the multimedia subsystem and is required to enable things like display and
> camera.
>
> v5:
> -handle the case where gcc uses rpmcc for xo, but the link is not specified in dt
> -have gcc select rpmcc
>
> v4:
> -fix makefile to use correct config item
> -pick up tags
> -fix ordering of clocks and clock-names in dt
> -drop MODULE_ALIAS
> -wait for xo in mmcc since that was found to be useful in some debug configs
>
> v3:
> -Rebase onto linux-next to get the final version of the clk parent rewrite
> series
> -Moved the bindings header to the bindings patch per Rob
> -Made xo manditory for GCC to work around the lack of clk orphan probe defer
> to avoid the uart console glitch
>
> v2:
> -Rebased on the "Rewrite clk parent handling" series and updated to the clk init
> mechanisms introduced there.
> -Marked XO clk as CLK_IGNORE_UNUSED to avoid the concern about the XO going away
> "incorrectly" during late init
> -Corrected the name of the XO clock to "xo"
> -Dropped the fake XO clock in GCC to prevent a namespace conflict
> -Fully enumerated the external clocks (DSI PLLs, etc) in the DT binding
> -Cleaned up the weird newlines in the added DT node
> -Added DT header file to msm8998 DT for future clients
>
> Jeffrey Hugo (6):
> dt-bindings: clock: Document external clocks for MSM8998 gcc
> arm64: dts: msm8998: Add xo clock to gcc node
> 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,gcc.txt | 10 +
> .../devicetree/bindings/clock/qcom,mmcc.txt | 21 +
> arch/arm64/boot/dts/qcom/msm8998.dtsi | 16 +
> drivers/clk/qcom/Kconfig | 9 +
> drivers/clk/qcom/Makefile | 1 +
> drivers/clk/qcom/clk-smd-rpm.c | 24 +-
> drivers/clk/qcom/gcc-msm8998.c | 29 +-
> drivers/clk/qcom/mmcc-msm8998.c | 2915 +++++++++++++++++
> include/dt-bindings/clock/qcom,mmcc-msm8998.h | 210 ++
> 9 files changed, 3214 insertions(+), 21 deletions(-)
> create mode 100644 drivers/clk/qcom/mmcc-msm8998.c
> create mode 100644 include/dt-bindings/clock/qcom,mmcc-msm8998.h
>
Stephen, is there any chance for this series to make 5.3?
--
Jeffrey Hugo
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.
prev parent reply other threads:[~2019-06-19 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 19:10 [PATCH v5 0/6] MSM8998 Multimedia Clock Controller Jeffrey Hugo
2019-06-12 19:10 ` Jeffrey Hugo
2019-06-12 19:10 ` [PATCH v5 1/6] dt-bindings: clock: Document external clocks for MSM8998 gcc Jeffrey Hugo
2019-06-13 17:56 ` Rob Herring
2019-06-13 17:56 ` Rob Herring
2019-06-12 19:11 ` [PATCH v5 2/6] arm64: dts: msm8998: Add xo clock to gcc node Jeffrey Hugo
2019-06-12 19:12 ` [PATCH v5 3/6] clk: qcom: smd: Add XO clock for MSM8998 Jeffrey Hugo
2019-06-12 19:12 ` [PATCH v5 4/6] dt-bindings: clock: Add support for the MSM8998 mmcc Jeffrey Hugo
2019-06-12 19:12 ` [PATCH v5 5/6] clk: qcom: Add MSM8998 Multimedia Clock Controller (MMCC) driver Jeffrey Hugo
2019-06-12 19:13 ` [PATCH v5 6/6] arm64: dts: qcom: msm8998: Add mmcc node Jeffrey Hugo
2019-06-19 15:45 ` Jeffrey Hugo [this message]
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=f151d380-4ac5-cb1a-4244-9e4e8e2134d8@codeaurora.org \
--to=jhugo@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.