From: Tony Lindgren <tony@atomide.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v2 1/5] dt-bindings: arm: ti: add toradex,verdin-am62 et al.
Date: Fri, 2 Jun 2023 10:20:45 +0300 [thread overview]
Message-ID: <20230602072045.GO14287@atomide.com> (raw)
In-Reply-To: <20230601131332.26877-2-francesco@dolcini.it>
Hi,
* Francesco Dolcini <francesco@dolcini.it> [230601 13:15]:
> From: Francesco Dolcini <francesco.dolcini@toradex.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
next prev parent reply other threads:[~2023-06-02 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 13:13 [PATCH v2 0/5] Add Toradex Verdin AM62 Francesco Dolcini
2023-06-01 13:13 ` [PATCH v2 1/5] dt-bindings: arm: ti: add toradex,verdin-am62 et al Francesco Dolcini
2023-06-02 7:20 ` Tony Lindgren [this message]
2023-06-02 8:18 ` Francesco Dolcini
2023-06-05 4:48 ` Tony Lindgren
2023-06-01 13:13 ` [PATCH v2 3/5] arm64: dts: ti: add verdin am62 Francesco Dolcini
2023-06-15 6:08 ` Vignesh Raghavendra
2023-06-15 6:51 ` Francesco Dolcini
2023-06-15 7:38 ` Vignesh Raghavendra
2023-06-15 7:48 ` Francesco Dolcini
2023-06-15 9:51 ` Vignesh Raghavendra
2023-06-01 13:13 ` [PATCH v2 4/5] arm64: dts: ti: add verdin am62 dahlia Francesco Dolcini
2023-06-15 6:22 ` Vignesh Raghavendra
2023-06-15 6:30 ` Francesco Dolcini
2023-06-01 13:18 ` [PATCH v2 5/5] arm64: dts: ti: add verdin am62 yavia Francesco Dolcini
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=20230602072045.GO14287@atomide.com \
--to=tony@atomide.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/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).