From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Markus Niebel <Markus.Niebel@tq-group.com>
Subject: Re: [PATCH 2/2] arm64: dts: freescale: add initial device tree for TQMa8MPQL with i.MX8MP
Date: Thu, 16 Jun 2022 07:26:42 -0700 [thread overview]
Message-ID: <e039bef3-3fc4-e11e-9dcd-fe3a764edf3b@linaro.org> (raw)
In-Reply-To: <20220616142221.3986670-3-alexander.stein@ew.tq-group.com>
On 16/06/2022 07:22, Alexander Stein wrote:
> This adds support for TQMa8MPQL module on MBa8MPxL board.
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> arch/arm64/boot/dts/freescale/Makefile | 1 +
> .../freescale/imx8mp-tqma8mpql-mba8mpxl.dts | 689 ++++++++++++++++++
> .../boot/dts/freescale/imx8mp-tqma8mpql.dtsi | 284 ++++++++
> 3 files changed, 974 insertions(+)
> create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-tqma8mpql-mba8mpxl.dts
> create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-tqma8mpql.dtsi
>
> diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile
> index c288bda8aa36..ab8e61d4dd7c 100644
> --- a/arch/arm64/boot/dts/freescale/Makefile
> +++ b/arch/arm64/boot/dts/freescale/Makefile
> @@ -82,6 +82,7 @@ dtb-$(CONFIG_ARCH_MXC) += imx8mn-venice-gw7902.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx8mp-evk.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx8mp-icore-mx8mp-edimm2.2.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx8mp-phyboard-pollux-rdk.dtb
> +dtb-$(CONFIG_ARCH_MXC) += imx8mp-tqma8mpql-mba8mpxl.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx8mp-venice-gw74xx.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx8mp-verdin-nonwifi-dahlia.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx8mp-verdin-nonwifi-dev.dtb
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-tqma8mpql-mba8mpxl.dts b/arch/arm64/boot/dts/freescale/imx8mp-tqma8mpql-mba8mpxl.dts
> new file mode 100644
> index 000000000000..e9755bd7619c
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-tqma8mpql-mba8mpxl.dts
> @@ -0,0 +1,689 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
> +/*
> + * Copyright 2021-2022 TQ-Systems GmbH
> + * Author: Alexander Stein <alexander.stein@tq-group.com>
> + */
> +
> +/dts-v1/;
> +
> +#include <dt-bindings/net/ti-dp83867.h>
> +#include <dt-bindings/pwm/pwm.h>
> +#include "imx8mp-tqma8mpql.dtsi"
> +
> +/ {
> + model = "TQ-Systems i.MX8MPlus TQMa8MPxL on MBa8MPxL";
> + compatible = "tq,imx8mp-tqma8mpql-mba8mpxl", "tq,imx8mp-tqma8mpql", "fsl,imx8mp";
> +
> + chosen {
> + stdout-path = &uart4;
> + };
> +
> + iio-hwmon {
> + compatible = "iio-hwmon";
> + io-channels = <&adc 0>, <&adc 1>;
> + };
> +
> + aliases {
> + mmc0 = &usdhc3;
> + mmc1 = &usdhc2;
> + mmc2 = &usdhc1;
> + rtc0 = &pcf85063;
> + rtc1 = &snvs_rtc;
> + spi0 = &flexspi;
> + spi1 = &ecspi1;
> + spi2 = &ecspi2;
> + spi3 = &ecspi3;
> + };
> +
> + backlight_lvds: backlight-lvds {
> + compatible = "pwm-backlight";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_bllvds>;
> + pwms = <&pwm2 0 5000000 0>;
> + power-supply = <®_vcc_12v0>;
> + enable-gpios = <&gpio3 19 GPIO_ACTIVE_HIGH>;
> + status = "disabled";
> + };
> +
> + gpio-keys {
> + compatible = "gpio-keys";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_gpiobutton>;
> + autorepeat;
> +
> + switch1 {
swtich-1
> + label = "S12";
> + linux,code = <BTN_0>;
> + gpios = <&gpio5 26 GPIO_ACTIVE_LOW>;
> + };
> +
> + switch2 {
switch-2
> + label = "S13";
> + linux,code = <BTN_1>;
> + gpios = <&gpio5 27 GPIO_ACTIVE_LOW>;
> + };
> + };
> +
> + gpio-leds {
> + compatible = "gpio-leds";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_gpioled>;
> +
> + led0 {
led-0
> + label = "led0";
Your label should be more useful... or just replace it with function and
color.
> + gpios = <&gpio5 5 GPIO_ACTIVE_HIGH>;
> + linux,default-trigger = "default-on";
> + };
> +
> + led1 {
led-1
> + label = "led1";
> + gpios = <&gpio5 4 GPIO_ACTIVE_HIGH>;
> + linux,default-trigger = "heartbeat";
> + };
> +
> + led2 {
led-2
> + label = "led2";
> + gpios = <&gpio5 3 GPIO_ACTIVE_HIGH>;
> + };
> + };
> +
> + lvds_panel: display {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_lvdspanel>;
> + enable-gpios = <&gpio3 20 GPIO_ACTIVE_HIGH>;
> + backlight = <&backlight_lvds>;
> + status = "disabled";
What's this node about? There is no compatible.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-16 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 14:22 [PATCH 0/2] TQMa8MPxL + MBa8MPxL support Alexander Stein
2022-06-16 14:22 ` [PATCH 1/2] dt-bindings: arm: add TQMa8MPxL board Alexander Stein
2022-06-16 21:57 ` Krzysztof Kozlowski
2022-06-16 14:22 ` [PATCH 2/2] arm64: dts: freescale: add initial device tree for TQMa8MPQL with i.MX8MP Alexander Stein
2022-06-16 14:26 ` Krzysztof Kozlowski [this message]
2022-06-17 11:21 ` (EXT) " Alexander Stein
2022-06-17 23:15 ` Krzysztof Kozlowski
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=e039bef3-3fc4-e11e-9dcd-fe3a764edf3b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Markus.Niebel@tq-group.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).