From: Franz Schnyder <[email protected]> Currently, the Verdin iMX95 uses the Toradex product ID table to determine whether the module is a WiFi or a non-WiFi one and sets the DTB accordingly.
In the progress of decoupling from the Toradex product PID table, use the WiFi DTB as the default for new PIDs. This change is safe, as on non-WiFi modules this leaves the WiFi and BT devices unprobed. Further, the SDIO/UART signals are exposed to the edge connector on non-WiFi modules and can be used on the carrier. However, no Toradex carrier board makes use of these interfaces on the carrier and it can only be achieved with a customized board. For customized boards, it's expected to override the default selection by setting the 'fdtfile' env variable. Signed-off-by: Franz Schnyder <[email protected]> --- board/toradex/verdin-imx95/verdin-imx95.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/board/toradex/verdin-imx95/verdin-imx95.c b/board/toradex/verdin-imx95/verdin-imx95.c index 7c0804c1d1c..2651d3dd871 100644 --- a/board/toradex/verdin-imx95/verdin-imx95.c +++ b/board/toradex/verdin-imx95/verdin-imx95.c @@ -19,7 +19,7 @@ static void select_dt_from_module_version(void) { char variant[32]; char *env_variant = env_get("variant"); - bool is_wifi = false; + bool is_wifi = true; if (IS_ENABLED(CONFIG_TDX_CFG_BLOCK)) { /* @@ -27,8 +27,8 @@ static void select_dt_from_module_version(void) * module with Wi-Fi/Bluetooth make sure we use the -wifi * device tree. */ - is_wifi = (tdx_hw_tag.prodid == VERDIN_IMX95H_8G_WIFI_BT_IT) || - (tdx_hw_tag.prodid == VERDIN_IMX95H_4G_WB_IT); + is_wifi = !((tdx_hw_tag.prodid == VERDIN_IMX95H_4G_ET) || + (tdx_hw_tag.prodid == VERDIN_IMX95H_16G_IT)); } if (is_wifi) -- 2.43.0
