From: Frank Li <Frank.li@oss.nxp.com>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux@ew.tq-group.com
Subject: Re: [PATCH 1/8] ARM: dts: imx6ul: Add LVDS DT overlay for TQMa6ULx
Date: Fri, 2 Oct 2026 09:37:17 -0500 [thread overview]
Message-ID: <ar_BnRDhyiMpUs_T@SMW015318> (raw)
In-Reply-To: <20261002081417.2092471-2-alexander.stein@ew.tq-group.com>
On Fri, Oct 02, 2026 at 10:14:02AM +0200, Alexander Stein wrote:
> The generic setup like pinmux and lcdif <-> display connection is done
> in the mainboard while LVDS specific setup is done in the overlay.
> As this mainboard also supports parallel display the LVDS connection
> using an LVDS encoder is done in the overlay.
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> arch/arm/boot/dts/nxp/imx/Makefile | 4 ++
> ...6ul-tqma6ul2-mba6ulx-lvds-tm070jvhg33.dtso | 69 +++++++++++++++++++
> arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi | 64 +++++++++++++++++
> 3 files changed, 137 insertions(+)
> create mode 100644 arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ul2-mba6ulx-lvds-tm070jvhg33.dtso
>
> diff --git a/arch/arm/boot/dts/nxp/imx/Makefile b/arch/arm/boot/dts/nxp/imx/Makefile
> index c5caca92ea10c..ea0799ba1893e 100644
> --- a/arch/arm/boot/dts/nxp/imx/Makefile
> +++ b/arch/arm/boot/dts/nxp/imx/Makefile
> @@ -420,6 +420,10 @@ dtb-$(CONFIG_SOC_IMX6UL) += \
> imx6ulz-14x14-evk.dtb \
> imx6ulz-bsh-smm-m2.dtb
>
> +imx6ul-tqma6ul2-mba6ulx-lvds-tm070jvhg33-dtbs += imx6ul-tqma6ul2-mba6ulx.dtb imx6ul-tqma6ul2-mba6ulx-lvds-tm070jvhg33.dtbo
> +
> +dtb-$(CONFIG_SOC_IMX6UL) += imx6ul-tqma6ul2-mba6ulx-lvds-tm070jvhg33.dtb
> +
> imx7d-colibri-emmc-aster-panel-cap-touch-7inch-parallel-dtbs := \
> imx7d-colibri-emmc-aster.dtb \
> imx7d-colibri-emmc-panel-cap-touch-7inch-parallel.dtbo
> diff --git a/arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ul2-mba6ulx-lvds-tm070jvhg33.dtso b/arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ul2-mba6ulx-lvds-tm070jvhg33.dtso
> new file mode 100644
> index 0000000000000..e44b7461001ea
> --- /dev/null
> +++ b/arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ul2-mba6ulx-lvds-tm070jvhg33.dtso
> @@ -0,0 +1,69 @@
> +// SPDX-License-Identifier: (GPL-2.0-or-later OR MIT)
> +/*
> + * Copyright 2018-2026 TQ-Systems GmbH <linux@ew.tq-group.com>,
> + * D-82229 Seefeld, Germany.
> + * Author: Markus Niebel
> + * Author: Alexander Stein
> + */
> +
> +/dts-v1/;
> +/plugin/;
> +
> +#include <dt-bindings/gpio/gpio.h>
> +
> +&{/} {
> + lvds_encoder: lvds-encoder {
> + compatible = "ti,sn75lvds83", "lvds-encoder";
Can you check if shared one overlay files with
ls1021a-tqmls1021a-mbls1021a-lvds-tm070jvhg33.dtso
I suppose use the model between two boards.
You use two labels like
reg_lvds: reg_mba6ul_3v3: regulator { ... } to create unified label naming
for regulator.
GPIO can use nexus node to do mapping.
https://lore.kernel.org/imx/20261001-verdin-imx8mp-hmp-camera-ready-v2-3-7d1343ecd3ec@toradex.com/
Frank
> + powerdown-gpios = <&expander_out0 3 GPIO_ACTIVE_LOW>;
> + power-supply = <®_mba6ul_3v3>;
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@0 {
> + reg = <0>;
> +
> + lvds_encoder_in: endpoint {
> + remote-endpoint = <&lcdif_out>;
> + };
> + };
> +
> + port@1 {
> + reg = <1>;
> +
> + lvds_encoder_out: endpoint {
> + remote-endpoint = <&display_in>;
> + };
> + };
> + };
> + };
> +};
> +
> +&backlight {
> + pwms = <&pwm2 0 62500 0>;
> + brightness-levels = <0 16 32 64 96 128 160 192 224 255>;
> + default-brightness-level = <5>;
> + status = "okay";
> +};
> +
> +&display {
> + compatible = "tianma,tm070jvhg33";
> + power-supply = <®_mba6ul_5v0>;
> + status = "okay";
> +};
> +
> +&display_in {
> + remote-endpoint = <&lvds_encoder_out>;
> +};
> +
> +/* for lcd reset != #stkrst */
> +/* place r2021, resolder r2022 and iomux following: */
> +/* MX6UL_PAD_LCD_RESET__GPIO3_IO04 0x79 */
> +&lcdif {
> + status = "okay";
> +};
> +
> +&lcdif_out {
> + remote-endpoint = <&lvds_encoder_in>;
> +};
> diff --git a/arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi b/arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi
> index fd05479bbffc9..ba79bb9760806 100644
> --- a/arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi
> +++ b/arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi
> @@ -30,6 +30,21 @@ beeper: beeper {
> gpios = <&expander_out1 6 GPIO_ACTIVE_HIGH>;
> };
>
> + display: display {
> + /*
> + * Display is not fixed, so compatible has to be added from
> + * DT overlay
> + */
> + backlight = <&backlight>;
> + status = "disabled";
> +
> + port {
> + display_in: endpoint {
> + remote-endpoint = <&lcdif_out>;
> + };
> + };
> + };
> +
> gpio_buttons: gpio-keys {
> compatible = "gpio-keys";
> pinctrl-names = "default";
> @@ -299,6 +314,17 @@ se97b: eeprom@51 {
> };
> };
>
> +&lcdif {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_lcdif>, <&pinctrl_lcdifctrl>;
> +
> + port {
> + lcdif_out: endpoint {
> + remote-endpoint = <&display_in>;
> + };
> + };
> +};
> +
> &pwm2 {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_pwm2>;
> @@ -466,6 +492,44 @@ MX6UL_PAD_UART2_CTS_B__FLEXCAN2_TX 0x1b020
> >;
> };
>
> + pinctrl_lcdif: lcdifgrp {
> + fsl,pins = <
> + MX6UL_PAD_LCD_DATA00__LCDIF_DATA00 0x79
> + MX6UL_PAD_LCD_DATA01__LCDIF_DATA01 0x79
> + MX6UL_PAD_LCD_DATA02__LCDIF_DATA02 0x79
> + MX6UL_PAD_LCD_DATA03__LCDIF_DATA03 0x79
> + MX6UL_PAD_LCD_DATA04__LCDIF_DATA04 0x79
> + MX6UL_PAD_LCD_DATA05__LCDIF_DATA05 0x79
> + MX6UL_PAD_LCD_DATA06__LCDIF_DATA06 0x79
> + MX6UL_PAD_LCD_DATA07__LCDIF_DATA07 0x79
> + MX6UL_PAD_LCD_DATA08__LCDIF_DATA08 0x79
> + MX6UL_PAD_LCD_DATA09__LCDIF_DATA09 0x79
> + MX6UL_PAD_LCD_DATA10__LCDIF_DATA10 0x79
> + MX6UL_PAD_LCD_DATA11__LCDIF_DATA11 0x79
> + MX6UL_PAD_LCD_DATA12__LCDIF_DATA12 0x79
> + MX6UL_PAD_LCD_DATA13__LCDIF_DATA13 0x79
> + MX6UL_PAD_LCD_DATA14__LCDIF_DATA14 0x79
> + MX6UL_PAD_LCD_DATA15__LCDIF_DATA15 0x79
> + MX6UL_PAD_LCD_DATA16__LCDIF_DATA16 0x79
> + MX6UL_PAD_LCD_DATA17__LCDIF_DATA17 0x79
> + MX6UL_PAD_LCD_DATA18__LCDIF_DATA18 0x79
> + MX6UL_PAD_LCD_DATA19__LCDIF_DATA19 0x79
> + MX6UL_PAD_LCD_DATA20__LCDIF_DATA20 0x79
> + MX6UL_PAD_LCD_DATA21__LCDIF_DATA21 0x79
> + MX6UL_PAD_LCD_DATA22__LCDIF_DATA22 0x79
> + MX6UL_PAD_LCD_DATA23__LCDIF_DATA23 0x79
> + >;
> + };
> +
> + pinctrl_lcdifctrl: lcdifctrlgrp {
> + fsl,pins = <
> + MX6UL_PAD_LCD_CLK__LCDIF_CLK 0x79
> + MX6UL_PAD_LCD_ENABLE__LCDIF_ENABLE 0x79
> + MX6UL_PAD_LCD_HSYNC__LCDIF_HSYNC 0x79
> + MX6UL_PAD_LCD_VSYNC__LCDIF_VSYNC 0x79
> + >;
> + };
> +
> pinctrl_pwm2: pwm2grp {
> fsl,pins = <
> /* 100 k PD, DSE 120 OHM, SPEED LO */
> --
> 2.55.0
>
>
next prev parent reply other threads:[~2026-10-02 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 8:14 [PATCH 0/8] Display support for TQMa6UL[L]x Alexander Stein
2026-10-02 8:14 ` [PATCH 1/8] ARM: dts: imx6ul: Add LVDS DT overlay for TQMa6ULx Alexander Stein
2026-10-02 14:37 ` Frank Li [this message]
2026-10-02 8:14 ` [PATCH 2/8] ARM: dts: imx6ul: Add LVDS DT overlay for TQMa6ULxL Alexander Stein
2026-10-02 8:14 ` [PATCH 3/8] ARM: dts: imx6ull: Add LVDS DT overlay for TQMa6ULLx Alexander Stein
2026-10-02 8:14 ` [PATCH 4/8] ARM: dts: imx6ull: Add LVDS DT overlay for TQMa6ULLxL Alexander Stein
2026-10-02 8:14 ` [PATCH 5/8] ARM: dts: imx6ul: Add parallel display DT overlay for TQMa6ULx Alexander Stein
2026-10-02 8:14 ` [PATCH 6/8] ARM: dts: imx6ul: Add parallel display DT overlay for TQMa6ULxL Alexander Stein
2026-10-02 8:14 ` [PATCH 7/8] ARM: dts: imx6ull: Add parallel display DT overlay for TQMa6ULLx Alexander Stein
2026-10-02 8:14 ` [PATCH 8/8] ARM: dts: imx6ull: Add parallel display DT overlay for TQMa6ULLxL Alexander Stein
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=ar_BnRDhyiMpUs_T@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=robh@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
all inboxes | Powered by JetHome®