Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Ajit Pandey <quic_ajipan@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Vinod Koul <vkoul@kernel.org>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Taniya Das <quic_tdas@quicinc.com>,
	Jagadeesh Kona <quic_jkona@quicinc.com>,
	Imran Shaik <quic_imrashai@quicinc.com>,
	Satya Priya Kakitapalli <quic_skakitap@quicinc.com>
Subject: Re: [PATCH V4 8/8] arm64: dts: qcom: sm4450: add camera, display and gpu clock controller
Date: Fri, 12 Jul 2024 18:01:30 +0530	[thread overview]
Message-ID: <46e6f1f0-d244-4e53-99ce-9fee339dc4de@quicinc.com> (raw)
In-Reply-To: <8f7cdb31-c50d-4690-b878-518bad545612@linaro.org>



On 7/12/2024 5:52 PM, Konrad Dybcio wrote:
> On 12.07.2024 11:53 AM, Ajit Pandey wrote:
>>
>>
>> On 7/11/2024 3:25 PM, Konrad Dybcio wrote:
>>> On 3.07.2024 11:16 AM, Ajit Pandey wrote:
>>>>
>>>>
>>>> On 6/13/2024 1:11 PM, Konrad Dybcio wrote:
>>>>>
>>>>>
>>>>> On 6/11/24 15:37, Ajit Pandey wrote:
>>>>>> Add device node for camera, display and graphics clock controller on
>>>>>> Qualcomm SM4450 platform.
>>>>>>
>>>>>> Signed-off-by: Ajit Pandey <quic_ajipan@quicinc.com>
>>>>>> ---
>>>>>
>>>>> None of these nodes reference a power domain (which would usually be
>>>>> CX/MX/MMCX). This way, the RPMhPDs will never be scaled.
>>>>>
>>>>> The current upstream implementation only allows one power domain to be
>>>>> scaled, but that's better than none (see other DTs for recent SoCs).
>>>>>
>>>>> Konrad
>>>>
>>>> SM4450 doesn't support MMCX and CX/MX domains will remain active so
>>>> power-domains property is actually not required for SM4450 clock nodes.
>>>
>>> It's not only about them being active.. some PLLs require e.g. MX to be
>>> at a certain level, or the system will be unstable
>>>
>>> Konrad
>>
>> With active I mean CX/MX rails will be default running at minimum level required for clock controllers. Adding power-domains property for CX/MX rails is like a redundant code as that will also scale such rails at default specified minimum level only. Also we hadn't added such property for other targets DT nodes to scale up CX/MX at minimum level.
> 
> What I mean here is that, the minimum level may not be enough. In such case
> you would also add a required-opps = <&handle_to_rpmhpd_opp_level>
> 
> Konrad
> 

Apologies, but could you please elaborate the use-case where minimum 
level isn't enough ? I guess for clock controllers configuration min 
level of CX/MX would be suffice, client will anyhow scale such rails to 
higher levels depending on their use-case.

-- 
Thanks, and Regards
Ajit

  reply	other threads:[~2024-07-12 12:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 13:37 [PATCH V4 0/8] clk: qcom: Add support for DISPCC, CAMCC and GPUCC on SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 1/8] clk: qcom: clk-alpha-pll: Fix CAL_L_VAL override for LUCID EVO PLL Ajit Pandey
2024-06-13  8:19   ` Vladimir Zapolskiy
2024-06-13 16:58   ` Konrad Dybcio
2024-06-11 13:37 ` [PATCH V4 2/8] dt-bindings: clock: qcom: add DISPCC clocks on SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 3/8] clk: qcom: Add DISPCC driver support for SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 4/8] dt-bindings: clock: qcom: add CAMCC clocks on SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 5/8] clk: qcom: Add CAMCC driver support for SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 6/8] dt-bindings: clock: qcom: add GPUCC clocks on SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 7/8] clk: qcom: Add GPUCC driver support for SM4450 Ajit Pandey
2024-06-11 13:37 ` [PATCH V4 8/8] arm64: dts: qcom: sm4450: add camera, display and gpu clock controller Ajit Pandey
2024-06-11 15:47   ` Dmitry Baryshkov
2024-06-13  7:41   ` Konrad Dybcio
2024-07-03  9:16     ` Ajit Pandey
2024-07-11  9:55       ` Konrad Dybcio
2024-07-12  9:53         ` Ajit Pandey
2024-07-12 12:22           ` Konrad Dybcio
2024-07-12 12:31             ` Ajit Pandey [this message]
2024-07-12 12:40               ` Konrad Dybcio
2024-07-16  8:39                 ` Taniya Das
2024-07-16 10:39                   ` Konrad Dybcio
2024-07-26  8:18                     ` Ajit Pandey
2024-08-15 20:40 ` (subset) [PATCH V4 0/8] clk: qcom: Add support for DISPCC, CAMCC and GPUCC on SM4450 Bjorn Andersson

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=46e6f1f0-d244-4e53-99ce-9fee339dc4de@quicinc.com \
    --to=quic_ajipan@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_imrashai@quicinc.com \
    --cc=quic_jkona@quicinc.com \
    --cc=quic_skakitap@quicinc.com \
    --cc=quic_tdas@quicinc.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=vladimir.zapolskiy@linaro.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