From: Shawn Guo <shawnguo@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8mp: Add TC9595 bridge on DH electronics i.MX8M Plus DHCOM
Date: Sat, 27 May 2023 16:35:15 +0800 [thread overview]
Message-ID: <20230527083515.GE528183@dragon> (raw)
In-Reply-To: <20230515162424.67597-1-marex@denx.de>
On Mon, May 15, 2023 at 06:24:24PM +0200, Marek Vasut wrote:
> Add TC9595 DSI-to-DPI and DSI-to-(e)DP bridge to
> DH electronics i.MX8M Plus DHCOM SoM . The bridge
> is populated on the SoM, but disabled by default
> unless used for display output.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Fabio Estevam <festevam@gmail.com>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> Cc: NXP Linux Team <linux-imx@nxp.com>
> Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Sascha Hauer <s.hauer@pengutronix.de>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: devicetree@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> ---
> .../boot/dts/freescale/imx8mp-dhcom-som.dtsi | 55 +++++++++++++++++++
> 1 file changed, 55 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-dhcom-som.dtsi b/arch/arm64/boot/dts/freescale/imx8mp-dhcom-som.dtsi
> index 98a11c31d7d45..9c0cb75386e36 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp-dhcom-som.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-dhcom-som.dtsi
> @@ -240,6 +240,36 @@ &i2c3 {
> sda-gpios = <&gpio5 19 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> status = "okay";
>
> + tc_bridge: bridge@f {
> + compatible = "toshiba,tc9595", "toshiba,tc358767";
Is "toshiba,tc9595" documented?
Shawn
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_tc9595>;
> + reg = <0xf>;
> + clock-names = "ref";
> + clocks = <&clk IMX8MP_CLK_CLKOUT2>;
> + assigned-clocks = <&clk IMX8MP_CLK_CLKOUT2_SEL>,
> + <&clk IMX8MP_CLK_CLKOUT2>,
> + <&clk IMX8MP_AUDIO_PLL2_OUT>;
> + assigned-clock-parents = <&clk IMX8MP_AUDIO_PLL2_OUT>;
> + assigned-clock-rates = <13000000>, <13000000>, <156000000>;
> + reset-gpios = <&gpio3 21 GPIO_ACTIVE_HIGH>;
> + status = "disabled";
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> +
> + tc_bridge_in: endpoint {
> + data-lanes = <1 2 3 4>;
> + remote-endpoint = <&dsi_out>;
> + };
> + };
> + };
> + };
> +
> pmic: pmic@25 {
> compatible = "nxp,pca9450c";
> reg = <0x25>;
> @@ -406,6 +436,22 @@ &i2c5 { /* HDMI EDID bus */
> status = "okay";
> };
>
> +&mipi_dsi {
> + samsung,burst-clock-frequency = <160000000>;
> + samsung,esc-clock-frequency = <10000000>;
> +
> + ports {
> + port@1 {
> + reg = <1>;
> +
> + dsi_out: endpoint {
> + data-lanes = <1 2 3 4>;
> + remote-endpoint = <&tc_bridge_in>;
> + };
> + };
> + };
> +};
> +
> &pwm1 {
> pinctrl-0 = <&pinctrl_pwm1>;
> pinctrl-names = "default";
> @@ -880,6 +926,15 @@ MX8MP_IOMUXC_SAI3_TXD__AUDIOMIX_SAI3_TX_DATA00 0xd6
> >;
> };
>
> + pinctrl_tc9595: dhcom-tc9595-grp {
> + fsl,pins = <
> + /* RESET_DSIBRIDGE */
> + MX8MP_IOMUXC_SAI1_RXC__GPIO4_IO01 0x40000146
> + /* DSI-CONV_INT Interrupt */
> + MX8MP_IOMUXC_SAI5_RXD0__GPIO3_IO21 0x141
> + >;
> + };
> +
> pinctrl_touch: dhcom-touch-grp {
> fsl,pins = <
> /* #TOUCH_INT */
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-05-27 8:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 16:24 [PATCH] arm64: dts: imx8mp: Add TC9595 bridge on DH electronics i.MX8M Plus DHCOM Marek Vasut
2023-05-23 11:17 ` Alexander Stein
2023-05-23 13:10 ` Marek Vasut
2023-05-24 6:49 ` Alexander Stein
2023-05-24 9:28 ` Marek Vasut
2023-05-24 10:24 ` Alexander Stein
2023-05-24 10:37 ` Marek Vasut
2023-05-26 12:52 ` Alexander Stein
2023-05-27 8:35 ` Shawn Guo [this message]
2023-05-27 10:19 ` Marek Vasut
2023-05-27 10:47 ` Shawn Guo
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=20230527083515.GE528183@dragon \
--to=shawnguo@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).