boards: remove ECM/EEM from default configuration

The board hardware has no network interfaces, although the ECM/EEM class implementation can provide Ethernet-like functionality and export it to the host, this is no reason to default to a specific USB class implementation.We do not make this kind of configuration for other boards that have a USB device controller. Also, it may not be what a user expects when using these boards with networking and a USB stack. Signed-off-by: Johann Fischer <[email protected]>
zephyrproject-rtos · Nov 15, 2024 · b9a3072 · b9a3072
1 parent 0fa745d
commit b9a3072
Show file tree

Hide file tree

Showing 4 changed files with 0 additions and 56 deletions.
diff --git a/boards/blues/swan_r5/Kconfig.defconfig b/boards/blues/swan_r5/Kconfig.defconfig
@@ -9,14 +9,4 @@ config SPI_STM32_INTERRUPT
 	default y
 	depends on SPI
 
-if NETWORKING
-
-config USB_DEVICE_STACK
-	default y
-
-config USB_DEVICE_NETWORK_EEM
-	default y
-
-endif # NETWORKING
-
 endif # BOARD_SWAN_R5
diff --git a/boards/st/nucleo_f412zg/Kconfig.defconfig b/boards/st/nucleo_f412zg/Kconfig.defconfig
diff --git a/boards/st/nucleo_f413zh/Kconfig.defconfig b/boards/st/nucleo_f413zh/Kconfig.defconfig
diff --git a/boards/st/nucleo_l4r5zi/Kconfig.defconfig b/boards/st/nucleo_l4r5zi/Kconfig.defconfig
@@ -9,14 +9,4 @@ config SPI_STM32_INTERRUPT
 	default y
 	depends on SPI
 
-if NETWORKING
-
-config USB_DEVICE_STACK
-	default y
-
-config USB_DEVICE_NETWORK_EEM
-	default y
-
-endif # NETWORKING
-
 endif # BOARD_NUCLEO_L4R5ZI