[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240215-supervise-concerned-55a18554a120@spud>
Date: Thu, 15 Feb 2024 17:29:40 +0000
From: Conor Dooley <conor@...nel.org>
To: Paweł Anikiel <panikiel@...gle.com>
Cc: airlied@...il.com, akpm@...ux-foundation.org, conor+dt@...nel.org,
daniel@...ll.ch, dinguyen@...nel.org, hverkuil-cisco@...all.nl,
krzysztof.kozlowski+dt@...aro.org,
maarten.lankhorst@...ux.intel.com, mchehab@...nel.org,
mripard@...nel.org, robh+dt@...nel.org, tzimmermann@...e.de,
devicetree@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
chromeos-krk-upstreaming@...gle.com, ribalda@...omium.org
Subject: Re: [PATCH 7/9] media: dt-bindings: Add Chameleon v3 framebuffer
On Mon, Feb 12, 2024 at 01:13:21PM +0000, Paweł Anikiel wrote:
> The Chameleon v3 uses the framebuffer IP core to take the video signal
> from different sources and directly write frames into memory.
>
> Signed-off-by: Paweł Anikiel <panikiel@...gle.com>
> ---
> .../bindings/media/google,chv3-fb.yaml | 77 +++++++++++++++++++
> 1 file changed, 77 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/google,chv3-fb.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/google,chv3-fb.yaml b/Documentation/devicetree/bindings/media/google,chv3-fb.yaml
> new file mode 100644
> index 000000000000..ba6643cc7232
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/google,chv3-fb.yaml
> @@ -0,0 +1,77 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/google,chv3-fb.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Google Chameleon v3 video framebuffer
> +
> +maintainers:
> + - Paweł Anikiel <panikiel@...gle.com>
> +
> +properties:
> + compatible:
> + const: google,chv3-fb
> +
> + reg:
> + items:
> + - description: core registers
> + - description: irq registers
> +
> + interrupts:
> + maxItems: 1
> +
> + google,legacy-format:
> + type: boolean
> + description: The incoming video stream is in 32-bit padded mode.
> +
> + google,no-endpoint:
> + type: boolean
> + description:
> + The framebuffer isn't connected to a controllable endpoint.
> + The video interface still works, but EDID control is unavailable
> + and DV timing information only reports the active video width/height.
Why does this need a dedicated property? Is it not sufficient to check
that there are no endpoints in the devicetree?
Cheers,
Conor.
> +
> + port:
> + $ref: /schemas/graph.yaml#/properties/port
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +allOf:
> + - if:
> + not:
> + required:
> + - google,no-endpoint
> + then:
> + required:
> + - port
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + video@...60500 {
> + compatible = "google,chv3-fb";
> + reg = <0xc0060500 0x100>,
> + <0xc0060f20 0x10>;
> + interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>;
> + google,legacy-format;
> + google,no-endpoint;
> + };
> +
> + - |
> + video@...60600 {
> + compatible = "google,chv3-fb";
> + reg = <0xc0060600 0x100>,
> + <0xc0060f30 0x10>;
> + interrupts = <GIC_SPI 22 IRQ_TYPE_LEVEL_HIGH>;
> +
> + port {
> + fb_mst0_0: endpoint {
> + remote-endpoint = <&dprx_mst_0>;
> + };
> + };
> + };
> --
> 2.43.0.687.g38aa6559b0-goog
>
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists