[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c58ffc72-59d9-49f5-be22-18588f7df1e3@linaro.org>
Date: Thu, 28 Sep 2023 07:32:20 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Yuji Ishikawa <yuji2.ishikawa@...hiba.co.jp>,
Hans Verkuil <hverkuil@...all.nl>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@...hiba.co.jp>
Cc: linux-media@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 1/5] dt-bindings: media: platform: visconti: Add
Toshiba Visconti Video Input Interface
On 26/09/2023 01:28, Yuji Ishikawa wrote:
> Adds the Device Tree binding documentation that allows to describe
> the Video Input Interface found in Toshiba Visconti SoCs.
>
> + reg:
> + items:
> + - description: Registers for capture control
> + - description: Registers for CSI2 receiver control
> + - description: Registers for bus interface unit control
> + - description: Registers for Memory Protection Unit
> +
> + interrupts:
> + items:
> + - description: Sync Interrupt
> + - description: Status (Error) Interrupt
> + - description: CSI2 Receiver Interrupt
> + - description: L1ISP Interrupt
> +
> + port:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> + description: CSI-2 input port, with a single endpoint connected to the CSI-2 transmitter.
> +
> + properties:
> + endpoint:
> + $ref: video-interfaces.yaml#
> + additionalProperties: false
This is a friendly reminder during the review process.
It seems my previous comments were not fully addressed. Maybe my
feedback got lost between the quotes, maybe you just forgot to apply it.
Please go back to the previous discussion and either implement all
requested changes or keep discussing them.
Thank you.
> +
> + required:
> + - clock-noncontinuous
> + - link-frequencies
> + - remote-endpoint
> + - data-lanes
Not much improved here. required goes after properties, always. I
pointed you last time the file which you should use as an example.
> +
> + properties:
> + data-lanes:
> + description: VIIF supports 1, 2, 3 or 4 data lanes
> + minItems: 1
> + items:
> + - const: 1
> + - const: 2
> + - const: 3
> + - const: 4
> +
> + clock-noncontinuous: true
Drop
> + link-frequencies: true
Drop
> + remote-endpoint: true
Drop
Best regards,
Krzysztof
Powered by blists - more mailing lists