[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADvTj4rrodFreH4gsYC0fW94e=+Z7m6N_2HoQDEbkc=VVKyOfw@mail.gmail.com>
Date: Fri, 21 Jul 2023 01:05:13 -0600
From: James Hilliard <james.hilliard1@...il.com>
To: Fabio Estevam <festevam@...il.com>
Cc: devicetree@...r.kernel.org,
Gregory CLEMENT <gregory.clement@...tlin.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>,
Marek Vasut <marex@...x.de>,
Frieder Schrempf <frieder.schrempf@...tron.de>,
Stefan Wahren <stefan.wahren@...rgebyte.com>,
Tim Harvey <tharvey@...eworks.com>,
Marcel Ziswiler <marcel.ziswiler@...adex.com>,
Christoph Niedermaier <cniedermaier@...electronics.com>,
Li Yang <leoyang.li@....com>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 2/4] ARM: dts: imx6qdl: Add Variscite VAR-SOM-MX6 SoM support
On Thu, Jul 20, 2023 at 7:27 AM Fabio Estevam <festevam@...il.com> wrote:
>
> On Thu, Jul 20, 2023 at 10:10 AM James Hilliard
> <james.hilliard1@...il.com> wrote:
>
> > + reg_audio: regulator-audio {
> > + compatible = "regulator-fixed";
> > + regulator-name = "tlv320aic3x-supply";
> > + enable-active-high;
>
> enable-active-high should only be used when there is a corresponding
> gpio property.
>
> > +&ecspi3 {
> > + fsl,spi-num-chipselects = <1>;
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_ecspi3>;
> > + cs-gpios = <&gpio4 24 GPIO_ACTIVE_HIGH>;
>
> This should be ACTIVE_LOW instead.
>
> > + status = "okay";
> > +};
> > +
> > +&fec {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_enet>;
> > + phy-mode = "rgmii";
> > + phy-reset-gpios = <&gpio1 25 GPIO_ACTIVE_LOW>;
>
> This is a deprecated property.
>
> The recommendation is to add a mdio node with:
>
> reset-gpios = <&gpio1 25 GPIO_ACTIVE_LOW>;
> reset-assert-us = <10000>;
>
> Is this an Atheros AR8031 PHY. If so, please check imx6qdl-sabresd.dtsi.
Hmm, the datasheet appears to indicate it uses a KSZ9031RN ethernet phy.
Would that be a different configuration vs the Atheros AR8031 PHY?
>
> > +&ssi2 {
> > + fsl,mode = "i2s-slave";
>
> This is unused, drop it.
>
> Please check commit ece1e4999 606 ("ASoC: fsl_ssi: Remove unneeded
> 'i2s-slave' property")
>
> > +&usdhc3 {
> > + pinctrl-names = "default", "state_100mhz", "state_200mhz";
> > + pinctrl-0 = <&pinctrl_usdhc3>;
> > + pinctrl-1 = <&pinctrl_usdhc3_100mhz>;
> > + pinctrl-2 = <&pinctrl_usdhc3_200mhz>;
> > + bus-width = <4>;
> > + vmmc-supply = <®_wl18xx_vmmc>;
> > + non-removable;
> > + wakeup-source;
> > + keep-power-in-suspend;
> > + cap-power-off-card;
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + status = "okay";
> > +
> > + wifi: wifi@0 {
> > + compatible = "ti,wl1835";
> > + reg = <2>;
>
> @0 and reg = <2> do not match.
Powered by blists - more mailing lists