On 25/03/2022 18:14, Guillaume Ranquet 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 Reviewed-by: Rob Herring robh@kernel.org
.../display/mediatek/mediatek,dp.yaml | 97 +++++++++++++++++++ 1 file changed, 97 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..74db5c4e0f73 --- /dev/null +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml @@ -0,0 +1,97 @@ +# 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:
- CK Hu ck.hu@mediatek.com
- Jitao shi jitao.shi@mediatek.com
+description: |
- Device tree bindings for the Mediatek (embedded) Display Port controller
- present on some Mediatek SoCs.
+properties:
- compatible:
- enum:
- mediatek,mt8195-dp-tx
- syscon
This is wrong, should be a list. Are you sure you got Rob's review? I see now v8 with his Reviewed-by tag, but without syscon, so he looked at something else.
Please drop his tag and please test your changes. This would be easily spotted with dt_binding_check.
- reg:
- maxItems: 1
- interrupts:
- maxItems: 1
- clocks:
- items:
- description: faxi clock
- clock-names:
- items:
- const: faxi
- phys:
- maxItems: 1
- phy-names:
- items:
- const: dp
- power-domains:
- maxItems: 1
- ports:
- $ref: /schemas/graph.yaml#/properties/ports
- properties:
port@0:
$ref: /schemas/graph.yaml#/properties/port
description: Input endpoint of the controller, usually dp_intf
port@1:
$ref: /schemas/graph.yaml#/properties/port
description: Output endpoint of the controller
None of the ports are required?
+required:
- compatible
- reg
- interrupts
- ports
+additionalProperties: false
+examples:
- |
- #include <dt-bindings/interrupt-controller/arm-gic.h>
- #include <dt-bindings/power/mt8195-power.h>
- edp_tx: edp_tx@1c500000 {
generic node name, so I guess "dp" as display-port.
compatible = "mediatek,mt8195-dp-tx","syscon";
reg = <0 0x1c500000 0 0x8000>;
interrupts = <GIC_SPI 676 IRQ_TYPE_LEVEL_HIGH 0>;
power-domains = <&spm MT8195_POWER_DOMAIN_EPD_TX>;
pinctrl-names = "default";
pinctrl-0 = <&edp_pin>;
phys = <&dp_phy>;
phy-names = "dp";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
edp_in: endpoint {
remote-endpoint = <&dp_intf0_out>;
};
};
port@1 {
reg = <1>;
edp_out: endpoint {
remote-endpoint = <&panel_in>;
};
};
};
- };
Best regards, Krzysztof