[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240510211613.GA751688-robh@kernel.org>
Date: Fri, 10 May 2024 16:16:13 -0500
From: Rob Herring <robh@...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, 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
Subject: Re: [PATCH v3 05/10] media: dt-bindings: video-interfaces: Support
DisplayPort MST
On Tue, May 07, 2024 at 03:54:08PM +0000, Paweł Anikiel wrote:
> Add a DisplayPort bus type and a multi-stream-support property
> indicating whether the interface supports MST.
>
> Signed-off-by: Paweł Anikiel <panikiel@...gle.com>
> ---
> .../devicetree/bindings/media/video-interfaces.yaml | 7 +++++++
> include/dt-bindings/media/video-interfaces.h | 2 ++
> 2 files changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/media/video-interfaces.yaml b/Documentation/devicetree/bindings/media/video-interfaces.yaml
> index 26e3e7d7c67b..7bf3a2c09a5b 100644
> --- a/Documentation/devicetree/bindings/media/video-interfaces.yaml
> +++ b/Documentation/devicetree/bindings/media/video-interfaces.yaml
> @@ -94,6 +94,7 @@ properties:
> - 5 # Parallel
> - 6 # BT.656
> - 7 # DPI
> + - 8 # DisplayPort
> description:
> Data bus type.
>
> @@ -217,4 +218,10 @@ properties:
> Whether the clock signal is used as clock (0) or strobe (1). Used with
> CCP2, for instance.
>
> + multi-stream-support:
If MST is a known term for DP, then perhaps "dp-mst-support" for the
name. In any case, 'dp' should be in there somewhere.
> + type: boolean
> + description:
> + Support transport of multiple independent streams. Used for
> + DisplayPort MST-capable interfaces.
Wouldn't this be implied by the devices at each end of the link? The
drivers for each device should really list out features supported for
the link. The mode used is then the union of those 2 lists with DT
properties only used when the union is not definitive.
> +
> additionalProperties: true
> diff --git a/include/dt-bindings/media/video-interfaces.h b/include/dt-bindings/media/video-interfaces.h
> index 68ac4e05e37f..b236806f4482 100644
> --- a/include/dt-bindings/media/video-interfaces.h
> +++ b/include/dt-bindings/media/video-interfaces.h
> @@ -12,5 +12,7 @@
> #define MEDIA_BUS_TYPE_CSI2_DPHY 4
> #define MEDIA_BUS_TYPE_PARALLEL 5
> #define MEDIA_BUS_TYPE_BT656 6
> +#define MEDIA_BUS_TYPE_DPI 7
> +#define MEDIA_BUS_TYPE_DISPLAYPORT 8
>
> #endif /* __DT_BINDINGS_MEDIA_VIDEO_INTERFACES_H__ */
> --
> 2.45.0.rc1.225.g2a3ae87e7f-goog
>
Powered by blists - more mailing lists