From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Daniel Scally <dan.scally@ideasonboard.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh@kernel.org>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Li Yang <leoyang.li@nxp.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
kieran.bingham@ideasonboard.com, debix-tech@polyhex.net
Subject: Re: [PATCH 3/3] arm64: dts: Add device tree for the Debix Model A Board
Date: Mon, 3 Oct 2022 14:09:18 +0200 [thread overview]
Message-ID: <b0398b9c-7025-7f54-a884-8c41c6550a18@linaro.org> (raw)
In-Reply-To: <YzrQKyryCafL5pYx@pendragon.ideasonboard.com>
On 03/10/2022 14:06, Laurent Pinchart wrote:
> On Mon, Oct 03, 2022 at 11:26:54AM +0200, Krzysztof Kozlowski wrote:
>> On 03/10/2022 10:37, Daniel Scally wrote:
>>> Add a device tree file describing the Debix Model A board from
>>> Polyhex Technology Co.
>>>
>>> Signed-off-by: Daniel Scally <dan.scally@ideasonboard.com>
>>> ---
>>> arch/arm64/boot/dts/freescale/Makefile | 1 +
>>> .../dts/freescale/imx8mp-debix-model-a.dts | 550 ++++++++++++++++++
>>> 2 files changed, 551 insertions(+)
>>> create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-debix-model-a.dts
>>>
>>> diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile
>>> index 238a83e5b8c6..f26e802cef82 100644
>>> --- a/arch/arm64/boot/dts/freescale/Makefile
>>> +++ b/arch/arm64/boot/dts/freescale/Makefile
>>> @@ -79,6 +79,7 @@ dtb-$(CONFIG_ARCH_MXC) += imx8mn-ddr4-evk.dtb
>>> dtb-$(CONFIG_ARCH_MXC) += imx8mn-tqma8mqnl-mba8mx.dtb
>>> dtb-$(CONFIG_ARCH_MXC) += imx8mn-var-som-symphony.dtb
>>> dtb-$(CONFIG_ARCH_MXC) += imx8mn-venice-gw7902.dtb
>>> +dtb-$(CONFIG_ARCH_MXC) += imx8mp-debix-model-a.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
>>> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-debix-model-a.dts b/arch/arm64/boot/dts/freescale/imx8mp-debix-model-a.dts
>>> new file mode 100644
>>> index 000000000000..6d0fa3930d0b
>>> --- /dev/null
>>> +++ b/arch/arm64/boot/dts/freescale/imx8mp-debix-model-a.dts
>>> @@ -0,0 +1,550 @@
>>> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
>>> +/*
>>> + * Copyright 2019 NXP
>>> + */
>>> +
>>> +/dts-v1/;
>>> +
>>> +#include <dt-bindings/gpio/gpio.h>
>>> +#include <dt-bindings/leds/common.h>
>>> +#include <dt-bindings/usb/pd.h>
>>> +
>>> +#include "imx8mp.dtsi"
>>> +
>>> +/ {
>>> + model = "Polyhex Debix Model A (2GB) i.MX8MPlus board";
>>> + compatible = "polyhex,imx8mp-debix-modela2gb", "fsl,imx8mp";
>>> +
>>> + chosen {
>>> + stdout-path = &uart2;
>>> + };
>>> +
>>> + gpio-leds {
>>> + compatible = "gpio-leds";
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinctrl_gpio_led>;
>>> +
>>> + status-led {
>>> + function = LED_FUNCTION_POWER;
>>> + color = <LED_COLOR_ID_RED>;
>>> + gpios = <&gpio3 16 GPIO_ACTIVE_HIGH>;
>>> + default-state = "on";
>>> + };
>>> + };
>>> +
>>> + reg_usdhc2_vmmc: regulator-usdhc2 {
>>> + compatible = "regulator-fixed";
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinctrl_reg_usdhc2_vmmc>;
>>> + regulator-name = "VSD_3V3";
>>> + regulator-min-microvolt = <3300000>;
>>> + regulator-max-microvolt = <3300000>;
>>> + gpio = <&gpio2 19 GPIO_ACTIVE_HIGH>;
>>> + enable-active-high;
>>> + };
>>> +};
>>> +
>>> +&A53_0 {
>>> + cpu-supply = <&buck2>;
>>> +};
>>> +
>>> +&A53_1 {
>>> + cpu-supply = <&buck2>;
>>> +};
>>> +
>>> +&A53_2 {
>>> + cpu-supply = <&buck2>;
>>> +};
>>> +
>>> +&A53_3 {
>>> + cpu-supply = <&buck2>;
>>> +};
>>> +
>>> +&eqos {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinctrl_eqos>;
>>> + phy-connection-type = "rgmii-id";
>>> + phy-handle = <ðphy0>;
>>> + status = "okay";
>>> +
>>> + mdio {
>>> + compatible = "snps,dwmac-mdio";
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + ethphy0: ethernet-phy@0 {
>>> + compatible = "ethernet-phy-ieee802.3-c22";
>>> + reg = <0>;
>>> + reset-gpios = <&gpio4 18 GPIO_ACTIVE_LOW>;
>>> + reset-assert-us = <20>;
>>> + reset-deassert-us = <200000>;
>>> + };
>>> + };
>>> +};
>>> +
>>> +&fec {
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinctrl_fec>;
>>> + phy-connection-type = "rgmii-id";
>>> + phy-handle = <ðphy1>;
>>> + fsl,magic-packet;
>>> + status = "okay";
>>> +
>>> + mdio {
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + ethphy1: ethernet-phy@0 {
>>> + compatible = "ethernet-phy-ieee802.3-c22";
>>> + reg = <0>;
>>> + reset-gpios = <&gpio4 19 GPIO_ACTIVE_LOW>;
>>> + reset-assert-us = <10>;
>>> + reset-deassert-us = <150>;
>>> + };
>>> + };
>>> +};
>>> +
>>> +&i2c1 {
>>> + clock-frequency = <400000>;
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinctrl_i2c1>;
>>> + status = "okay";
>>> +
>>> + pmic@25 {
>>> + reg = <0x25>;
>>> + compatible = "nxp,pca9450c";
>>> + pinctrl-names = "default";
>>> + pinctrl-0 = <&pinctrl_pmic>;
>>> + interrupt-parent = <&gpio1>;
>>> + interrupts = <3 GPIO_ACTIVE_LOW>;
>>
>> Nope, wrong flag. This is a hint for us that you based your DTS on
>> something ancient (e.g. broken downstream stuff). Please start from
>> *scratch* and write your DTS based on a board taken from mainline.
>>
>> There is no point for us to repeat review for all the things we already
>> fixed in mainline.
>
> We can't fully do that, as we don't have access to the schematics for
> the board. What we can do, however, is to compare this .dts to others
> from mainline and investigate all differences to see if they can be
> bugs.
The upstreaming process is rather to take a DTS from the mainline and
customize it. Add stuff, remove something, change other nodes. Several
pieces are similar between boards, like the PMIC. I think this patch was
done in other way - entire PMIC was taken from downstream - therefore I
recommend the previous approach. It does not mean that everything should
be done from 0 but rather based on mainline DTS to avoid the same
mistakes we already fixed. Many times...
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-10-03 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 8:37 [PATCH 0/3] Debix Model A board devicetree Daniel Scally
2022-10-03 8:37 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Polyhex Technology Co Daniel Scally
2022-10-03 12:54 ` Krzysztof Kozlowski
2022-10-03 8:37 ` [PATCH 2/3] dt-bindings: arm: fsl: Enumerate Debix Model A Board Daniel Scally
2022-10-03 12:20 ` Laurent Pinchart
2022-10-03 12:55 ` Krzysztof Kozlowski
2022-10-03 8:37 ` [PATCH 3/3] arm64: dts: Add device tree for the " Daniel Scally
2022-10-03 9:26 ` Krzysztof Kozlowski
2022-10-03 10:22 ` Dan Scally
2022-10-03 12:06 ` Laurent Pinchart
2022-10-03 12:09 ` Krzysztof Kozlowski [this message]
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=b0398b9c-7025-7f54-a884-8c41c6550a18@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=dan.scally@ideasonboard.com \
--cc=debix-tech@polyhex.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marcel.ziswiler@toradex.com \
--cc=robh@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).