From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Alexandre Mergnat" <amergnat@baylibre.com>,
"Chun-Kuang Hu" <chunkuang.hu@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Jitao Shi" <jitao.shi@mediatek.com>,
"CK Hu" <ck.hu@mediatek.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>
Cc: dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pwm@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 18/18] arm64: dts: mediatek: add display support for mt8365-evk
Date: Wed, 17 Apr 2024 12:27:57 +0200 [thread overview]
Message-ID: <ee8d0a32-b4fb-4fc4-83b2-300f7453d95f@collabora.com> (raw)
In-Reply-To: <20231023-display-support-v2-18-33ce8864b227@baylibre.com>
Il 16/04/24 17:53, Alexandre Mergnat ha scritto:
> MIPI DSI:
> - Add "vsys_lcm_reg" regulator support and setup the "mt6357_vsim1_reg",
> to power the pannel plugged to the DSI connector.
> - Setup the Display Parallel Interface.
> - Add the startek kd070fhfid015 pannel support.
>
> HDMI:
> - Add HDMI connector support.
> - Add the "ite,it66121" HDMI bridge support, driven by I2C1.
> - Setup the Display Parallel Interface.
>
> Signed-off-by: Alexandre Mergnat <amergnat@baylibre.com>
> ---
> arch/arm64/boot/dts/mediatek/mt8365-evk.dts | 182 ++++++++++++++++++++++++++++
> 1 file changed, 182 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8365-evk.dts b/arch/arm64/boot/dts/mediatek/mt8365-evk.dts
> index 50cbaefa1a99..4afdcbefc481 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8365-evk.dts
> +++ b/arch/arm64/boot/dts/mediatek/mt8365-evk.dts
> @@ -26,6 +26,18 @@ chosen {
> stdout-path = "serial0:921600n8";
> };
>
> + connector {
> + compatible = "hdmi-connector";
> + label = "hdmi";
> + type = "d";
> +
> + port {
> + hdmi_connector_in: endpoint {
> + remote-endpoint = <&hdmi_connector_out>;
> + };
> + };
> + };
> +
> firmware {
> optee {
> compatible = "linaro,optee-tz";
> @@ -86,6 +98,56 @@ optee_reserved: optee@43200000 {
> reg = <0 0x43200000 0 0x00c00000>;
> };
> };
> +
> + vsys_lcm_reg: regulator-vsys-lcm {
> + compatible = "regulator-fixed";
> + enable-active-high;
> + gpio = <&pio 129 GPIO_ACTIVE_HIGH>;
> + regulator-max-microvolt = <5000000>;
> + regulator-min-microvolt = <5000000>;
> + regulator-name = "vsys_lcm";
> + };
> +};
> +
> +&dpi0 {
> + pinctrl-0 = <&dpi_default_pins>;
> + pinctrl-1 = <&dpi_idle_pins>;
> + pinctrl-names = "default", "sleep";
> + status = "okay";
> +
> + port {
> + dpi_out: endpoint {
> + remote-endpoint = <&it66121_in>;
> + };
> + };
> +};
> +
> +&dsi0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + status = "okay";
> +
> + panel@0 {
> + compatible = "startek,kd070fhfid015";
> + status = "okay";
status is always okay, unless it's disabled.
> + reg = <0>;
> + enable-gpios = <&pio 67 GPIO_ACTIVE_HIGH>;
> + reset-gpios = <&pio 20 GPIO_ACTIVE_HIGH>;
> + iovcc-supply = <&mt6357_vsim1_reg>;
> + power-supply = <&vsys_lcm_reg>;
> +
> + port {
> + panel_in: endpoint {
> + remote-endpoint = <&dsi_out>;
> + };
> + };
> + };
> +
> + port {
> + dsi_out: endpoint {
> + remote-endpoint = <&panel_in>;
> + };
> + };
> };
>
> &cpu0 {
> @@ -138,6 +200,50 @@ &i2c0 {
> status = "okay";
> };
>
> +&i2c1 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + clock-div = <2>;
> + clock-frequency = <100000>;
> + pinctrl-0 = <&i2c1_pins>;
> + pinctrl-names = "default";
> + status = "okay";
> +
> + it66121hdmitx: it66121hdmitx@4c {
Can we please get an actually readable name for this node?
Just a suggestion (you're free to rename however you want)
it66121_hdmi: hdmi@4c {
> + #sound-dai-cells = <0>;
> + compatible = "ite,it66121";
> + interrupt-parent = <&pio>;
> + interrupts = <68 IRQ_TYPE_LEVEL_LOW>;
> + pinctrl-0 = <&ite_pins>;
> + pinctrl-names = "default";
> + reg = <0x4c>;
> + reset-gpios = <&pio 69 GPIO_ACTIVE_LOW>;
> + vcn18-supply = <&mt6357_vsim2_reg>;
> + vcn33-supply = <&mt6357_vibr_reg>;
> + vrf12-supply = <&mt6357_vrf12_reg>;
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> + it66121_in: endpoint {
> + bus-width = <12>;
> + remote-endpoint = <&dpi_out>;
> + };
> + };
> +
> + port@1 {
> + reg = <1>;
> + hdmi_connector_out: endpoint {
> + remote-endpoint = <&hdmi_connector_in>;
> + };
> + };
> + };
> + };
> +};
> +
> &mmc0 {
> assigned-clock-parents = <&topckgen CLK_TOP_MSDCPLL>;
> assigned-clocks = <&topckgen CLK_TOP_MSDC50_0_SEL>;
> @@ -180,7 +286,55 @@ &mt6357_pmic {
> #interrupt-cells = <2>;
> };
>
> +&mt6357_vsim1_reg {
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> +};
> +
> &pio {
> + dpi_default_pins: dpi-default-pins {
> + pins {
> + pinmux = <MT8365_PIN_0_GPIO0__FUNC_DPI_D0>,
> + <MT8365_PIN_1_GPIO1__FUNC_DPI_D1>,
> + <MT8365_PIN_2_GPIO2__FUNC_DPI_D2>,
> + <MT8365_PIN_3_GPIO3__FUNC_DPI_D3>,
> + <MT8365_PIN_4_GPIO4__FUNC_DPI_D4>,
> + <MT8365_PIN_5_GPIO5__FUNC_DPI_D5>,
> + <MT8365_PIN_6_GPIO6__FUNC_DPI_D6>,
> + <MT8365_PIN_7_GPIO7__FUNC_DPI_D7>,
> + <MT8365_PIN_8_GPIO8__FUNC_DPI_D8>,
> + <MT8365_PIN_9_GPIO9__FUNC_DPI_D9>,
> + <MT8365_PIN_10_GPIO10__FUNC_DPI_D10>,
> + <MT8365_PIN_11_GPIO11__FUNC_DPI_D11>,
> + <MT8365_PIN_12_GPIO12__FUNC_DPI_DE>,
> + <MT8365_PIN_13_GPIO13__FUNC_DPI_VSYNC>,
> + <MT8365_PIN_14_GPIO14__FUNC_DPI_CK>,
> + <MT8365_PIN_15_GPIO15__FUNC_DPI_HSYNC>;
> + drive-strength = <MTK_DRIVE_4mA>;
drive-strength = <4> is just fine....! :-)
> + };
> + };
> +
> + dpi_idle_pins: dpi-idle-pins {
> + pins {
> + pinmux = <MT8365_PIN_0_GPIO0__FUNC_GPIO0>,
> + <MT8365_PIN_1_GPIO1__FUNC_GPIO1>,
> + <MT8365_PIN_2_GPIO2__FUNC_GPIO2>,
> + <MT8365_PIN_3_GPIO3__FUNC_GPIO3>,
> + <MT8365_PIN_4_GPIO4__FUNC_GPIO4>,
> + <MT8365_PIN_5_GPIO5__FUNC_GPIO5>,
> + <MT8365_PIN_6_GPIO6__FUNC_GPIO6>,
> + <MT8365_PIN_7_GPIO7__FUNC_GPIO7>,
> + <MT8365_PIN_8_GPIO8__FUNC_GPIO8>,
> + <MT8365_PIN_9_GPIO9__FUNC_GPIO9>,
> + <MT8365_PIN_10_GPIO10__FUNC_GPIO10>,
> + <MT8365_PIN_11_GPIO11__FUNC_GPIO11>,
> + <MT8365_PIN_12_GPIO12__FUNC_GPIO12>,
> + <MT8365_PIN_13_GPIO13__FUNC_GPIO13>,
> + <MT8365_PIN_14_GPIO14__FUNC_GPIO14>,
> + <MT8365_PIN_15_GPIO15__FUNC_GPIO15>;
> + };
> + };
> +
> ethernet_pins: ethernet-pins {
> phy_reset_pins {
> pinmux = <MT8365_PIN_133_TDM_TX_DATA1__FUNC_GPIO133>;
> @@ -222,6 +376,34 @@ pins {
> };
> };
>
> + i2c1_pins: i2c1-pins {
> + pins {
> + pinmux = <MT8365_PIN_59_SDA1__FUNC_SDA1_0>,
> + <MT8365_PIN_60_SCL1__FUNC_SCL1_0>;
> + bias-pull-up;
> + };
> + };
> +
> + ite_pins: ite-pins {
> +
extra blank line, please remove.
> + irq_ite_pins {
Did you run dtbs_check?!? :-)
Cheers,
Angelo
> + pinmux = <MT8365_PIN_68_CMDAT0__FUNC_GPIO68>;
> + input-enable;
> + bias-pull-up;
> + };
> +
> + pwr_pins {
> + pinmux = <MT8365_PIN_70_CMDAT2__FUNC_GPIO70>,
> + <MT8365_PIN_71_CMDAT3__FUNC_GPIO71>;
> + output-high;
> + };
> +
> + rst_ite_pins {
> + pinmux = <MT8365_PIN_69_CMDAT1__FUNC_GPIO69>;
> + output-high;
> + };
> + };
> +
> mmc0_default_pins: mmc0-default-pins {
> clk-pins {
> pinmux = <MT8365_PIN_99_MSDC0_CLK__FUNC_MSDC0_CLK>;
>
next prev parent reply other threads:[~2024-04-17 10:28 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 15:53 [PATCH v2 00/18] Add display support for the MT8365-EVK board Alexandre Mergnat
2024-04-16 15:53 ` [PATCH v2 01/18] dt-bindings: display: mediatek: aal: add compatible for MT8365 SoC Alexandre Mergnat
2024-04-17 10:19 ` AngeloGioacchino Del Regno
2024-04-17 18:43 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 02/18] dt-bindings: display: mediatek: ccorr: " Alexandre Mergnat
2024-04-17 10:19 ` AngeloGioacchino Del Regno
2024-04-17 18:43 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 03/18] dt-bindings: display: mediatek: color: " Alexandre Mergnat
2024-04-17 10:19 ` AngeloGioacchino Del Regno
2024-04-17 18:43 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 04/18] dt-bindings: display: mediatek: dither: " Alexandre Mergnat
2024-04-17 10:19 ` AngeloGioacchino Del Regno
2024-04-17 18:43 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 05/18] dt-bindings: display: mediatek: dsi: " Alexandre Mergnat
2024-04-17 10:21 ` AngeloGioacchino Del Regno
2024-04-17 18:44 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 06/18] dt-bindings: display: mediatek: dpi: add power-domains property amergnat
2024-04-17 10:15 ` AngeloGioacchino Del Regno
2024-04-17 18:44 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 07/18] dt-bindings: display: mediatek: dpi: add compatible for MT8365 Alexandre Mergnat
2024-04-17 10:14 ` AngeloGioacchino Del Regno
2024-04-16 15:53 ` [PATCH v2 08/18] dt-bindings: display: mediatek: gamma: add compatible for MT8365 SoC Alexandre Mergnat
2024-04-17 10:19 ` AngeloGioacchino Del Regno
2024-04-17 18:47 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 09/18] dt-bindings: display: mediatek: ovl: " Alexandre Mergnat
2024-04-17 10:19 ` AngeloGioacchino Del Regno
2024-04-17 18:47 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 10/18] dt-bindings: display: mediatek: rdma: " Alexandre Mergnat
2024-04-17 10:19 ` AngeloGioacchino Del Regno
2024-04-17 18:48 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 11/18] dt-bindings: pwm: mediatek,pwm-disp: add power-domains property Alexandre Mergnat
2024-04-17 8:01 ` Uwe Kleine-König
2024-04-17 8:06 ` Alexandre Mergnat
2024-04-17 10:19 ` AngeloGioacchino Del Regno
2024-04-17 13:25 ` Uwe Kleine-König
2024-04-17 13:50 ` AngeloGioacchino Del Regno
2024-04-16 15:53 ` [PATCH v2 12/18] dt-bindings: pwm: mediatek,pwm-disp: add compatible for mt8365 SoC Alexandre Mergnat
2024-04-17 8:06 ` Uwe Kleine-König
2024-04-18 9:46 ` Alexandre Mergnat
2024-04-18 16:05 ` Uwe Kleine-König
2024-04-17 18:48 ` Rob Herring
2024-04-16 15:53 ` [PATCH v2 13/18] drm/mediatek: dsi: Improves the DSI lane setup robustness Alexandre Mergnat
2024-04-16 15:53 ` [PATCH v2 14/18] drm/mediatek: add mt8365 dpi support Alexandre Mergnat
2024-04-17 10:14 ` AngeloGioacchino Del Regno
2024-04-16 15:53 ` [PATCH v2 15/18] drm/mediatek: add MT8365 SoC support amergnat
2024-04-16 15:53 ` [PATCH v2 16/18] arm64: defconfig: enable display connector support Alexandre Mergnat
2024-04-16 15:53 ` [PATCH v2 17/18] arm64: dts: mediatek: add display blocks support for the MT8365 SoC Alexandre Mergnat
2024-04-17 10:27 ` AngeloGioacchino Del Regno
2024-04-16 15:53 ` [PATCH v2 18/18] arm64: dts: mediatek: add display support for mt8365-evk Alexandre Mergnat
2024-04-17 10:27 ` AngeloGioacchino Del Regno [this message]
2024-04-18 13:02 ` Alexandre Mergnat
2024-04-17 7:58 ` [PATCH v2 00/18] Add display support for the MT8365-EVK board Uwe Kleine-König
2024-04-17 8:12 ` Alexandre Mergnat
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=ee8d0a32-b4fb-4fc4-83b2-300f7453d95f@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=airlied@gmail.com \
--cc=amergnat@baylibre.com \
--cc=catalin.marinas@arm.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jitao.shi@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=will@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).