linux-kernel - Re: [PATCH v2 1/5] dt-bindings: arm: ti: add toradex,verdin-am62 et al.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 2 Jun 2023 10:18:25 +0200
From:   Francesco Dolcini <francesco@...cini.it>
To:     Tony Lindgren <tony@...mide.com>
Cc:     Francesco Dolcini <francesco@...cini.it>,
        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.

On Fri, Jun 02, 2023 at 10:20:45AM +0300, Tony Lindgren wrote:
> 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.

This is exactly the case, the wifi/non-wifi variant are re-using pins.

I provided a more verbose explanation on that on a previous discussion
https://lore.kernel.org/all/ZG5jYV%2FNfGJvYkma@francesco-nb.int.toradex.com/

Francesco