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 <johann.fischer@nordicsemi.no>
This commit is contained in:
Johann Fischer 2024-11-15 11:23:00 +01:00 committed by Benjamin Cabé
parent 272290bfee
commit 2ddb576021
4 changed files with 0 additions and 56 deletions

View file

@ -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

View file

@ -1,18 +0,0 @@
# NUCLEO-144 F412ZG board configuration
# Copyright (c) 2017 Florian Vaussard, HEIG-VD
# SPDX-License-Identifier: Apache-2.0
if BOARD_NUCLEO_F412ZG
if NETWORKING
config USB_DEVICE_STACK
default y
config USB_DEVICE_NETWORK_ECM
default y
endif # NETWORKING
endif # BOARD_NUCLEO_F412ZG

View file

@ -1,18 +0,0 @@
# NUCLEO-144 F413ZH board configuration
# Copyright (c) 2017 Florian Vaussard, HEIG-VD
# SPDX-License-Identifier: Apache-2.0
if BOARD_NUCLEO_F413ZH
if NETWORKING
config USB_DEVICE_STACK
default y
config USB_DEVICE_NETWORK_ECM
default y
endif # NETWORKING
endif # BOARD_NUCLEO_F413ZH

View file

@ -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