linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <andy.gross@linaro.org>,
	AngeloGioacchino Del Regno <kholk11@gmail.com>,
	David Brown <david.brown@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>
Cc: AngeloGioacchino Del Regno <kholk11@gmail.com>,
	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: Thu, 24 Jan 2019 11:22:55 -0800	[thread overview]
Message-ID: <154835777525.136743.6424256006615217720@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <65fb363366f651e42d3e97792d5990185823cbc3.camel@gmail.com>

Quoting AngeloGioacchino Del Regno (2019-01-12 07:03:18)
> 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
> 
> 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>

Are you going to send out DTS bits and provide platform support? I'm not
interested in merging the clk bits and then having to support a driver
that never gets used.

Also, is this copy/pasted from some downstream kernel sources? Would be
good to have a pointer to that so we can compare and see if you've
changed anything.


      parent reply	other threads:[~2019-01-24 20:17 UTC|newest]

Thread overview: 3+ 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-22  0:28 ` Rob Herring
2019-01-24 19:22 ` Stephen Boyd [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=154835777525.136743.6424256006615217720@swboyd.mtv.corp.google.com \
    --to=sboyd@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 \
    /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).