From: Tirupathi Reddy T <tirupath@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: sboyd@codeaurora.org, mturquette@baylibre.com,
mark.rutland@arm.com, andy.gross@linaro.org,
david.brown@linaro.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 V6] clk: qcom: Add spmi_pmic clock divider support
Date: Tue, 21 Nov 2017 14:42:51 +0530 [thread overview]
Message-ID: <396227ab-d628-ba5e-1e63-ad51f5cae253@codeaurora.org> (raw)
In-Reply-To: <20171117202243.you76ej4qvk3ul3g@rob-hp-laptop>
On 11/18/2017 1:52 AM, Rob Herring wrote:
> On Fri, Nov 17, 2017 at 03:18:47PM +0530, Tirupathi Reddy wrote:
>> Clkdiv module provides a clock output on the PMIC with CXO as
>> the source. This clock can be routed through PMIC GPIOs. Add
>> a device driver to configure this clkdiv module.
>>
>> Signed-off-by: Tirupathi Reddy <tirupath@codeaurora.org>
>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> Normally your S-o-B would be last.
Addressed in next patch version [7]
>
>> ---
>> .../bindings/clock/clk-spmi-pmic-div.txt | 59 ++++
> Please split bindings to a separate patch.
Addressed in next patch version [7]
>
> Otherwise,
>
> Acked-by: Rob Herring <robh@kernel.org>
>
>> drivers/clk/qcom/Kconfig | 9 +
>> drivers/clk/qcom/Makefile | 1 +
>> drivers/clk/qcom/clk-spmi-pmic-div.c | 308 +++++++++++++++++++++
>> 4 files changed, 377 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/clock/clk-spmi-pmic-div.txt
>> create mode 100644 drivers/clk/qcom/clk-spmi-pmic-div.c
next prev parent reply other threads:[~2017-11-21 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 9:48 [PATCH V6] clk: qcom: Add spmi_pmic clock divider support Tirupathi Reddy
2017-11-17 20:22 ` Rob Herring
2017-11-21 9:12 ` Tirupathi Reddy T [this message]
2017-11-17 23:56 ` Stephen Boyd
2017-11-21 9:12 ` Tirupathi Reddy T
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=396227ab-d628-ba5e-1e63-ad51f5cae253@codeaurora.org \
--to=tirupath@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--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=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--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