| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20240704-catcall-stubbly-9258b056e42e@spud>
Date: Thu, 4 Jul 2024 17:26:56 +0100
From: Conor Dooley <conor@...nel.org>
To: Julien Stephan <jstephan@...libre.com>
Cc: Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Andy Hsieh <andy.hsieh@...iatek.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
linux-media@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Louis Kuo <louis.kuo@...iatek.com>,
Phi-Bang Nguyen <pnguyen@...libre.com>
Subject: Re: [PATCH v5 1/5] dt-bindings: media: add mediatek ISP3.0 sensor
interface
On Thu, Jul 04, 2024 at 03:36:40PM +0200, Julien Stephan wrote:
> From: Louis Kuo <louis.kuo@...iatek.com>
>
> This adds the bindings, for the mediatek ISP3.0 SENINF module embedded in
> some Mediatek SoC, such as the mt8365
>
> Signed-off-by: Louis Kuo <louis.kuo@...iatek.com>
> Signed-off-by: Phi-Bang Nguyen <pnguyen@...libre.com>
> Link: https://lore.kernel.org/r/20230807094940.329165-2-jstephan@baylibre.com
> Signed-off-by: Laurent Pinchart <laurent.pinchart@...asonboard.com>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@...asonboard.com>
> Signed-off-by: Julien Stephan <jstephan@...libre.com>
I'm really confused by the link tag here. At first glance this looked
like you were sending out something that had been applied by Laurent,
given the Link, Rb and SoB from him. Why does he have a SoB on this
patch? What did Phi-Bang Nguyen do with this patch, and should they have
a Co-developed-by tag?
> ---
> .../bindings/media/mediatek,mt8365-seninf.yaml | 275 +++++++++++++++++++++
> MAINTAINERS | 7 +
> 2 files changed, 282 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/media/mediatek,mt8365-seninf.yaml b/Documentation/devicetree/bindings/media/mediatek,mt8365-seninf.yaml
> new file mode 100644
> index 000000000000..aeabea9f956a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/mediatek,mt8365-seninf.yaml
> @@ -0,0 +1,275 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright (c) 2023 MediaTek, BayLibre
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/mediatek,mt8365-seninf.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MediaTek Sensor Interface 3.0
> +
> +maintainers:
> + - Laurent Pinchart <laurent.pinchart@...asonboard.com>
> + - Julien Stephan <jstephan@...libre.com>
> + - Andy Hsieh <andy.hsieh@...iatek.com>
> +
> +description:
> + The ISP3.0 SENINF is the CSI-2 and parallel camera sensor interface found in
> + multiple MediaTek SoCs. It can support up to three physical CSI-2 input ports,
> + configured in DPHY (2 or 4 data lanes) or CPHY depending on the SoC.
> + On the output side, SENINF can be connected either to CAMSV instance or
> + to the internal ISP. CAMSV is used to bypass the internal ISP processing
> + in order to connect either an external ISP, or a sensor (RAW, YUV).
> +
> +properties:
> + compatible:
> + const: mediatek,mt8365-seninf
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + power-domains:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: Seninf camsys clock
> + - description: Seninf top mux clock
> +
> + clock-names:
> + items:
> + - const: camsys
> + - const: top_mux
> +
> + phys: true
> +
> + phy-names: true
> +
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + properties:
> + port@0:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> + description: CSI0 or CSI0A port
> +
> + properties:
> + endpoint:
> + $ref: video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + clock-lanes:
> + maxItems: 1
> + data-lanes:
> + minItems: 1
> + maxItems: 4
> +
> + port@1:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> + description: CSI1 port
> +
> + properties:
> + endpoint:
> + $ref: video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + clock-lanes:
> + maxItems: 1
> + data-lanes:
> + minItems: 1
> + maxItems: 4
> +
> + port@2:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> + description: CSI2 port
> +
> + properties:
> + endpoint:
> + $ref: video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + clock-lanes:
> + maxItems: 1
> + data-lanes:
> + minItems: 1
> + maxItems: 4
> +
> + port@3:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> + description: CSI0B port
> +
> + properties:
> + endpoint:
> + $ref: video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + clock-lanes:
> + maxItems: 1
> + data-lanes:
> + minItems: 1
> + maxItems: 2
> +
> + port@4:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: connection point for cam0
> +
> + port@5:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: connection point for cam1
> +
> + port@6:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: connection point for camsv0
> +
> + port@7:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: connection point for camsv1
> +
> + port@8:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: connection point for camsv2
> +
> + port@9:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: connection point for camsv3
> +
> + required:
> + - port@0
> + - port@1
> + - port@2
> + - port@3
> + - port@4
> + - port@5
> + - port@6
> + - port@7
> + - port@8
> + - port@9
> +
> +required:
> + - compatible
> + - interrupts
> + - clocks
> + - clock-names
> + - power-domains
> + - ports
> +
> +additionalProperties: false
> +
> +if:
> + properties:
> + compatible:
> + contains:
> + const: mediatek,mt8365-seninf
The binding supports only a single compatible, why is this complexity
required? I don't see other devices being added in this series.
Cheers,
Conor.
> +then:
> + properties:
> + phys:
> + minItems: 2
> + maxItems: 2
> + description:
> + phandle to the PHYs connected to CSI0/A, CSI1, CSI0B
> +
> + phy-names:
> + description:
> + list of PHYs names
> + minItems: 2
> + maxItems: 2
> + items:
> + type: string
> + enum:
> + - csi0
> + - csi1
> + - csi0b
> + uniqueItems: true
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists