From: sashiko-bot@kernel.org
To: "Pengyu Luo" <mitltlatltl@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org,
dri-devel@lists.freedesktop.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: display: panel: Add Novatek NT36536
Date: Tue, 30 Jun 2026 02:45:30 +0000 [thread overview]
Message-ID: <20260630024531.47D4B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260630023439.248861-2-mitltlatltl@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] Use of `additionalProperties: false` breaks inheritance of common panel properties.
- [Low] Missing space before brace in the device tree example.
--
commit a15a27453070f4b1a8c8e896b7b599f3e42a0e6c
Author: Pengyu Luo <mitltlatltl@gmail.com>
dt-bindings: display: panel: Add Novatek NT36536
This commit adds a new device tree binding for the Novatek NT36536 DSI
display panel used in the LENOVO Legion Y700 Gen4.
> diff --git a/Documentation/devicetree/bindings/display/panel/novatek,nt36536.yaml b/Documentation/devicetree/bindings/display/panel/novatek,nt36536.yaml
> new file mode 100644
> index 0000000000000..06f4d1e0ee4a0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/panel/novatek,nt36536.yaml
> @@ -0,0 +1,90 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/panel/novatek,nt36536.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Novatek NT36536 based DSI display Panels
[ ... ]
> +allOf:
> + - $ref: panel-common-dual.yaml#
> +
> +properties:
[ ... ]
> +required:
> + - compatible
> + - reg
> + - vddio-supply
> + - reset-gpios
> + - ports
> +
> +additionalProperties: false
[Severity: Low]
Does using additionalProperties: false here break the inheritance of properties
from panel-common-dual.yaml#?
The schema validator might reject standard panel properties since
additionalProperties: false only considers properties explicitly defined in the
local file's properties block. Should this be unevaluatedProperties: false
instead?
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + dsi {
[ ... ]
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> + panel_in_0: endpoint {
> + remote-endpoint = <&dsi0_out>;
> + };
> + };
> +
> + port@1{
[Severity: Low]
This isn't a bug, but there is a missing space before the brace here.
> + reg = <1>;
> + panel_in_1: endpoint {
> + remote-endpoint = <&dsi1_out>;
> + };
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260630023439.248861-1-mitltlatltl@gmail.com?part=1
next prev parent reply other threads:[~2026-06-30 2:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 2:34 [PATCH 0/2] drm/panel: Add Novatek NT36536 panel driver Pengyu Luo
2026-06-30 2:34 ` [PATCH 1/2] dt-bindings: display: panel: Add Novatek NT36536 Pengyu Luo
2026-06-30 2:45 ` sashiko-bot [this message]
2026-06-30 7:46 ` Krzysztof Kozlowski
2026-06-30 2:34 ` [PATCH 2/2] drm/panel: Add Novatek NT36536 panel driver Pengyu Luo
2026-06-30 2:47 ` sashiko-bot
2026-07-03 8:24 ` Neil Armstrong
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=20260630024531.47D4B1F000E9@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=mitltlatltl@gmail.com \
--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 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.