From: Johan Hovold <johan@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Johan Hovold <johan+linaro@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sc8280xp-x13s: Use the correct DP PHY compatible
Date: Mon, 16 Oct 2023 10:12:30 +0200 [thread overview]
Message-ID: <ZSzwbmE_grD-giRp@hovoldconsulting.com> (raw)
In-Reply-To: <ZRqFYWtEcuSCauCf@hovoldconsulting.com>
On Mon, Oct 02, 2023 at 10:54:57AM +0200, Johan Hovold wrote:
> On Fri, Sep 29, 2023 at 06:02:57PM +0200, Konrad Dybcio wrote:
> > The DP PHY needs different settings when an eDP display is used.
> > Make sure these apply on the X13s.
>
> Good catch. This looks to be more in line with what Bjorn intended.
>
> You should fix up sc8280xp-crd and sa8295p-adp.dts as well however.
As we discussed off-list, some of the ADP DP PHYs are apparently just
confusingly named "eDP" for some reason so that does not need fixing.
I sent a fix for the CRD here:
https://lore.kernel.org/all/20231016080658.6667-1-johan+linaro@kernel.org/
> > &mdss0_dp3_phy {
> > + compatible = "qcom,sc8280xp-edp-phy";
>
> Nit: Can you add a newline here after the compatible, please?
Would you mind respinning this one with an added newline here for
consistency, though?
> > vdda-phy-supply = <&vreg_l6b>;
> > vdda-pll-supply = <&vreg_l3b>;
Johan
next prev parent reply other threads:[~2023-10-16 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 16:02 [PATCH] arm64: dts: qcom: sc8280xp-x13s: Use the correct DP PHY compatible Konrad Dybcio
2023-10-02 8:54 ` Johan Hovold
2023-10-16 8:12 ` Johan Hovold [this message]
2023-10-16 8:51 ` Dmitry Baryshkov
2023-10-16 9:01 ` Johan Hovold
2023-10-16 9:10 ` Dmitry Baryshkov
2023-10-17 3:28 ` Bjorn Andersson
2023-10-17 16:22 ` Konrad Dybcio
2023-10-22 15:50 ` 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=ZSzwbmE_grD-giRp@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).