From: Thierry Reding <thierry.reding@gmail.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Dmitry Osipenko" <digetx@gmail.com>,
"David Heidelberg" <david@ixit.cz>,
"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: Re: LVDS panel compatible strings
Date: Fri, 14 Jul 2023 17:16:22 +0200 [thread overview]
Message-ID: <ZLFmxuVuO2FWy1as@orome> (raw)
In-Reply-To: <CAPVz0n3fj77JEzJbYve9-5pjjVt+yJHNcFGqJr0HFSJnaOtbzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4070 bytes --]
On Fri, Jul 14, 2023 at 06:00:43PM +0300, Svyatoslav Ryhel wrote:
> пт, 14 лип. 2023 р. о 17:38 Thierry Reding <thierry.reding@gmail.com> пише:
> >
> > 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#
>
> Hello Thierry! Pegatron Chagall uses a Hannstar similar to one used in
> ASUS TF201 but unfortunately it is not compatible with existing simple
> panel setup (blurry image if used). My assumption is that chagall as
> different revision of this panel like HSD101PWW3-B00 or
> HSD101PWW1-A00 which is more likely or panel is highly modified which
> is unlikely. I propose to use "hannstar,hsd101pww1" which is more wide
> spread.
Interesting. So is the problem the HSD101PWW2 timings that are off, or
is it because the panel-lvds code does something special to make this
blurry image go away?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-14 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 14:38 LVDS panel compatible strings Thierry Reding
2023-07-14 15:00 ` Svyatoslav Ryhel
2023-07-14 15:16 ` Thierry Reding [this message]
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=ZLFmxuVuO2FWy1as@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.