Do not enable subsystem/driver shell modules by default and stop abusing CONFIG_SHELL_MINIMAL, which is internal to the shell subsystem, to decide when to enable a driver shell. The list of shell modules has grown considerably through the years. Enabling CONFIG_SHELL for doing e.g. an interactive debug session leads to a large number of shell modules also being enabled unless explicitly disabled, which again leads to non-negligible increases in RAM/ROM usage. This commit attempts to establish a policy of subsystem/driver shell modules being disabled by default, requiring the user/application to explicitly enable only those needed. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
46 lines
921 B
Plaintext
46 lines
921 B
Plaintext
# Copyright (c) 2022 Nordic Semiconductor ASA
|
|
#
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
menuconfig USB_DEVICE_STACK_NEXT
|
|
bool "New USB device stack [EXPERIMENTAL]"
|
|
select EXPERIMENTAL
|
|
select UDC_DRIVER
|
|
select HWINFO
|
|
help
|
|
New experimental USB device stack.
|
|
|
|
if USB_DEVICE_STACK_NEXT
|
|
|
|
module = USBD
|
|
module-str = usbd
|
|
source "subsys/logging/Kconfig.template.log_config"
|
|
|
|
config USBD_SHELL
|
|
bool "USB device shell"
|
|
depends on SHELL
|
|
help
|
|
Enable USB device shell.
|
|
|
|
config USBD_THREAD_INIT_PRIO
|
|
int
|
|
default 90
|
|
help
|
|
USB device thread initialization priority level.
|
|
|
|
config USBD_THREAD_STACK_SIZE
|
|
int "USB device stack thread stack size"
|
|
default 1024
|
|
help
|
|
USB device stack thread stack size in bytes.
|
|
|
|
config USBD_MAX_UDC_MSG
|
|
int "Maximum number of UDC events"
|
|
default 10
|
|
help
|
|
Maximum number of USB device controller events that can be queued.
|
|
|
|
rsource "class/Kconfig"
|
|
|
|
endif # USB_DEVICE_STACK_NEXT
|