From mboxrd@z Thu Jan 1 00:00:00 1970 From: Claude Code Review Bot To: dri-devel-reviews@example.com Subject: Claude review: dt-bindings: display: bridge: Document Renesas R-Car V4H DSC bindings Date: Sat, 16 May 2026 09:46:52 +1000 Message-ID: In-Reply-To: <20260515-rcar-du-dsc-v2-2-f6b9240a1240@ideasonboard.com> References: <20260515-rcar-du-dsc-v2-0-f6b9240a1240@ideasonboard.com> <20260515-rcar-du-dsc-v2-2-f6b9240a1240@ideasonboard.com> X-Mailer: Claude Code Patch Reviewer Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Patch Review **Status: Looks good, minor comment** The binding schema is well-structured. The required properties (compatible, reg, clocks, interrupts, power-domains, resets, ports) match the driver's resource acquisition. The example is consistent with the actual DTS node added in patch 5. One small note: the binding uses `unevaluatedProperties: false` at the top level but does not include `additionalProperties: false` under `ports/properties`. The `$ref: /schemas/graph.yaml#/properties/ports` should handle that, so this is fine. The binding declares `interrupts` as required, but the driver (patch 3) never requests or uses the interrupt. This is acceptable for a binding (it describes hardware, not driver capabilities), but worth noting for future DSC encoding support. --- --- Generated by Claude Code Patch Reviewer