upstream kconfig is replacing the ---help--- command syntax with help.
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
config CARL9170FW_GPIO_INTERRUPT
def_bool y
prompt "GPIO Software Interrupt"
config CARL9170FW_GPIO_INTERRUPT
def_bool y
prompt "GPIO Software Interrupt"
When this option is enabled, the firmware will poll the GPIO
registers and reports to the driver whenever the GPIO state
has changed from a previous state.
When this option is enabled, the firmware will poll the GPIO
registers and reports to the driver whenever the GPIO state
has changed from a previous state.
config CARL9170FW_SECURITY_ENGINE
def_bool y
prompt "Support Hardware Crypto Engine"
config CARL9170FW_SECURITY_ENGINE
def_bool y
prompt "Support Hardware Crypto Engine"
This options controls if the firmware will allow the driver
to program the security engine / CAM through a firmware
interface.
This options controls if the firmware will allow the driver
to program the security engine / CAM through a firmware
interface.
config CARL9170FW_RADIO_FUNCTIONS
def_bool y
prompt "Enable Firmware-supported Radio/RF functions"
config CARL9170FW_RADIO_FUNCTIONS
def_bool y
prompt "Enable Firmware-supported Radio/RF functions"
Some PHY/RF functions (e.g.: AGC and Noise calibration) need
to be done in the firmware.
Some PHY/RF functions (e.g.: AGC and Noise calibration) need
to be done in the firmware.
def_bool y
prompt "Advanced printf"
depends on CARL9170FW_DEBUG_UART || CARL9170FW_DEBUG_USB
def_bool y
prompt "Advanced printf"
depends on CARL9170FW_DEBUG_UART || CARL9170FW_DEBUG_USB
Advanced printf (very useful for debugging purposes)
The formats supported by this implementation are:
'd' 'u' 'c' 's' 'x' 'X' 'p'.
Advanced printf (very useful for debugging purposes)
The formats supported by this implementation are:
'd' 'u' 'c' 's' 'x' 'X' 'p'.
def_bool n
prompt "Wakeup on WLAN"
depends on CARL9170FW_EXPERIMENTAL
def_bool n
prompt "Wakeup on WLAN"
depends on CARL9170FW_EXPERIMENTAL
With this option enabled, the firmware can wake-up
suspended hosts... As long as they fully support
USB remote wakeup.
With this option enabled, the firmware can wake-up
suspended hosts... As long as they fully support
USB remote wakeup.
prompt "Standard NL80211 wakeup triggers"
depends on CARL9170FW_WOL_OPTION
select CARL9170FW_WOL
prompt "Standard NL80211 wakeup triggers"
depends on CARL9170FW_WOL_OPTION
select CARL9170FW_WOL
Available triggers:
* Magic Packet(tm) pattern
* disconnect event
Available triggers:
* Magic Packet(tm) pattern
* disconnect event
prompt "Probe Request"
depends on CARL9170FW_WOL_OPTION
select CARL9170FW_WOL
prompt "Probe Request"
depends on CARL9170FW_WOL_OPTION
select CARL9170FW_WOL
Scan probe requests for a given SSID.
config CARL9170FW_WOL_PROBE_REQUEST_SSID
Scan probe requests for a given SSID.
config CARL9170FW_WOL_PROBE_REQUEST_SSID
def_bool n
prompt "Allow 80/88MHz clock for HT40"
depends on CARL9170FW_EXPERIMENTAL
def_bool n
prompt "Allow 80/88MHz clock for HT40"
depends on CARL9170FW_EXPERIMENTAL
The SoC can run up to 80/88MHz in HT40 mode. This improves
throughput and timing accuracy over the 40/44MHz clock.
However some devices don't have heat shields and they with
The SoC can run up to 80/88MHz in HT40 mode. This improves
throughput and timing accuracy over the 40/44MHz clock.
However some devices don't have heat shields and they with
def_bool n
prompt "LED Heartbeat"
depends on CARL9170FW_BROKEN_FEATURES
def_bool n
prompt "LED Heartbeat"
depends on CARL9170FW_BROKEN_FEATURES
This option conflicts with the application's LED code.
Also, it assumes that you have two LEDs, which is not
necessarily true.
This option conflicts with the application's LED code.
Also, it assumes that you have two LEDs, which is not
necessarily true.
def_bool n
prompt "Pass debug messages through Highspeed UART"
depends on CARL9170FW_BROKEN_FEATURES
def_bool n
prompt "Pass debug messages through Highspeed UART"
depends on CARL9170FW_BROKEN_FEATURES
This option allows the firmware to send BUG/ERR/INFO/DBG and
hexdumps through the UART _as well_. However, first: you must
connect a working logger.
This option allows the firmware to send BUG/ERR/INFO/DBG and
hexdumps through the UART _as well_. However, first: you must
connect a working logger.
def_bool n
prompt "USB 1.1 / 2.0 switching support"
depends on CARL9170FW_BROKEN_FEATURES && CARL9170FW_USB_STANDARD_CMDS
def_bool n
prompt "USB 1.1 / 2.0 switching support"
depends on CARL9170FW_BROKEN_FEATURES && CARL9170FW_USB_STANDARD_CMDS
Mostly implemented, but untested and some serious
doubts remain.
Mostly implemented, but untested and some serious
doubts remain.
config CARL9170FW_AGGRESSIVE_CFLAGS
def_bool y
prompt "Enable aggressive size optimization"
config CARL9170FW_AGGRESSIVE_CFLAGS
def_bool y
prompt "Enable aggressive size optimization"
This option adds several more optimization compiler flags,
which can greatly reduce the firmware size... at the expense
of machine-code readability.
This option adds several more optimization compiler flags,
which can greatly reduce the firmware size... at the expense
of machine-code readability.
config CARL9170FW_USB_STANDARD_CMDS
def_bool y
prompt "Basic USB Interface"
config CARL9170FW_USB_STANDARD_CMDS
def_bool y
prompt "Basic USB Interface"
Allows the device to be queried about Standard USB 2.0 Device
Description Descriptors.
Allows the device to be queried about Standard USB 2.0 Device
Description Descriptors.
config CARL9170FW_USB_UP_STREAM
def_bool y
prompt "USB Upload Stream"
config CARL9170FW_USB_UP_STREAM
def_bool y
prompt "USB Upload Stream"
This features allows the USB silicon to combine small, single
frames into bigger transfers. This can help to reduce
some per-transfer overhead in the application.
This features allows the USB silicon to combine small, single
frames into bigger transfers. This can help to reduce
some per-transfer overhead in the application.
config CARL9170FW_DEBUG_USB
def_bool y
prompt "Pass debug messages through USB transport"
config CARL9170FW_DEBUG_USB
def_bool y
prompt "Pass debug messages through USB transport"
Report all firmware messages through the USB transport.
But there is a catch: In case of a BUG, the USB transport
needs to be functional, otherwise the application won't
Report all firmware messages through the USB transport.
But there is a catch: In case of a BUG, the USB transport
needs to be functional, otherwise the application won't