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,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v10 3/3] clk: qcom: Add lpass clock controller driver for SDM845
Date: Fri, 30 Nov 2018 23:47:17 +0530 [thread overview]
Message-ID: <0691834a-e2bf-20bb-fa5c-081ee6668250@codeaurora.org> (raw)
In-Reply-To: <154331006901.88331.9760589510991406736@swboyd.mtv.corp.google.com>
Hello Stephen,
On 11/27/2018 2:44 PM, Stephen Boyd wrote:
> Quoting Taniya Das (2018-11-21 23:53:41)
>> +
>> +static struct clk_branch lpass_qdsp6ss_core_clk = {
>> + .halt_reg = 0x20,
>> + /* CLK_OFF would not toggle until LPASS is not out of reset */
>
> Is this really "CLK_OFF won't toggle until LPASS it out of reset"?
>
Would take care of it, in the next series.
--
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-30 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 7:53 [PATCH v10 0/3] Add support for LPASS clock controller for SDM845 Taniya Das
2018-11-22 7:53 ` [PATCH v10 1/3] dt-bindings: clock: Update GCC bindings for protected-clocks Taniya Das
2018-11-26 18:58 ` Rob Herring
2018-11-26 18:58 ` Rob Herring
2018-11-22 7:53 ` [PATCH v10 2/3] dt-bindings: clock: Introduce QCOM LPASS clock bindings Taniya Das
2018-11-26 18:59 ` Rob Herring
2018-11-26 18:59 ` Rob Herring
2018-11-22 7:53 ` [PATCH v10 3/3] clk: qcom: Add lpass clock controller driver for SDM845 Taniya Das
2018-11-27 9:14 ` Stephen Boyd
2018-11-27 9:14 ` Stephen Boyd
2018-11-30 18:17 ` Taniya Das [this message]
2018-11-28 21:10 ` Stephen Boyd
2018-11-28 21:10 ` Stephen Boyd
2018-11-30 18:19 ` Taniya Das
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=0691834a-e2bf-20bb-fa5c-081ee6668250@codeaurora.org \
--to=tdas@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=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=robh@kernel.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 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.