From: Rob Herring <robh@kernel.org>
To: Jeffrey Hugo <jhugo@codeaurora.org>
Cc: bjorn.andersson@linaro.org, mturquette@baylibre.com,
sboyd@kernel.org, marc.w.gonzalez@free.fr, andy.gross@linaro.org,
david.brown@linaro.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 v2 3/4] clk: qcom: Add MSM8998 Multimedia Clock Controller (MMCC) driver
Date: Mon, 18 Feb 2019 14:15:32 -0600 [thread overview]
Message-ID: <20190218201532.GA19638@bogus> (raw)
In-Reply-To: <1550377947-11414-1-git-send-email-jhugo@codeaurora.org>
On Sat, Feb 16, 2019 at 09:32:27PM -0700, Jeffrey Hugo wrote:
> Add a driver for the multimedia clock controller found on MSM8998
> based devices. This should allow most multimedia device drivers
> to probe and control their clocks.
>
> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
> ---
> drivers/clk/qcom/Kconfig | 9 +
> drivers/clk/qcom/Makefile | 1 +
> drivers/clk/qcom/mmcc-msm8998.c | 2915 +++++++++++++++++
> include/dt-bindings/clock/qcom,mmcc-msm8998.h | 210 ++
If you need to respin, this file goes in the binding patch.
> 4 files changed, 3135 insertions(+)
> create mode 100644 drivers/clk/qcom/mmcc-msm8998.c
> create mode 100644 include/dt-bindings/clock/qcom,mmcc-msm8998.h
next prev parent reply other threads:[~2019-02-18 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 4:31 [PATCH v2 0/4] MSM8998 Multimedia Clock Controller Jeffrey Hugo
2019-02-17 4:32 ` [PATCH v2 1/4] clk: qcom: smd: Add XO clock for MSM8998 Jeffrey Hugo
2019-02-17 4:32 ` [PATCH v2 2/4] dt-bindings: clock: Add support for the MSM8998 mmcc Jeffrey Hugo
2019-02-18 20:14 ` Rob Herring
2019-02-17 4:32 ` [PATCH v2 3/4] clk: qcom: Add MSM8998 Multimedia Clock Controller (MMCC) driver Jeffrey Hugo
2019-02-18 20:15 ` Rob Herring [this message]
2019-02-17 4:32 ` [PATCH v2 4/4] arm64: dts: qcom: msm8998: Add mmcc 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=20190218201532.GA19638@bogus \
--to=robh@kernel.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jhugo@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=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).