From: sashiko-bot@kernel.org
To: "David Heidelberg" <david@ixit.cz>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 08/10] arm64: dts: qcom: sdm845-samsung-starqltechn: Update panel compatible
Date: Sun, 08 Nov 2026 12:43:11 +0000 [thread overview]
Message-ID: <sashiko-outbox-203741@kernel.org> (raw)
In-Reply-To: <20261108-crosshatch-panel-v3-8-87dd4ec4f7cc@ixit.cz>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] arm64: dts: qcom: incompatible panel@0 compatible and
reset-gpios change
--
commit 73ab76c040fc6673b910317ac87e836c9478306e
Author: David Heidelberg <david@ixit.cz>
arm64: dts: qcom: sdm845-samsung-starqltechn: Update panel compatible
This commit replaces the panel@0 compatible string with
"samsung,s6e3ha8-amb577px01" and changes reset-gpios to GPIO_ACTIVE_LOW in
sdm845-samsung-starqltechn.dts.
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts b/arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts
> index bd59f1dcd96dc..c156ed3733b4e 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts
> +++ b/arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts
> @@ -267,13 +267,13 @@ &mdss_dsi0 {
> status = "okay";
>
> panel@0 {
> - compatible = "samsung,s6e3ha8";
> + compatible = "samsung,s6e3ha8-amb577px01";
> reg = <0>;
> vci-supply = <&s2dos05_ldo4>;
> vddr-supply = <&s2dos05_buck>;
> vdd3-supply = <&s2dos05_ldo1>;
> te-gpios = <&tlmm 10 GPIO_ACTIVE_HIGH>;
> - reset-gpios = <&tlmm 6 GPIO_ACTIVE_HIGH>;
> + reset-gpios = <&tlmm 6 GPIO_ACTIVE_LOW>;
[Severity: High]
As reported by Krzysztof Kozlowski on v2 [1], does replacing the
"samsung,s6e3ha8" compatible string and inverting reset-gpios break DTB ABI
compatibility for existing kernels and DTB consumers?
Existing kernels and trees that only match "samsung,s6e3ha8" and expect
GPIO_ACTIVE_HIGH (introduced in 70005c18c9f7 ("arm64: dts: qcom:
sdm845-starqltechn: add graphics support")) will no longer bind or reset
panel@0 when booted with this DTB, while the panel driver already handles
the legacy compatible and polarity via broken_reset_polarity.
[1] https://lore.kernel.org/r/20260929-spirited-umber-hedgehog-300ebd@quoll
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261108-crosshatch-panel-v3-0-87dd4ec4f7cc@ixit.cz?part=8
next prev parent reply other threads:[~2026-11-08 12:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 12:32 [PATCH v3 00/10] Pixel 3 XL display panel support David Heidelberg via B4 Relay
2026-11-08 12:32 ` [PATCH v3 01/10] dt-bindings: display: panel: s6e3ha8: Adjust to reflect the DDIC and panel used David Heidelberg via B4 Relay
2026-11-09 12:34 ` Krzysztof Kozlowski
2026-11-08 12:32 ` [PATCH v3 02/10] dt-bindings: display: panel: samsung,s6e3ha8: Add AMB630QY01 panel David Heidelberg via B4 Relay
2026-11-08 12:44 ` sashiko-bot
2026-11-09 12:30 ` Krzysztof Kozlowski
2026-11-08 12:32 ` [PATCH v3 03/10] drm/panel: s6e3ha8: Introduce AMB577PX01 panel compatible David Heidelberg via B4 Relay
2026-11-08 12:32 ` [PATCH v3 04/10] drm/panel: s6e3ha8: Prepare for supporting multiple panels David Heidelberg via B4 Relay
2026-11-08 12:32 ` [PATCH v3 05/10] drm/panel: s6e3ha8: Correct the polarity logic within David Heidelberg via B4 Relay
2026-11-08 12:32 ` [PATCH v3 06/10] drm/panel: s6e3ha8: Assert reset GPIO in unprepare David Heidelberg via B4 Relay
2026-11-08 12:32 ` [PATCH v3 07/10] drm/panel: s6e3ha8: add Samsung AMB630QY01 (Google Pixel 3 XL) panel David Heidelberg via B4 Relay
2026-11-08 12:32 ` [PATCH v3 08/10] arm64: dts: qcom: sdm845-samsung-starqltechn: Update panel compatible David Heidelberg via B4 Relay
2026-11-08 12:43 ` sashiko-bot [this message]
2026-11-09 12:46 ` Abel Vesa
2026-11-08 12:32 ` [PATCH v3 09/10] arm64: dts: qcom: sdm845-google: Move panel pins into common David Heidelberg via B4 Relay
2026-11-09 12:46 ` Abel Vesa
2026-11-08 12:32 ` [PATCH v3 10/10] arm64: dts: qcom: sdm845-google-crosshatch: Add display panel David Heidelberg via B4 Relay
2026-11-09 12:47 ` Abel Vesa
2026-11-09 13:10 ` Konrad Dybcio
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=sashiko-outbox-203741@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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