From: Rob Herring <robh@kernel.org>
To: Markus Schneider-Pargmann <msp@baylibre.com>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Vinod Koul <vkoul@kernel.org>, Sam Ravnborg <sam@ravnborg.org>,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/7] dt-bindings: mediatek, dp: Add Display Port binding
Date: Mon, 11 Oct 2021 19:43:16 -0500 [thread overview]
Message-ID: <YWTaJOXGgF2bHznv@robh.at.kernel.org> (raw)
In-Reply-To: <20211011094624.3416029-3-msp@baylibre.com>
On Mon, Oct 11, 2021 at 11:46:19AM +0200, Markus Schneider-Pargmann wrote:
> 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>
> ---
> .../display/mediatek/mediatek,dp.yaml | 89 +++++++++++++++++++
> 1 file changed, 89 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..f7a35962c23b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dp.yaml
> @@ -0,0 +1,89 @@
> +# 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-edp_tx
> + - mediatek,mt8195-dp_tx
Are these blocks different?
> +
> + 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@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
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - ports
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/power/mt8195-power.h>
> + dp_tx: edp_tx@1c500000 {
> + compatible = "mediatek,mt8195-edp_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>;
> + status = "okay";
Don't show status in examples.
> +
> + 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>;
> + };
> + };
> + };
> + };
> --
> 2.33.0
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-12 0:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 9:46 [PATCH v4 0/7] drm/mediatek: Add mt8195 DisplayPort driver Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 1/7] dt-bindings: mediatek,dpintf: Add DP_INTF binding Markus Schneider-Pargmann
2021-10-11 13:36 ` Rob Herring
2021-10-11 13:43 ` Markus Schneider-Pargmann
2021-10-11 18:41 ` Rob Herring
2021-10-11 23:44 ` Rob Herring
2021-10-20 19:13 ` Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 2/7] dt-bindings: mediatek,dp: Add Display Port binding Markus Schneider-Pargmann
2021-10-11 13:36 ` [PATCH v4 2/7] dt-bindings: mediatek, dp: " Rob Herring
2021-10-11 13:44 ` Markus Schneider-Pargmann
2021-10-12 0:43 ` Rob Herring [this message]
2021-10-18 14:19 ` Markus Schneider-Pargmann
2021-10-18 19:38 ` Rob Herring
2021-10-20 19:34 ` Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 3/7] drm/edid: Add cea_sad helpers for freq/length Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 4/7] video/hdmi: Add audio_infoframe packing for DP Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 5/7] drm/mediatek: dpi: Add dpintf support Markus Schneider-Pargmann
2021-10-11 9:46 ` [PATCH v4 6/7] phy: phy-mtk-dp: Add driver for DP phy Markus Schneider-Pargmann
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=YWTaJOXGgF2bHznv@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=msp@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=sam@ravnborg.org \
--cc=vkoul@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).