Add a schema for the JDI FHD NT35596S MIPI-DSI panel used by
the Xiaomi Mi Mix 2S. The schema documents the DSI reg value,
reset GPIO, backlight, graph port, and vddio, vddpos, and vddneg
supplies present in the DTS.
Assisted-by: LLM
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
.../display/panel/jdi,fhd-nt35596s.yaml | 73 +++++++++++++++++++
1 file changed, 73 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/panel/jdi,fhd-nt35596s.yaml
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: incorrect use of additionalProperties instead of unevaluatedProperties
--
commit e0dc4d49c687f6d5568ce2c31031086acb6cd5e6
Author: Rob Herring (Arm) [off-list ref]
dt-bindings: panel: Add JDI NT35596S
This commit adds a new device tree binding schema for the JDI FHD
NT35596S MIPI-DSI panel. It documents properties such as the DSI reg value,
reset GPIO, backlight, port, and various power supplies.
[Severity: Low]
Does the use of additionalProperties: false here incorrectly reject standard
inherited panel properties?
Because this schema references panel-common.yaml in an allOf block,
additionalProperties does not traverse the $ref references. This blocks
standard properties like rotation and forces the redundant declaration of
properties like backlight, reset-gpios, and port just to pass static JSON
schema validation during a make dt_binding_check.
Should this use unevaluatedProperties: false instead?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260921232609.3130272-1-robh@kernel.org?part=1
On Mon, Sep 21, 2026 at 11:31:27PM +0000, sashiko-bot@kernel.org wrote:
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: incorrect use of additionalProperties instead of unevaluatedProperties
--
commit e0dc4d49c687f6d5568ce2c31031086acb6cd5e6
Author: Rob Herring (Arm) [off-list ref]
dt-bindings: panel: Add JDI NT35596S
This commit adds a new device tree binding schema for the JDI FHD
NT35596S MIPI-DSI panel. It documents properties such as the DSI reg value,
reset GPIO, backlight, port, and various power supplies.
[Severity: Low]
Does the use of additionalProperties: false here incorrectly reject standard
inherited panel properties?
Because this schema references panel-common.yaml in an allOf block,
additionalProperties does not traverse the $ref references. This blocks
standard properties like rotation and forces the redundant declaration of
properties like backlight, reset-gpios, and port just to pass static JSON
schema validation during a make dt_binding_check.
Should this use unevaluatedProperties: false instead?
This seems to be the new thing that Sashiko whines about, any binding I
see with additionalProperties: false seems to get complained about.
From: Rob Herring <robh@kernel.org> Date: 2026-09-23 15:07:37
On Tue, Sep 22, 2026 at 07:03:29PM +0100, Conor Dooley wrote:
On Mon, Sep 21, 2026 at 11:31:27PM +0000, sashiko-bot@kernel.org wrote:
quoted
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: incorrect use of additionalProperties instead of unevaluatedProperties
--
commit e0dc4d49c687f6d5568ce2c31031086acb6cd5e6
Author: Rob Herring (Arm) [off-list ref]
dt-bindings: panel: Add JDI NT35596S
This commit adds a new device tree binding schema for the JDI FHD
NT35596S MIPI-DSI panel. It documents properties such as the DSI reg value,
reset GPIO, backlight, port, and various power supplies.
[Severity: Low]
Does the use of additionalProperties: false here incorrectly reject standard
inherited panel properties?
Because this schema references panel-common.yaml in an allOf block,
additionalProperties does not traverse the $ref references. This blocks
standard properties like rotation and forces the redundant declaration of
properties like backlight, reset-gpios, and port just to pass static JSON
schema validation during a make dt_binding_check.
Should this use unevaluatedProperties: false instead?
This seems to be the new thing that Sashiko whines about, any binding I
see with additionalProperties: false seems to get complained about.
That and needing labels to be resolved in examples it consistently gets
wrong. Probably need to work on the guidance...
Rob