linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Georgi Djakov <georgi.djakov@linaro.org>
To: sboyd@codeaurora.org
Cc: Georgi Djakov <georgi.djakov@linaro.org>,
	mturquette@baylibre.com, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add initial support for RPM clocks
Date: Wed, 02 Sep 2015 19:54:13 +0300	[thread overview]
Message-ID: <55E729B5.3020908@linaro.org> (raw)
In-Reply-To: <1438620489-32515-1-git-send-email-georgi.djakov@linaro.org>

On 08/03/2015 07:48 PM, Georgi Djakov wrote:
> This patchset adds initial support for the clocks controlled by
> the RPM (Resource Power Manager) processor on Qualcomm platforms.
> It depends on Bjorn's Qualcomm SMD & RPM patches, that are now in
> linux-next: https://lkml.org/lkml/2015/7/27/1125
> 
> The first patch implements the RPM clock operations, which are
> using a shared memory for sending requests to the RPM processor.
> The second patch adds the support of RPM clocks on the MSM8916
> platform.
> 
> Changes since v1 (https://lkml.org/lkml/2015/7/9/257):
> * Changed the driver name to clk-smd-rpm, also build it only
>   when it is needed - suggested by Srini and Bjorn.
> * More detailed binding example.
> * Minor changes.
> 
> Georgi Djakov (2):
>   clk: qcom: Add support for RPM Clocks
>   clk: qcom: Add MSM8916 RPM clock driver
> 
>  .../devicetree/bindings/clock/qcom,rpmcc.txt       |   35 ++++
>  drivers/clk/qcom/Kconfig                           |    4 +
>  drivers/clk/qcom/Makefile                          |    2 +
>  drivers/clk/qcom/clk-smd-rpm.c                     |  165 ++++++++++++++++
>  drivers/clk/qcom/clk-smd-rpm.h                     |  139 ++++++++++++++
>  drivers/clk/qcom/gcc-msm8916.c                     |   13 --
>  drivers/clk/qcom/rpmcc-msm8916.c                   |  196 ++++++++++++++++++++
>  include/dt-bindings/clock/qcom,rpmcc-msm8916.h     |   44 +++++
>  8 files changed, 585 insertions(+), 13 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/clock/qcom,rpmcc.txt
>  create mode 100644 drivers/clk/qcom/clk-smd-rpm.c
>  create mode 100644 drivers/clk/qcom/clk-smd-rpm.h
>  create mode 100644 drivers/clk/qcom/rpmcc-msm8916.c
>  create mode 100644 include/dt-bindings/clock/qcom,rpmcc-msm8916.h
> 

Hi Stephen, any comments on this?
Thanks!

  parent reply	other threads:[~2015-09-02 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 16:48 [PATCH v2 0/2] Add initial support for RPM clocks Georgi Djakov
2015-08-03 16:48 ` [PATCH v2 1/2] clk: qcom: Add support for RPM Clocks Georgi Djakov
2015-09-02 20:31   ` Stephen Boyd
2015-09-03 15:40     ` Georgi Djakov
2015-09-03 17:22       ` Bjorn Andersson
2015-09-03 17:39       ` Stephen Boyd
2015-08-03 16:48 ` [PATCH v2 2/2] clk: qcom: Add MSM8916 RPM clock driver Georgi Djakov
2015-09-02 23:55   ` Stephen Boyd
2015-09-02 16:54 ` Georgi Djakov [this message]
2015-09-21  4:33 ` [PATCH v2 0/2] Add initial support for RPM clocks Bjorn Andersson
2015-09-22 22:46   ` Georgi Djakov

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=55E729B5.3020908@linaro.org \
    --to=georgi.djakov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.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).