[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230602072045.GO14287@atomide.com>
Date: Fri, 2 Jun 2023 10:20:45 +0300
From: Tony Lindgren <tony@...mide.com>
To: Francesco Dolcini <francesco@...cini.it>
Cc: Nishanth Menon <nm@...com>, Vignesh Raghavendra <vigneshr@...com>,
Francesco Dolcini <francesco.dolcini@...adex.com>,
Tero Kristo <kristo@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v2 1/5] dt-bindings: arm: ti: add toradex,verdin-am62 et
al.
Hi,
* Francesco Dolcini <francesco@...cini.it> [230601 13:15]:
> From: Francesco Dolcini <francesco.dolcini@...adex.com>
>
> Add toradex,verdin-am62 for Toradex Verdin AM62 SoM, its
> nonwifi and wifi variants and the carrier boards (Dahlia,
> Verdin Development Board and Yavia) they may be mated in.
Looks like you have wifi on sdio, there should be no need for separate
compatible properties. The sdio wifi will try to probe and will just bail
out if no wifi is populated.
If however the non-wifi variants are recycling the sdio pins for something
else, then it's it's a different story. In that case you want either
seprate compatible properties, or want to use dts fragments possibly.
Regards,
Tony
Powered by blists - more mailing lists