From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Markus Schneider-Pargmann <msp@baylibre.com>
Subject: [RFC PATCH 1/5] dt-bindings: mediatek,dpi: Add mt8195 dpintf
Date: Mon, 16 Aug 2021 21:25:19 +0200 [thread overview]
Message-ID: <20210816192523.1739365-2-msp@baylibre.com> (raw)
In-Reply-To: <20210816192523.1739365-1-msp@baylibre.com>
DP_INTF is similar to the actual dpi. They differ in some points
regarding registers and what needs to be set but the function blocks
itself are similar in design.
Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
---
.../display/mediatek/mediatek,dpi.yaml | 48 ++++++++++++++++---
1 file changed, 42 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
index dd2896a40ff0..de4bdacd83ac 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
@@ -4,7 +4,7 @@
$id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
-title: mediatek DPI Controller Device Tree Bindings
+title: mediatek DPI/DP_INTF Controller Device Tree Bindings
maintainers:
- CK Hu <ck.hu@mediatek.com>
@@ -13,7 +13,8 @@ maintainers:
description: |
The Mediatek DPI function block is a sink of the display subsystem and
provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a parallel
- output bus.
+ output bus. The Mediatek DP_INTF is a similar function block that is
+ connected to the (embedded) display port function block.
properties:
compatible:
@@ -23,6 +24,7 @@ properties:
- mediatek,mt8173-dpi
- mediatek,mt8183-dpi
- mediatek,mt8192-dpi
+ - mediatek,mt8195-dpintf
reg:
maxItems: 1
@@ -37,10 +39,11 @@ properties:
- description: DPI PLL
clock-names:
- items:
- - const: pixel
- - const: engine
- - const: pll
+ description:
+ For dpi clocks pixel, engine and pll are required. For dpintf pixel, pll,
+ pll_d2, pll_d4, pll_d8, pll_d16, hf_fmm, hf_fdp are required.
+ minItems: 3
+ maxItems: 8
pinctrl-0: true
pinctrl-1: true
@@ -64,6 +67,39 @@ required:
- clock-names
- port
+allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - mediatek,mt8195-dpintf
+ then:
+ properties:
+ clocks:
+ minItems: 8
+ maxItems: 8
+ clock-names:
+ items:
+ - const: pixel
+ - const: pll
+ - const: pll_d2
+ - const: pll_d4
+ - const: pll_d8
+ - const: pll_d16
+ - const: hf_fmm
+ - const: hf_fdp
+ else:
+ properties:
+ clocks:
+ minItems: 3
+ maxItems: 3
+ clock-names:
+ items:
+ - const: pixel
+ - const: engine
+ - const: pll
+
additionalProperties: false
examples:
--
2.32.0
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Markus Schneider-Pargmann <msp@baylibre.com>
Subject: [RFC PATCH 1/5] dt-bindings: mediatek,dpi: Add mt8195 dpintf
Date: Mon, 16 Aug 2021 21:25:19 +0200 [thread overview]
Message-ID: <20210816192523.1739365-2-msp@baylibre.com> (raw)
In-Reply-To: <20210816192523.1739365-1-msp@baylibre.com>
DP_INTF is similar to the actual dpi. They differ in some points
regarding registers and what needs to be set but the function blocks
itself are similar in design.
Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
---
.../display/mediatek/mediatek,dpi.yaml | 48 ++++++++++++++++---
1 file changed, 42 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
index dd2896a40ff0..de4bdacd83ac 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
@@ -4,7 +4,7 @@
$id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
-title: mediatek DPI Controller Device Tree Bindings
+title: mediatek DPI/DP_INTF Controller Device Tree Bindings
maintainers:
- CK Hu <ck.hu@mediatek.com>
@@ -13,7 +13,8 @@ maintainers:
description: |
The Mediatek DPI function block is a sink of the display subsystem and
provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a parallel
- output bus.
+ output bus. The Mediatek DP_INTF is a similar function block that is
+ connected to the (embedded) display port function block.
properties:
compatible:
@@ -23,6 +24,7 @@ properties:
- mediatek,mt8173-dpi
- mediatek,mt8183-dpi
- mediatek,mt8192-dpi
+ - mediatek,mt8195-dpintf
reg:
maxItems: 1
@@ -37,10 +39,11 @@ properties:
- description: DPI PLL
clock-names:
- items:
- - const: pixel
- - const: engine
- - const: pll
+ description:
+ For dpi clocks pixel, engine and pll are required. For dpintf pixel, pll,
+ pll_d2, pll_d4, pll_d8, pll_d16, hf_fmm, hf_fdp are required.
+ minItems: 3
+ maxItems: 8
pinctrl-0: true
pinctrl-1: true
@@ -64,6 +67,39 @@ required:
- clock-names
- port
+allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - mediatek,mt8195-dpintf
+ then:
+ properties:
+ clocks:
+ minItems: 8
+ maxItems: 8
+ clock-names:
+ items:
+ - const: pixel
+ - const: pll
+ - const: pll_d2
+ - const: pll_d4
+ - const: pll_d8
+ - const: pll_d16
+ - const: hf_fmm
+ - const: hf_fdp
+ else:
+ properties:
+ clocks:
+ minItems: 3
+ maxItems: 3
+ clock-names:
+ items:
+ - const: pixel
+ - const: engine
+ - const: pll
+
additionalProperties: false
examples:
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Markus Schneider-Pargmann <msp@baylibre.com>
Subject: [RFC PATCH 1/5] dt-bindings: mediatek,dpi: Add mt8195 dpintf
Date: Mon, 16 Aug 2021 21:25:19 +0200 [thread overview]
Message-ID: <20210816192523.1739365-2-msp@baylibre.com> (raw)
In-Reply-To: <20210816192523.1739365-1-msp@baylibre.com>
DP_INTF is similar to the actual dpi. They differ in some points
regarding registers and what needs to be set but the function blocks
itself are similar in design.
Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
---
.../display/mediatek/mediatek,dpi.yaml | 48 ++++++++++++++++---
1 file changed, 42 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
index dd2896a40ff0..de4bdacd83ac 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
@@ -4,7 +4,7 @@
$id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
-title: mediatek DPI Controller Device Tree Bindings
+title: mediatek DPI/DP_INTF Controller Device Tree Bindings
maintainers:
- CK Hu <ck.hu@mediatek.com>
@@ -13,7 +13,8 @@ maintainers:
description: |
The Mediatek DPI function block is a sink of the display subsystem and
provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a parallel
- output bus.
+ output bus. The Mediatek DP_INTF is a similar function block that is
+ connected to the (embedded) display port function block.
properties:
compatible:
@@ -23,6 +24,7 @@ properties:
- mediatek,mt8173-dpi
- mediatek,mt8183-dpi
- mediatek,mt8192-dpi
+ - mediatek,mt8195-dpintf
reg:
maxItems: 1
@@ -37,10 +39,11 @@ properties:
- description: DPI PLL
clock-names:
- items:
- - const: pixel
- - const: engine
- - const: pll
+ description:
+ For dpi clocks pixel, engine and pll are required. For dpintf pixel, pll,
+ pll_d2, pll_d4, pll_d8, pll_d16, hf_fmm, hf_fdp are required.
+ minItems: 3
+ maxItems: 8
pinctrl-0: true
pinctrl-1: true
@@ -64,6 +67,39 @@ required:
- clock-names
- port
+allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - mediatek,mt8195-dpintf
+ then:
+ properties:
+ clocks:
+ minItems: 8
+ maxItems: 8
+ clock-names:
+ items:
+ - const: pixel
+ - const: pll
+ - const: pll_d2
+ - const: pll_d4
+ - const: pll_d8
+ - const: pll_d16
+ - const: hf_fmm
+ - const: hf_fdp
+ else:
+ properties:
+ clocks:
+ minItems: 3
+ maxItems: 3
+ clock-names:
+ items:
+ - const: pixel
+ - const: engine
+ - const: pll
+
additionalProperties: false
examples:
--
2.32.0
next prev parent reply other threads:[~2021-08-16 19:27 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 19:25 [RFC PATCH 0/5] drm/mediatek: Add mt8195 DisplayPort driver Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann [this message]
2021-08-16 19:25 ` [RFC PATCH 1/5] dt-bindings: mediatek,dpi: Add mt8195 dpintf Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-18 4:45 ` CK Hu
2021-08-18 4:45 ` CK Hu
2021-08-18 4:45 ` CK Hu
2021-08-18 7:30 ` Markus Schneider-Pargmann
2021-08-18 7:30 ` Markus Schneider-Pargmann
2021-08-18 7:30 ` Markus Schneider-Pargmann
2021-08-16 19:25 ` [RFC PATCH 2/5] drm/mediatek: dpi: Add dpintf support Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-17 9:50 ` CK Hu
2021-08-17 9:50 ` CK Hu
2021-08-17 9:50 ` CK Hu
2021-08-18 7:26 ` Markus Schneider-Pargmann
2021-08-18 7:26 ` Markus Schneider-Pargmann
2021-08-18 7:26 ` Markus Schneider-Pargmann
2021-08-16 19:25 ` [RFC PATCH 3/5] drm/edid: Add cea_sad helpers for freq/length Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-16 19:25 ` [RFC PATCH 4/5] video/hdmi: Add audio_infoframe packing for DP Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-16 19:25 ` [RFC PATCH 5/5] drm/mediatek: Add mt8195 DisplayPort driver Markus Schneider-Pargmann
2021-08-16 19:25 ` Markus Schneider-Pargmann
2021-08-16 21:36 ` Sam Ravnborg
2021-08-16 21:36 ` Sam Ravnborg
2021-08-16 21:36 ` Sam Ravnborg
2021-08-17 7:31 ` Markus Schneider-Pargmann
2021-08-17 7:31 ` Markus Schneider-Pargmann
2021-08-17 7:31 ` Markus Schneider-Pargmann
2021-08-17 5:36 ` CK Hu
2021-08-17 5:36 ` CK Hu
2021-08-17 5:36 ` CK Hu
2021-08-17 7:35 ` Markus Schneider-Pargmann
2021-08-17 7:35 ` Markus Schneider-Pargmann
2021-08-17 7:35 ` Markus Schneider-Pargmann
2021-08-17 7:21 ` kernel test robot
2021-08-18 4:42 ` CK Hu
2021-08-18 4:42 ` CK Hu
2021-08-18 4:42 ` CK Hu
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=20210816192523.1739365-2-msp@baylibre.com \
--to=msp@baylibre.com \
--cc=chunkuang.hu@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=p.zabel@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.