From: Stephen Boyd <sboyd@codeaurora.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v9 2/3] clk: qcom: Add support for RPM Clocks
Date: Thu, 10 Nov 2016 16:48:18 -0800 [thread overview]
Message-ID: <20161111004818.GB5177@codeaurora.org> (raw)
In-Reply-To: <20161102155658.32203-3-georgi.djakov@linaro.org>
On 11/02, Georgi Djakov wrote:
> This adds initial support for clocks controlled by the Resource
> Power Manager (RPM) processor on some Qualcomm SoCs, which use
> the qcom_rpm driver to communicate with RPM.
> Such platforms are apq8064 and msm8960.
>
> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
> ---
Applied to clk-qcom-rpm and merged into clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-11-11 0:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 15:56 [PATCH v9 0/3] Add initial support for RPM clocks Georgi Djakov
2016-11-02 15:56 ` [PATCH v9 1/3] clk: qcom: Add support for SMD-RPM Clocks Georgi Djakov
2016-11-09 18:26 ` Rob Herring
2016-11-11 0:48 ` Stephen Boyd
2016-11-02 15:56 ` [PATCH v9 2/3] clk: qcom: Add support for RPM Clocks Georgi Djakov
2016-11-09 18:26 ` Rob Herring
2016-11-11 0:48 ` Stephen Boyd [this message]
[not found] ` <20161102155658.32203-1-georgi.djakov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-11-02 15:56 ` [PATCH v9 3/3] clk: qcom: Always add factor clock for xo clocks Georgi Djakov
2016-11-02 15:56 ` Georgi Djakov
[not found] ` <20161102155658.32203-4-georgi.djakov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-11-11 0:48 ` Stephen Boyd
2016-11-11 0:48 ` 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=20161111004818.GB5177@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@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.