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>,
Amit Nischal <anischal@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] clk: qcom: Add display clock controller driver for SDM845
Date: Mon, 9 Jul 2018 15:04:07 +0530 [thread overview]
Message-ID: <288770be-a763-b287-f62a-72ab7616efdb@codeaurora.org> (raw)
In-Reply-To: <153112184177.143105.15452587215679149679@swboyd.mtv.corp.google.com>
On 7/9/2018 1:07 PM, Stephen Boyd wrote:
> Quoting Taniya Das (2018-07-09 00:07:21)
>>
>>
>> On 7/9/2018 11:46 AM, Stephen Boyd wrote:
>>>>
>>>> > Why is the nocache flag needed? Applies to all clks in this file.
>>>> >
>>>>
>>>> This flag is required for all RCGs whose PLLs are controlled outside the
>>>> clock controller. The display code would require the recalculated rate
>>>> always.
>>>
>>> Right. Why is the PLL controlled outside of the clock controller? The
>>> rate should propagate upward to the PLL from here, so who's going
>>> outside of that?
>>>
>> The DSI0/1 PLL are not part of the display clock controller, but in the
>> display subsystem which are managed by the DRM drivers. When DRM drivers
>> query for the rate clock driver should always return the non cached rates.
>
> Why? Is the DSI PLL changing rate all the time, randomly, without going
> through the clk APIs to do so?
>
Hmm, I am afraid I do not have an answer for this, but this was the
requirement to always return the non cached rates from the clock driver.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
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-07-09 9:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 14:19 [PATCH v3 0/3] " Taniya Das
2018-06-23 14:19 ` [PATCH v3 1/3] clk: qcom: Move frequency table macro to common file Taniya Das
2018-07-08 23:49 ` Stephen Boyd
2018-06-23 14:19 ` [PATCH v3 2/3] dt-bindings: clock: Introduce QCOM Display clock bindings Taniya Das
2018-07-08 23:50 ` Stephen Boyd
2018-06-23 14:19 ` [PATCH v3 3/3] clk: qcom: Add display clock controller driver for SDM845 Taniya Das
2018-07-08 23:54 ` Stephen Boyd
2018-07-09 3:38 ` Taniya Das
2018-07-09 6:16 ` Stephen Boyd
2018-07-09 7:07 ` Taniya Das
2018-07-09 7:37 ` Stephen Boyd
2018-07-09 9:34 ` Taniya Das [this message]
2018-07-09 15:06 ` Stephen Boyd
2018-07-12 17:21 ` Taniya Das
2018-07-12 19:41 ` Stephen Boyd
2018-07-13 8:25 ` spanda
2018-07-16 5:57 ` Taniya Das
2018-07-24 17:32 ` 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=288770be-a763-b287-f62a-72ab7616efdb@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=anischal@codeaurora.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
all inboxes | Powered by JetHome®