From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Taniya Das <tdas@codeaurora.org>
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, 08 Nov 2018 10:25:18 -0800 [thread overview]
Message-ID: <154170151864.88331.3913955115537863015@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <32c2e69a-2070-5b6d-257a-627e2ad063e3@codeaurora.org>
Quoting Taniya Das (2018-11-07 22:43:43)
> 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?
>
Yes, if you want to resubmit on top of that series it would make it
easier for me to apply these patches. I'm currently waiting for any DT
review from Rob Herring, and having the patches ready and staged can be
done regardless of that.
prev parent reply other threads:[~2018-11-08 18:25 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
2018-11-08 18:25 ` Stephen Boyd [this message]
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=154170151864.88331.3913955115537863015@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.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=tdas@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).