From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, andersson@kernel.org,
agross@kernel.org, krzysztof.kozlowski@linaro.org
Cc: marijn.suijten@somainline.org, Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: sm8150: Add DISPCC node
Date: Mon, 12 Dec 2022 11:23:50 +0100 [thread overview]
Message-ID: <80168963-0e17-e8aa-6d99-a1c53f63c934@linaro.org> (raw)
In-Reply-To: <FF242AC6-01EC-4C8E-BE49-BB54FC9D2FEE@linaro.org>
On 12.12.2022 11:18, Dmitry Baryshkov wrote:
>
>
> On 12 December 2022 12:33:13 GMT+03:00, Konrad Dybcio <konrad.dybcio@linaro.org> wrote:
>> Years after the SoC support has been added, it's high time for it to
>> get dispcc going. Add the node to ensure that.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>> ---
>> arch/arm64/boot/dts/qcom/sm8150.dtsi | 26 ++++++++++++++++++++++++++
>> 1 file changed, 26 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sm8150.dtsi b/arch/arm64/boot/dts/qcom/sm8150.dtsi
>> index a0c57fb798d3..ff04397777f4 100644
>> --- a/arch/arm64/boot/dts/qcom/sm8150.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sm8150.dtsi
>> @@ -3579,6 +3579,32 @@ camnoc_virt: interconnect@ac00000 {
>> qcom,bcm-voters = <&apps_bcm_voter>;
>> };
>>
>> + dispcc: clock-controller@af00000 {
>> + compatible = "qcom,sm8150-dispcc";
>> + reg = <0 0x0af00000 0 0x10000>;
>> + clocks = <&rpmhcc RPMH_CXO_CLK>,
>> + <0>,
>> + <0>,
>> + <0>,
>> + <0>,
>> + <0>,
>> + <0>;
>> + clock-names = "bi_tcxo",
>> + "dsi0_phy_pll_out_byteclk",
>> + "dsi0_phy_pll_out_dsiclk",
>> + "dsi1_phy_pll_out_byteclk",
>> + "dsi1_phy_pll_out_dsiclk",
>> + "dp_phy_pll_link_clk",
>> + "dp_phy_pll_vco_div_clk";
>> + #clock-cells = <1>;
>> + #reset-cells = <1>;
>> + #power-domain-cells = <1>;
>> +
>> + power-domains = <&rpmhpd SM8150_MMCX>;
>> + /* TODO: Maybe rpmhpd_opp_min_svs could work as well? */
>> + required-opps = <&rpmhpd_opp_low_svs>;
>
> Is it required for the dispcc, for the DSI or for the dpu? We have stumbled upon the similar issue when working on the 8350, see the latest Robert's patchset.
While I don't have any hard evidence, it seems like it is required for
any "interesting" multimedia components, AFAIU even including video and
camera clocks..
Seems like it's a deep down dependency for a lot of things on this
particular SoC (and likely also on newer ones, remember the initial
mess with 8250 mmcx?)
Konrad
>
>
>> + };
>> +
>> pdc: interrupt-controller@b220000 {
>> compatible = "qcom,sm8150-pdc", "qcom,pdc";
>> reg = <0 0x0b220000 0 0x400>;
>
next prev parent reply other threads:[~2022-12-12 10:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 9:33 [PATCH 1/3] dt-bindings: display/msm: Add SM8150 MDSS & DPU Konrad Dybcio
2022-12-12 9:33 ` [PATCH 2/3] arm64: dts: qcom: sm8150: Add DISPCC node Konrad Dybcio
2022-12-12 10:18 ` Dmitry Baryshkov
2022-12-12 10:23 ` Konrad Dybcio [this message]
2022-12-12 10:53 ` Dmitry Baryshkov
2022-12-12 10:19 ` Marijn Suijten
2022-12-28 4:16 ` Bjorn Andersson
2022-12-28 23:10 ` Marijn Suijten
2022-12-12 9:33 ` [PATCH 3/3] arm64: dts: qcom: sm8150: Wire up MDSS Konrad Dybcio
2022-12-12 10:25 ` Marijn Suijten
2022-12-28 4:15 ` Bjorn Andersson
2022-12-13 14:22 ` [PATCH 1/3] dt-bindings: display/msm: Add SM8150 MDSS & DPU Rob Herring
2023-01-18 2:06 ` Dmitry Baryshkov
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=80168963-0e17-e8aa-6d99-a1c53f63c934@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
/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®