From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jianhua Lu <lujianhua000@gmail.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] arm64: dts: qcom: sm8250-xiaomi-elish-boe: Add mdss and dsi panel
Date: Sat, 8 Apr 2023 15:04:52 +0200 [thread overview]
Message-ID: <0a5729a8-9fd8-a084-3932-cf8ebf00860b@linaro.org> (raw)
In-Reply-To: <20230323005925.23179-2-lujianhua000@gmail.com>
On 23/03/2023 01:59, Jianhua Lu wrote:
> Add nodes for BOE NT36523 panel found in xiaomi-elish. This panel
> is a dual dsi mode panel and the dsi phy type is cphy.
>
> Signed-off-by: Jianhua Lu <lujianhua000@gmail.com>
> ---
> Changes in v2:
> - Include missing <dt-bindings/phy/phy.h> for phy-type property.
>
> Changes in v3:
> - Sort include header.
> - Move qcom,sync-dual-dsi to the front of qcom,master-dsi
> - Add newline before subnode.
>
> .../boot/dts/qcom/sm8250-xiaomi-elish-boe.dts | 5 ++
> .../dts/qcom/sm8250-xiaomi-elish-common.dtsi | 75 +++++++++++++++++++
> 2 files changed, 80 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-boe.dts b/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-boe.dts
> index bd9ad109daf9..8b2ae39950ff 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-boe.dts
> +++ b/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-boe.dts
> @@ -11,3 +11,8 @@ / {
> model = "Xiaomi Mi Pad 5 Pro (BOE)";
> compatible = "xiaomi,elish", "qcom,sm8250";
> };
> +
> +&display_panel {
> + compatible = "xiaomi,elish-boe-nt36523";
If you add new bindings and new nodes using these - in this case this
panel - please test it. This is why we have DT schema, so you can verify
your DTS. Sending DTS which is entirely different than the bindings you
sent, is adding quite an effort for us later to fix it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-08 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 0:59 [PATCH v3 1/3] arm64: dts: qcom: Split elish dts into common dtsi and elish-boe dts Jianhua Lu
2023-03-23 0:59 ` [PATCH v3 2/3] arm64: dts: qcom: sm8250-xiaomi-elish-boe: Add mdss and dsi panel Jianhua Lu
2023-03-23 16:16 ` Konrad Dybcio
2023-04-08 13:04 ` Krzysztof Kozlowski [this message]
2023-04-08 13:33 ` Jianhua Lu
2023-03-23 0:59 ` [PATCH v3 3/3] arm64: dts: qcom: sm8250-xiaomi-elish-csot: Add Xiaomi Mi Pad 5 Pro CSOT variant Jianhua Lu
2023-03-23 6:52 ` [PATCH v3 1/3] arm64: dts: qcom: Split elish dts into common dtsi and elish-boe dts Krzysztof Kozlowski
2023-04-07 18:51 ` (subset) " 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=0a5729a8-9fd8-a084-3932-cf8ebf00860b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@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-kernel@vger.kernel.org \
--cc=lujianhua000@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).