From: Krzysztof Kozlowski <krzk@kernel.org>
To: Frank Li <Frank.li@nxp.com>, Liu Ying <victor.liu@nxp.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: display: panel-simple-lvds-dual-ports: use unevaluatedProperties
Date: Tue, 13 Aug 2024 11:08:45 +0200 [thread overview]
Message-ID: <9ab6419c-2066-4c6d-bb6a-f78d4845b2b5@kernel.org> (raw)
In-Reply-To: <ZrrWi0HuAIDe7C0x@lizhi-Precision-Tower-5810>
On 13/08/2024 05:44, Frank Li wrote:
> On Tue, Aug 13, 2024 at 10:32:04AM +0800, Liu Ying wrote:
>> On 08/13/2024, Frank Li wrote:
>>> Replace additionalProperties with unevaluatedProperties because it ref to
>>> panel-common.yaml.
>>
>> This would allow all properties in panel-common.yaml, which is not expected.
>> Isn't adding 'panel-timing: true' next to 'enable-gpios: true' enough?
>
> Strange, you ref to panel-common.yaml, suppose it will use all common
> preperties.
>
> Krzysztof Kozlowski:
>
> Can I just add panel-timing:true for this case?
Yes, although I would claim that most of the panel-common schema also
applies here...
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-13 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 19:36 Frank Li
2024-08-13 2:32 ` Liu Ying
2024-08-13 3:44 ` Frank Li
2024-08-13 9:08 ` Krzysztof Kozlowski [this message]
2024-08-16 22:05 ` Rob Herring
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=9ab6419c-2066-4c6d-bb6a-f78d4845b2b5@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.li@nxp.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
--cc=victor.liu@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®