From: Thierry Reding <thierry.reding@gmail.com>
To: Dmitry Osipenko <digetx@gmail.com>,
David Heidelberg <david@ixit.cz>,
Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Raffaele Tranquillini" <raffaele.tranquillini@gmail.com>,
"Ion Agorria" <ion@agorria.com>,
"Maxim Schwalm" <maxim.schwalm@gmail.com>,
"Pedro Ângelo" <pangelo@void.io>,
"Matt Merhar" <mattmerhar@protonmail.com>,
"Zack Pearsall" <zpearsall@yahoo.com>,
linux-tegra@vger.kernel.org
Subject: LVDS panel compatible strings
Date: Fri, 14 Jul 2023 16:38:52 +0200 [thread overview]
Message-ID: <ZLFd_L_Uw1PmpSep@orome> (raw)
[-- Attachment #1: Type: text/plain, Size: 3507 bytes --]
Hi everyone,
I've been working on converting all Tegra-related device tree bindings
to json-schema so that eventually we can fully validate device tree
files. Getting all the bindings reviewed and merged has been slow, but
I have a local tree where pretty much all validation errors and warnings
have been fixed. The remaining warnings that I'm not sure how to resolve
are these:
arch/arm/boot/dts/nvidia/tegra30-asus-nexus7-tilapia-E1565.dtb: display-panel: compatible:0: 'panel-lvds' is not one of ['auo,b101ew05', 'tbs,a711-panel']
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-asus-nexus7-tilapia-E1565.dtb: display-panel: compatible: ['panel-lvds'] is too short
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-asus-nexus7-tilapia-E1565.dtb: display-panel: Unevaluated properties are not allowed ('compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-asus-nexus7-grouper-E1565.dtb: display-panel: compatible:0: 'panel-lvds' is not one of ['auo,b101ew05', 'tbs,a711-panel']
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-asus-nexus7-grouper-E1565.dtb: display-panel: compatible: ['panel-lvds'] is too short
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-asus-nexus7-grouper-E1565.dtb: display-panel: Unevaluated properties are not allowed ('compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-asus-nexus7-grouper-PM269.dtb: display-panel: compatible:0: 'panel-lvds' is not one of ['auo,b101ew05', 'tbs,a711-panel']
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-asus-nexus7-grouper-PM269.dtb: display-panel: compatible: ['panel-lvds'] is too short
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-asus-nexus7-grouper-PM269.dtb: display-panel: Unevaluated properties are not allowed ('compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-pegatron-chagall.dtb: display-panel: compatible:0: 'panel-lvds' is not one of ['auo,b101ew05', 'tbs,a711-panel']
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-pegatron-chagall.dtb: display-panel: compatible: ['panel-lvds'] is too short
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
arch/arm/boot/dts/nvidia/tegra30-pegatron-chagall.dtb: display-panel: Unevaluated properties are not allowed ('compatible' was unexpected)
from schema $id: http://devicetree.org/schemas/display/panel/panel-lvds.yaml#
The reason for these is that the device tree files use:
compatible = "panel-lvds";
but that's not valid as per the bindings. So what we really want is a
specific compatible string that specifies the exact panel that each of
these devices uses in addition to the "panel-lvds" fallback. Do you guys
have information about these that could help fix up the DT files?
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-07-14 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 14:38 Thierry Reding [this message]
2023-07-14 15:00 ` LVDS panel compatible strings Svyatoslav Ryhel
2023-07-14 15:16 ` Thierry Reding
2023-07-14 15:57 ` Svyatoslav Ryhel
2023-07-17 7:16 ` Thierry Reding
2023-07-17 7:25 ` Svyatoslav Ryhel
2023-07-17 8:08 ` Svyatoslav Ryhel
2023-07-17 8:50 ` Dmitry Osipenko
2023-07-17 13:25 ` Thierry Reding
2023-07-22 1:26 ` Dmitry Osipenko
2023-07-18 20:55 ` Maxim Schwalm
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=ZLFd_L_Uw1PmpSep@orome \
--to=thierry.reding@gmail.com \
--cc=clamor95@gmail.com \
--cc=david@ixit.cz \
--cc=digetx@gmail.com \
--cc=ion@agorria.com \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=maxim.schwalm@gmail.com \
--cc=pangelo@void.io \
--cc=raffaele.tranquillini@gmail.com \
--cc=zpearsall@yahoo.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.