From: Stephen Boyd <sboyd@codeaurora.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v6 0/2] Add initial support for RPM clocks
Date: Thu, 11 Feb 2016 16:37:57 -0800 [thread overview]
Message-ID: <20160212003757.GD4847@codeaurora.org> (raw)
In-Reply-To: <1450182602-6996-1-git-send-email-georgi.djakov@linaro.org>
On 12/15, Georgi Djakov wrote:
>
> .../devicetree/bindings/clock/qcom,rpmcc.txt | 37 ++
> drivers/clk/qcom/Kconfig | 29 ++
> drivers/clk/qcom/Makefile | 2 +
> drivers/clk/qcom/clk-rpm.c | 290 +++++++++++++
> drivers/clk/qcom/clk-rpm.h | 71 ++++
Do we need this header file?
> drivers/clk/qcom/clk-smd-rpm.c | 433 ++++++++++++++++++++
> drivers/clk/qcom/clk-smd-rpm.h | 142 +++++++
And this one too?
>From what I can tell they're only going to be included by the
clk-rpm and clk-smd-rpm C files. We can also avoid exporting the
RPM ops then if we're going to make the C files into full blown
platform drivers.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-02-12 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 12:30 [PATCH v6 0/2] Add initial support for RPM clocks Georgi Djakov
2015-12-15 12:30 ` [PATCH v6 1/2] clk: qcom: Add support for SMD-RPM Clocks Georgi Djakov
2015-12-15 12:30 ` [PATCH v6 2/2] clk: qcom: Add support for RPM Clocks Georgi Djakov
2016-02-12 0:41 ` Stephen Boyd
2016-02-22 15:32 ` Georgi Djakov
2016-03-13 13:06 ` Bjorn Andersson
2016-03-15 17:16 ` Georgi Djakov
2016-02-12 0:37 ` Stephen Boyd [this message]
2016-02-22 15:29 ` [PATCH v6 0/2] Add initial support for RPM clocks 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=20160212003757.GD4847@codeaurora.org \
--to=sboyd@codeaurora.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=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 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.