On Fri, Jun 10, 2022 at 06:55:13PM +0800, Bo-Chen Chen wrote:
From: Markus Schneider-Pargmann msp@baylibre.com
This controller is present on several mediatek hardware. Currently mt8195 and mt8395 have this controller without a functional difference, so only one compatible field is added.
The controller can have two forms, as a normal display port and as an embedded display port.
Signed-off-by: Markus Schneider-Pargmann msp@baylibre.com Signed-off-by: Guillaume Ranquet granquet@baylibre.com [Bo-Chen: Fix reviewers' comment] Signed-off-by: Bo-Chen Chen rex-bc.chen@mediatek.com
.../display/mediatek/mediatek,dp.yaml | 101 ++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml new file mode 100644 index 000000000000..10f50a0dcf49 --- /dev/null +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml @@ -0,0 +1,101 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/mediatek/mediatek,dp.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml#
+title: MediaTek Display Port Controller
+maintainers:
- Chun-Kuang Hu chunkuang.hu@kernel.org
- Jitao shi jitao.shi@mediatek.com
+description: |
- Device tree bindings for the MediaTek display port and
- embedded display port controller present on some MediaTek SoCs.
+properties:
- compatible:
- enum:
- mediatek,mt8195-dp-tx- mediatek,mt8195-edp-tx- reg:
- maxItems: 1
- nvmem-cells:
- maxItems: 1
- description: efuse data for display port calibration
- nvmem-cell-names:
- const: dp_calibration_data
- power-domains:
- maxItems: 1
- interrupts:
- maxItems: 1
- ports:
- $ref: /schemas/graph.yaml#/properties/ports
- properties:
port@0:$ref: /schemas/graph.yaml#/properties/portdescription: Input endpoint of the controller, usually dp_intfport@1:$ref: /schemas/graph.yaml#/properties/portdescription: Output endpoint of the controller- required:
- port@0- port@1- max-lanes:
- maxItems: 1
- description: maximum number of lanes supported by the hardware.
We already have a 'data-lanes' property defined in 'video-interfaces.yaml' that can serve this purpose.
- max-linkrate:
- maxItems: 1
- description: maximum link rate supported by the hardware and unit is MHz.
Then use '-mhz' suffix on the property name. Then you don't need a type (or maxItems).