From: sashiko-bot@kernel.org
To: "Konrad Dybcio" <konradybcio@kernel.org>
Cc: dri-devel@lists.freedesktop.org, robh@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] Revert "dt-bindings: display: panel: panel-simple: Add lg,sw49410 compatible"
Date: Fri, 11 Sep 2026 07:43:11 +0000 [thread overview]
Message-ID: <20260911074311.BFB1D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260911-topic-lg_sw49410_revert-v1-1-c9385a9e1926@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Reverting the 'lg,sw49410' compatible from panel-simple.yaml leaves the corresponding in-tree device tree node with an undocumented compatible string, causing a dtbs_check warning.
--
commit 28eecf951716dcb353efba4db6671dff19420f95
Author: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Revert "dt-bindings: display: panel: panel-simple: Add lg,sw49410 compatible"
This reverts the addition of the lg,sw49410 compatible string from the
panel-simple bindings. The commit states the panel needs more specific
handling and that the intended compatible was supposed to contain both
the display panel name and driver IC model number.
Link: https://lore.kernel.org/all/20260614-judyln-panel-v3-2-07f4134441bd@postmarketos.org/
> Moreover, the other compatible that didn't make it in the end landed in
> the Qualcomm tree some time ago, instead of the one this revert
> removes, so it's not even used.
[Severity: Medium]
Is this statement accurate?
Looking at arch/arm64/boot/dts/qcom/sdm845-lg-judyln.dts, this compatible
string appears to be actively used by the display_panel node:
arch/arm64/boot/dts/qcom/sdm845-lg-judyln.dts:display_panel {
...
compatible = "lg,sw49410-lh609qh1", "lg,sw49410";
...
}
> diff --git a/Documentation/devicetree/bindings/display/panel/panel-simple.yaml b/Documentation/devicetree/bindings/display/panel/panel-simple.yaml
> index 3d1cc11ba3aa4..de722f45f862a 100644
> --- a/Documentation/devicetree/bindings/display/panel/panel-simple.yaml
> +++ b/Documentation/devicetree/bindings/display/panel/panel-simple.yaml
[ ... ]
> @@ -206,8 +206,6 @@ properties:
> - lemaker,bl035-rgb-002
> # LG 7" (800x480 pixels) TFT LCD panel
> - lg,lb070wv8
> - # LG 6.1" (1440x3120) IPS LCD panel
> - - lg,sw49410
[Severity: Medium]
Does removing this documentation leave the in-tree device tree node in
arch/arm64/boot/dts/qcom/sdm845-lg-judyln.dts completely undocumented?
Running make dtbs_check on the tree with this revert applied will complain
about the undocumented compatible strings lg,sw49410-lh609qh1 and lg,sw49410
for this panel node, resulting in a schema validation error.
> # Logic Technologies LT161010-2NHC 7" WVGA TFT Cap Touch Module
> - logictechno,lt161010-2nhc
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260911-topic-lg_sw49410_revert-v1-1-c9385a9e1926@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-09-11 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 7:36 [PATCH] Revert "dt-bindings: display: panel: panel-simple: Add lg,sw49410 compatible" Konrad Dybcio
2026-09-11 7:43 ` sashiko-bot [this message]
2026-09-13 9:02 ` Krzysztof Kozlowski
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=20260911074311.BFB1D1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=konradybcio@kernel.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