From: Conor Dooley <conor@kernel.org>
To: "Paweł Anikiel" <panikiel@google.com>
Cc: airlied@gmail.com, akpm@linux-foundation.org,
conor+dt@kernel.org, daniel@ffwll.ch, dinguyen@kernel.org,
hverkuil-cisco@xs4all.nl, krzysztof.kozlowski+dt@linaro.org,
maarten.lankhorst@linux.intel.com, mchehab@kernel.org,
mripard@kernel.org, robh+dt@kernel.org, tzimmermann@suse.de,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
chromeos-krk-upstreaming@google.com, ribalda@chromium.org
Subject: Re: [PATCH 7/9] media: dt-bindings: Add Chameleon v3 framebuffer
Date: Thu, 15 Feb 2024 17:29:40 +0000 [thread overview]
Message-ID: <20240215-supervise-concerned-55a18554a120@spud> (raw)
In-Reply-To: <20240212131323.2162161-8-panikiel@google.com>
[-- Attachment #1: Type: text/plain, Size: 2944 bytes --]
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@google.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@google.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@c0060500 {
> + compatible = "google,chv3-fb";
> + reg = <0xc0060500 0x100>,
> + <0xc0060f20 0x10>;
> + interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>;
> + google,legacy-format;
> + google,no-endpoint;
> + };
> +
> + - |
> + video@c0060600 {
> + 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
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-02-15 17:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 13:13 [PATCH 0/9] Add Chameleon v3 video support Paweł Anikiel
2024-02-12 13:13 ` [PATCH 1/9] media: v4l2-subdev: Add a pad variant of .query_dv_timings() Paweł Anikiel
2024-02-12 13:13 ` [PATCH 2/9] media: Add Chameleon v3 framebuffer driver Paweł Anikiel
2024-02-12 13:13 ` [PATCH 3/9] drm/dp_mst: Move DRM-independent structures to separate header Paweł Anikiel
2024-02-12 13:13 ` [PATCH 4/9] lib: Move DisplayPort CRC functions to common lib Paweł Anikiel
2024-02-12 13:13 ` [PATCH 5/9] drm/display: Add mask definitions for DP_PAYLOAD_ALLOCATE_* registers Paweł Anikiel
2024-02-12 13:13 ` [PATCH 6/9] media: intel: Add Displayport RX IP driver Paweł Anikiel
2024-02-12 13:13 ` [PATCH 7/9] media: dt-bindings: Add Chameleon v3 framebuffer Paweł Anikiel
2024-02-12 14:35 ` Rob Herring
2024-02-12 15:51 ` Paweł Anikiel
2024-02-16 9:43 ` Krzysztof Kozlowski
2024-02-15 17:29 ` Conor Dooley [this message]
2024-02-21 16:16 ` Paweł Anikiel
2024-02-12 13:13 ` [PATCH 8/9] media: dt-bindings: Add Intel Displayport RX IP Paweł Anikiel
2024-02-12 14:35 ` Rob Herring
2024-02-12 15:52 ` Paweł Anikiel
2024-02-15 17:26 ` Conor Dooley
2024-02-21 16:30 ` Paweł Anikiel
2024-02-12 13:13 ` [PATCH 9/9] ARM: dts: chameleonv3: Add video device nodes Paweł Anikiel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240215-supervise-concerned-55a18554a120@spud \
--to=conor@kernel.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chromeos-krk-upstreaming@google.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=panikiel@google.com \
--cc=ribalda@chromium.org \
--cc=robh+dt@kernel.org \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox