From: Taniya Das <tdas@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH v8] clk: qcom: Add lpass clock controller driver for SDM845
Date: Thu, 8 Nov 2018 12:13:43 +0530 [thread overview]
Message-ID: <32c2e69a-2070-5b6d-257a-627e2ad063e3@codeaurora.org> (raw)
In-Reply-To: <154152457264.88331.5152287370260040686@swboyd.mtv.corp.google.com>
Thanks Stephen.
On 11/6/2018 10:46 PM, Stephen Boyd wrote:
> Quoting Taniya Das (2018-11-02 20:16:20)
>> On 11/2/2018 10:08 PM, Stephen Boyd wrote:
>>> Quoting Taniya Das (2018-10-28 00:35:40)
>>>
>>
>> How about moving the QSPI clocks too under this qcom property? Later
>> could add the support?
>
> Yes the plan would be to have QSPI clks there too. Bjorn has sent the
> patch now.
>
> https://lkml.kernel.org/r/20181106055013.11271-1-bjorn.andersson@linaro.org
>
Would you be merging the code soon and then I should submit the cleaned
up LPASS next series?
Please suggest.
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation.
--
next prev parent reply other threads:[~2018-11-08 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 7:35 [PATCH v8] Add support for LPASS clock controller for SDM845 Taniya Das
2018-10-28 7:35 ` [PATCH v8] clk: qcom: Add lpass clock controller driver " Taniya Das
2018-11-02 16:38 ` Stephen Boyd
2018-11-03 3:16 ` Taniya Das
2018-11-06 17:16 ` Stephen Boyd
2018-11-08 6:43 ` Taniya Das [this message]
2018-11-08 18:25 ` 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=32c2e69a-2070-5b6d-257a-627e2ad063e3@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.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=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox