From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <kholk11@gmail.com>
Cc: Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-soc@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: Add MSM8976/56 Global Clock Controller (GCC) driver
Date: Mon, 21 Jan 2019 18:28:39 -0600 [thread overview]
Message-ID: <20190122002839.GA22319@bogus> (raw)
In-Reply-To: <65fb363366f651e42d3e97792d5990185823cbc3.camel@gmail.com>
On Sat, Jan 12, 2019 at 04:03:18PM +0100, AngeloGioacchino Del Regno wrote:
> From 50465f2a4454625aac622bb84dbecdeaf5a50904 Mon Sep 17 00:00:00 2001
> From: "Angelo G. Del Regno" <kholk11@gmail.com>
> Date: Sat, 12 Jan 2019 10:52:18 +0100
> Subject: [PATCH] clk: qcom: Add MSM8976/56 Global Clock Controller (GCC)
> driver
Looks like your patch is corrupted.
>
> Add support for the global clock controller found on MSM8976
> and MSM8976 SoCs.
> Since the multimedia clocks are actually in the GCC on these
> SoCs, this will allow drivers to probe and control basically
> all the required clocks.
>
> Signed-off-by: Angelo G. Del Regno <kholk11@gmail.com>
> ---
> .../devicetree/bindings/clock/qcom,gcc.txt | 1 +
> drivers/clk/qcom/Kconfig | 8 +
> drivers/clk/qcom/Makefile | 1 +
> drivers/clk/qcom/gcc-msm8976.c | 4208 +++++++++++++++++
> include/dt-bindings/clock/qcom,gcc-msm8976.h | 293 ++
The binding doc and this header should be in a separate patch.
> 5 files changed, 4511 insertions(+)
> create mode 100644 drivers/clk/qcom/gcc-msm8976.c
> create mode 100644 include/dt-bindings/clock/qcom,gcc-msm8976.h
next prev parent reply other threads:[~2019-01-22 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 15:03 [PATCH] clk: qcom: Add MSM8976/56 Global Clock Controller (GCC) driver AngeloGioacchino Del Regno
2019-01-12 15:03 ` AngeloGioacchino Del Regno
2019-01-22 0:28 ` Rob Herring [this message]
2019-01-24 19:22 ` Stephen Boyd
2019-01-24 19:22 ` Stephen Boyd
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=20190122002839.GA22319@bogus \
--to=robh@kernel.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kholk11@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--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 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.