[PATCH v10 02/21] dt-bindings: mediatek,dp: Add Display Port binding
AngeloGioacchino Del Regno
angelogioacchino.delregno at collabora.com
Wed May 25 08:30:33 PDT 2022
Il 23/05/22 12:47, Guillaume Ranquet ha scritto:
> From: Markus Schneider-Pargmann <msp at 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 at baylibre.com>
> Signed-off-by: Guillaume Ranquet <granquet at baylibre.com>
> ---
> .../display/mediatek/mediatek,dp.yaml | 99 +++++++++++++++++++
> 1 file changed, 99 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..36ae0a6df299
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml
> @@ -0,0 +1,99 @@
> +# 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 at mediatek.com>
> + - Jitao shi <jitao.shi at 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
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: faxi clock
> +
> + clock-names:
> + items:
> + - const: faxi
> +
> + power-domains:
> + maxItems: 1
> +
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> + properties:
> + port at 0:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: Input endpoint of the controller, usually dp_intf
> +
> + port at 1:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: Output endpoint of the controller
> +
You should add port at 0 (and port at 1, probably) as required... with what you've done
here, you're saying that "ports" is required, but you're allowing it to be empty..
ports:
$ref: /schemas/graph.yaml#/properties/ports
properties:
port at 0:
$ref: /schemas/graph.yaml#/properties/port
description: Input endpoint of the controller, usually dp_intf
port at 1:
$ref: /schemas/graph.yaml#/properties/port
description: Output endpoint of the controller
required:
- port at 0
- port at 1
^^^ that's how it should look.
> + max-lanes:
> + maxItems: 1
> + description: maximum number of lanes supported by the hardware
> +
> + max-linkrate:
> + maxItems: 1
> + description: maximum link rate supported by the hardware
As you've put it (in the example below), the max-linkrate property wants a value
that corresponds to what you find in the HW registers... this is wrong.
Devicetree bindings should be generic and devicetrees shouldn't have hardware
specific bits inside, hence, please change this property to accept a link rate
specified in Mbps and also specify that in the description.
Thanks,
Angelo
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - ports
> + - max-lanes
> + - max-linkrate
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/power/mt8195-power.h>
> + edp_tx: edp_tx at 1c500000 {
> + compatible = "mediatek,mt8195-dp-tx";
> + 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>;
> + max-lanes = /bits/ 8 <4>;
> + max-linkrate = /bits/ 8 <0x1e>;
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port at 0 {
> + reg = <0>;
> + edp_in: endpoint {
> + remote-endpoint = <&dp_intf0_out>;
> + };
> + };
> + port at 1 {
> + reg = <1>;
> + edp_out: endpoint {
> + remote-endpoint = <&panel_in>;
> + };
> + };
> + };
> + };
More information about the linux-arm-kernel
mailing list