nuttx/Kconfig

2615 lines
62 KiB
Plaintext
Raw Normal View History

#
# For a description of the syntax of this configuration file,
# see the file kconfig-language.txt in the NuttX tools repository.
#
mainmenu "NuttX/$ARCH Configuration"
config APPSDIR
string
option env="APPSDIR"
config APPSBINDIR
string
option env="APPSBINDIR"
---help---
Output path of Kconfig which dynamically generated by NuttX Apps
This option is consistent with the APPSDIR by default, and will
be changed when out-of-tree compilation is supported
config BINDIR
string
option env="BINDIR"
---help---
Output path of Kconfig which dynamically generated by NuttX Kernel
This option is consistent with the TOPDIR by default, and will
be changed when out-of-tree compilation is supported
menu "License Setup"
config ALLOW_BSD_COMPONENTS
bool "Use components that have BSD licenses"
default n
---help---
When this option is enabled the project will allow the use
of components that have BSD licenses.
NOTE: Please check that the license for each enabled
component matches your project license.
NOTE: If this option is not set the following components
are not included in the setup menu:
Crypto
AES cypher support
FS
NFS client file system
SPIFFS File System
Wireless
Bluetooth LE support
config ALLOW_GPL_COMPONENTS
bool "Use components that have GPL/LGPL licenses"
default n
---help---
When this option is enabled the project will allow the use
of components that have GPL/LGPL licenses.
NOTE: Please check that the license for each enabled
component matches your project license.
2022-08-01 15:05:06 +02:00
config ALLOW_MIT_COMPONENTS
bool "Use components that have MIT licenses"
default n
---help---
When this option is enabled the project will allow the use
of components that have MIT licenses.
NOTE: Please check that the license for each enabled
component matches your project license.
config ALLOW_BSDNORDIC_COMPONENTS
bool "Use components that have 5-Clause Nordic licenses"
depends on ARCH_CHIP_NRF52 || ARCH_CHIP_NRF53 || ARCH_CHIP_NRF91
default n
---help---
When this option is enabled the project will allow the use
of components that have 5-Clause Nordic licenses.
NOTE: Please check that the license for each enabled
component matches your project license.
2023-07-25 14:20:58 +02:00
config ALLOW_ECLIPSE_COMPONENTS
bool "Use components that have Eclipse Public Licenses"
default n
---help---
When this option is enabled the project will allow the use
of components that have EPL licenses.
NOTE: Please check that the license for each enabled
component matches your project license.
2023-09-22 12:06:18 +02:00
config ALLOW_ICS_COMPONENTS
bool "Use components that have ICS license"
default n
---help---
When this option is enabled the project will allow the use
of components that have ICS licenses.
NOTE: Please check that the license for each enabled
component matches your project license.
endmenu # License Setup
menu "Build Setup"
config EXPERIMENTAL
bool "Show experimental options"
---help---
Some features and drivers are considered "experimental" or
development/work-in-progress status. By default, these options are
hidden in the Kconfig menus. Enabling "Show experimental options"
makes these options visible and makes it possible to enable them.
config DEFAULT_SMALL
bool "Default to smallest size"
default n
---help---
When options are present, the default value for certain options will
be the one the results in the smallest size (at a loss of features).
The default is a fuller feature set at a larger size.
NOTE: This option does not prevent you from overriding the default
to select another alternative. Nor does it affect the settings that
have already been selected in your configuration file. This applies
only to new settings that require a default value.
choice
prompt "Build Host Platform"
default HOST_LINUX
config HOST_LINUX
bool "Linux"
config HOST_MACOS
bool "macOS"
config HOST_WINDOWS
bool "Windows"
config HOST_OTHER
bool "Other"
endchoice # Build Host Platform
config TOOLCHAIN_WINDOWS
bool
default n
depends on HOST_WINDOWS
---help---
Selected internally if the selected Windows environment is compatible
with the use of Windows native toolchains.
config CYGWIN_WINTOOL
bool
default n
depends on WINDOWS_CYGWIN
---help---
Selected internally if Cygwin environment with the use of Windows
native toolchains.
choice
prompt "Windows Build Environment"
default WINDOWS_CYGWIN
depends on HOST_WINDOWS
config WINDOWS_NATIVE
bool "Windows Native"
select TOOLCHAIN_WINDOWS
depends on EXPERIMENTAL
---help---
2016-03-19 15:08:18 +01:00
Build natively in a CMD.exe environment with Windows style paths
(like C:\cygwin\home)
The Windows native build is complete and available, but not often
used or verified. As a consequence, it cannot be assured to be
fully functional at any given time. Hence, it is marked here as
EXPERIMENTAL so that the end user will be aware of this state.
config WINDOWS_CYGWIN
bool "Cygwin"
select TOOLCHAIN_WINDOWS
2013-04-21 01:05:45 +02:00
---help---
2016-03-19 15:08:18 +01:00
Build natively in a Cygwin environment with POSIX style paths (like
/cygdrive/c/Program Files)
config WINDOWS_MSYS
2018-05-31 15:35:56 +02:00
bool "MSYS or MSYS2"
select TOOLCHAIN_WINDOWS
---help---
2016-03-19 15:08:18 +01:00
Build natively in a Cygwin environment with POSIX style paths (like
/cygdrive/c/cygwin/home)
config WINDOWS_OTHER
bool "Windows POSIX-like environment"
select TOOLCHAIN_WINDOWS
---help---
2016-03-19 15:08:18 +01:00
Build natively in another POSIX-like environment. Additional
support may be necessary
endchoice # Windows Build Environment
config WINDOWS_MKLINK
bool "Use mklink"
default n
depends on WINDOWS_NATIVE
---help---
Use the mklink command to set up symbolic links when NuttX is
configured. Otherwise, configuration directories will be copied to
establish the configuration.
If directories are copied, then some confusion can result ("Which
version of the file did I modify?"). In that case, it is recommended
that you re-build using 'make clean_context all'. That will cause the
configured directories to be recopied on each build.
NOTE: This option also (1) that you have administrator privileges, (2)
that you are using Windows 2000 or better, and (3) that you are using
the NTFS file system. Select 'n' is that is not the case.
menu "Build Configuration"
config APPS_DIR
string "Application directory"
default "../apps" if !WINDOWS_NATIVE
default "..\apps" if WINDOWS_NATIVE
---help---
Identifies the directory that builds the
2016-03-19 15:08:18 +01:00
application to link with NuttX. Default: ../apps This symbol must
be assigned to the path to the application build directory
*relative* to the NuttX top build directory. If you had an
application directory and the NuttX directory each in separate
directory trees like this:
build
|-nuttx
| |
| `- Makefile
`-application
|
`- Makefile
Then you would set APPS_DIR=../application.
The application direction must contain Makefile and this make
file must support the following targets:
1)libapps$(LIBEXT) (usually libapps.a). libapps.a is a static
library ( an archive) that contains all of application object
files.
2)clean. Do whatever is appropriate to clean the application
directories for a fresh build.
2014-02-08 17:46:29 +01:00
3)distclean. Clean everything -- auto-generated files, symbolic
links etc. -- so that the directory contents are the same as
the contents in your configuration management system.
This is only done when you change the NuttX configuration.
4)depend. Make or update the application build dependencies.
When this application is invoked it will receive the setting TOPDIR like:
$(MAKE) -C $(CONFIG_APPS_DIR) TOPDIR="$(TOPDIR)" <target>
TOPDIR is the full path to the NuttX directory. It can be used, for
example, to include makefile fragments (e.g., .config or Make.defs)
or to set up include file paths.
config BASE_DEFCONFIG
string "Base Configuration"
default ""
---help---
This will be automatically be updated by the configuration
script. This is the base configuration file that was used to create the
current configuration. It is useful for getting the current configuration
on runtime.
config BUILD_LOADABLE
bool
option modules
---help---
Automatically selected if KERNEL build is selected.
This selection only effects the behavior of the 'make export'
target and currently has no effect unless you wish to build
loadable applications in a FLAT build.
choice
prompt "Memory organization"
default BUILD_FLAT
config BUILD_FLAT
bool "Flat address space"
---help---
Build NuttX as one large, executable "blob". All of the code
within the blob can interrupt with all of the other code within
the blob. There are no special privileges, protections, or
restraints.
config BUILD_PROTECTED
bool "NuttX protected build"
depends on ARCH_USE_MPU
select LIB_SYSCALL
select BUILD_2PASS
---help---
2016-03-19 15:08:18 +01:00
Builds NuttX and selected applications as two "blobs": A protected,
privileged kernel blob and a separate unprivileged, user blob. This
requires use of the two pass build with each blob being build on
each pass.
NOTE: This build configuration requires that the platform support
a memory protection unit (MPU). Support, however, may not be
implemented on all platforms.
config BUILD_KERNEL
bool "NuttX kernel build"
depends on ARCH_USE_MMU && ARCH_ADDRENV
select BUILD_LOADABLE
select LIB_SYSCALL
---help---
Builds NuttX as a separately compiled kernel. No applications are
built. All user applications must reside in a file system where
they can be loaded into memory for execution.
NOTE: This build configuration requires that the platform support
2021-02-06 10:22:35 +01:00
a memory management unit (MMU) and address environments. Support,
however, may not be implemented on all platforms.
endchoice # Build configuration
config BUILD_2PASS
bool "Two pass build"
default n
---help---
Enables the two pass build options.
Two-pass build options. If the 2 pass build option is selected, then these
options configure the make system build a extra link object. This link object
is assumed to be an incremental (relative) link object, but could be a static
library (archive) (some modification to this Makefile would be required if
PASS1_TARGET generates an archive). Pass 1 1ncremental (relative) link
objects should be put into the processor-specific source directory (where other
2014-02-08 17:46:29 +01:00
link objects will be created). If the pass1 object is an archive, it could
go anywhere.
if BUILD_2PASS
config PASS1_TARGET
string "Pass one target"
default "all"
---help---
The name of the first pass build target. This
can be specific build target, a special build target (all, default, etc.)
or may just be left undefined.
config PASS1_BUILDIR
string "Pass one build directory"
default "build"
---help---
The path, relative to the top NuttX build
directory to directory that contains the Makefile to build the
first pass object. The Makefile must support the following targets:
The special target PASS1_TARGET (if defined)
and the usual depend, clean, and distclean targets.
config PASS1_OBJECT
string "Pass one object"
default ""
---help---
May be used to include an extra, pass1 object
into the final link. This would probably be the object generated
from the PASS1_TARGET. It may be available at link time
in the arch/<architecture>/src directory.
config NUTTX_USERSPACE
hex "Beginning of user-space blob"
default 0x0
depends on BUILD_PROTECTED
---help---
In the kernel build, the NuttX kernel and the user-space blob are
built separately linked objects. NUTTX_USERSPACE provides the
address where the user-space blob is loaded into memory. NuttX will
expect to find and instance of struct userspace_s at this location.
endif # Build 2-pass
endmenu # Build Setup
menu "Binary Output Formats"
config INTELHEX_BINARY
bool "Intel HEX binary format"
default n
---help---
Create the nuttx.hex in the Intel HEX binary format that is
2016-03-19 15:08:18 +01:00
used with many different loaders. This option will use the GNU objcopy
program and should not be selected if you are not using the GNU
toolchain.
config MOTOROLA_SREC
bool "Motorola S-Record binary format"
default n
---help---
Create the nuttx.srec in the Motorola S-Record binary format that is
2016-03-19 15:08:18 +01:00
used with many different loaders. This option will use the GNU objcopy
program and should not be selected if you are not using the GNU
toolchain.
config RAW_BINARY
bool "Raw binary format"
default n
---help---
Create the nuttx.bin in the raw binary format that is used with many
different loaders using the GNU objcopy program. This option
should not be selected if you are not using the GNU toolchain.
config RAW_DISASSEMBLY
bool "Create a disassembly file"
default n
---help---
Create the nuttx.asm in the disassembly format using the objdump program.
menuconfig UBOOT_UIMAGE
bool "U-Boot uImage"
select RAW_BINARY
depends on !WINDOWS_NATIVE
---help---
Create the uImage binary used with U-Boot.
if UBOOT_UIMAGE
config UIMAGE_LOAD_ADDRESS
hex "uImage load address"
default 0x0
config UIMAGE_ENTRY_POINT
hex "uImage entry point"
default 0x0
endif # UBOOT_UIMAGE
menuconfig DFU_BINARY
bool "DFU binary format"
select RAW_BINARY
---help---
Create the dfu binary used with dfu-utils.
if DFU_BINARY
config DFU_BASE
hex "Address DFU image is loaded to"
config DFU_VID
hex "VID to use for DFU image"
config DFU_PID
hex "PID to use for DFU image"
endif # DFU_BINARY
config OUTPUT_STRIP_PATHS
bool "Strip absolute paths from binaries"
default y
depends on ARCH_TOOLCHAIN_GNU
---help---
Cmake build provide absolute paths to compile files. If __FILE__
macros are used in the source code(ASSERT), the binary will contain
many invalid paths.
This saves some memory, stops exposing build systems locations in binaries,
make failure logs more deterministic and most importantly makes builds more
failure logs more deterministic and most importantly makes builds more
deterministic.
Debuggers usually have a path mapping feature to ensure the files are
still found.
endmenu # Binary Output Formats
menu "Customize Header Files"
config ARCH_HAVE_STDINT_H
bool
default n
---help---
Selected by architecture specific logic if the architecture provides
a stdint.h header file.
config ARCH_STDINT_H
bool "stdint.h"
default n
depends on ARCH_HAVE_STDINT_H
---help---
The stdint.h header file can be found at nuttx/include/stdint.h.
However, that header includes logic to redirect the inclusion of an
architecture specific header file like:
#ifdef CONFIG_ARCH_STDINT_H
# include <arch/stdint.h>
#else
...
#endif
Recall that that include path, include/arch, is a symbolic link and
will refer to a version of stdint.h at nuttx/arch/<architecture>/include/stdint.h.
config ARCH_HAVE_STDBOOL_H
bool
default n
---help---
Selected by architecture specific logic if the architecture provides
a stdbool.h header file.
config ARCH_STDBOOL_H
bool "stdbool.h"
default n
depends on ARCH_HAVE_STDBOOL_H
---help---
The stdbool.h header file can be found at nuttx/include/stdbool.h.
However, that header includes logic to redirect the inclusion of an
architecture specific header file like:
#ifdef CONFIG_ARCH_STDBOOL_H
# include <arch/stdbool.h>
#else
...
#endif
Recall that that include path, include/arch, is a symbolic link and
will refer to a version of stdbool.h at nuttx/arch/<architecture>/include/stdbool.h.
config ARCH_HAVE_MATH_H
bool
default n
---help---
Selected by architecture specific logic if the architecture provides
a math.h header file.
config ARCH_MATH_H
bool "math.h"
depends on ARCH_HAVE_MATH_H
default n
---help---
There is also a re-directing version of math.h in the source tree.
However, it resides out-of-the-way at include/nuttx/lib/math.h because it
conflicts too often with the system math.h. If ARCH_MATH_H=y is
defined, however, the top-level makefile will copy the redirecting
math.h header file from include/nuttx/lib/math.h to include/math.h. math.h
will then include the architecture-specific version of math.h that you
must provide at nuttx/arch/>architecture</include/math.h.
#ifdef CONFIG_ARCH_MATH_H
# include <arch/math.h>
#endif
So for the architectures that define ARCH_MATH_H=y, include/math.h
will be the redirecting math.h header file; for the architectures
that don't select ARCH_MATH_H, the redirecting math.h header file
will stay out-of-the-way in include/nuttx/.
config ARCH_FLOAT_H
bool "float.h"
default n
---help---
The float.h header file defines the properties of your floating
point implementation. It would always be best to use your
2014-02-08 17:46:29 +01:00
toolchain's float.h header file but if none is available, a default
float.h header file will provided if this option is selected. However
there is no assurance that the settings in this float.h are actually
correct for your platform!
config ARCH_HAVE_STDARG_H
bool
default n
---help---
Selected by architecture specific logic if the architecture provides
a math.h header file.
config ARCH_STDARG_H
bool "stdarg.h"
depends on ARCH_HAVE_STDARG_H
default n
---help---
There is a redirecting version of stdarg.h in the source tree. It
resides out-of-the-way at include/nuttx/lib/stdarg.h. This is
because you should normally use your toolchain's stdarg.h file. But
sometimes, your toolchain's stdarg.h file may have other header
file dependencies and so may not be usable in the NuttX build
environment. In those cases, you may have to create a architecture-
specific stdarg.h header file at nuttx/arch/<architecture>/include/stdarg.h
If ARCH_STDARG_H=y is defined, the top-level makefile will copy the
re-directing stdarg.h header file from include/nuttx/lib/stdarg.h to
include/stdarg.h. So for the architectures that cannot use their
toolchain's stdarg.h file, they can use this alternative by defining
ARCH_STDARG_H=y and providing. If ARCH_STDARG_H, is not defined, then
the stdarg.h header file will stay out-of-the-way in include/nuttx/.
config ARCH_HAVE_SETJMP
bool
default n
config ARCH_SETJMP_H
bool "setjmp.h"
default n
depends on ARCH_HAVE_SETJMP
---help---
There is a redirecting version of setjmp.h in the source tree. It
resides out-of-the-way at include/nuttx/lib/setjmp.h. This is
because you should normally use your toolchain's setjmp.h file. But
sometimes, your toolchain's setjmp.h file may have other header
file dependencies and so may not be usable in the NuttX build
environment. In those cases, you may have to create a architecture-
specific setjmp.h header file at nuttx/arch/<architecture>/include/setjmp.h
If ARCH_SETJMP_H=y is defined, the top-level makefile will copy the
re-directing setjmp.h header file from include/nuttx/lib/setjmp.h to
include/setjmp.h. So for the architectures that cannot use their
toolchain's setjmp.h file, they can use this alternative by defining
ARCH_SETJMP_H=y and providing. If ARCH_SETJMP_H, is not defined, then
the setjmp.h header file will stay out-of-the-way in include/nuttx/.
choice
prompt "debug.h selection"
default ARCH_NONE_DEBUG_H
config ARCH_NONE_DEBUG_H
bool "None"
---help---
No debug.h under include/arch/ and include/arch/chip.
config ARCH_DEBUG_H
bool "debug.h"
---help---
The debug.h under include/arch contains architecture dependent debugging primitives
config ARCH_CHIP_DEBUG_H
bool "chip debug.h"
---help---
The debug.h under include/arch/chip contains architecture dependent debugging primitives
config ARCH_BOARD_DEBUG_H
bool "board debug.h"
---help---
The debug.h under include/arch/board contains board dependent debugging primitives
endchoice # debug.h selection
endmenu # Customize Header Files
menu "Debug Options"
config FORTIFY_SOURCE
int "Fortify Source"
default 0
range 0 3
---help---
Detect overflows of buffers in common string and memory functions
where the compiler can determine and validate the buffer sizes.
0 does not have any checks.
1 will only check for out-of-bounds at compile time.
2 will only perform out-of-bounds checks on stack variables.
3 On the basis of 2, add an out-of-bounds check for dynamically allocated variables.
config NDEBUG
bool "Define NDEBUG globally"
default !DEBUG_ASSERTIONS
config ASSERTIONS_FILENAME
bool "Enable library call assert(3) show the file name"
default DEBUG_ASSERTIONS_FILENAME || !DEFAULT_SMALL
depends on !NDEBUG
---help---
This option can display the file information of the library call assert(3)
function when it is enabled. This option maybe will take up a lot
of space from applications.
config DEBUG_ALERT
bool
default n
config DEBUG_FEATURES
bool "Enable Debug Features"
default n
select DEBUG_ALERT
---help---
Enables built-in debug features. Selecting this option will (1) Enable
debug assertions in the code, (2) enable extended parameter testing in
many functions, and (3) enable support for debug output to the SYSLOG.
Note that enabling this option by itself does not produce debug output.
Debug output must also be selected on a subsystem-by-subsystem basis.
if DEBUG_FEATURES
comment "Debug SYSLOG Output Controls"
config DEBUG_ERROR
bool "Enable Error Output"
default y
---help---
Enables output from [a-z]err() statements. Errors are significant system
exceptions that require immediate attention.
config DEBUG_WARN
bool "Enable Warnings Output"
default y
depends on DEBUG_ERROR
---help---
Enables output from [a-z]warn() statements. Warnings are considered to
be various unexpected conditions, potential errors or errors that will
not have serious consequences.
config DEBUG_INFO
bool "Enable Informational Debug Output"
default y
depends on DEBUG_WARN
---help---
Enables verbose "informational" debug output. If you enable
CONFIG_DEBUG_INFO, then very chatty (and often annoying) output
will be generated.
config DEBUG_ASSERTIONS
bool "Enable Debug Assertions"
default n
---help---
Enables the DEBUGASSERT() macro. When CONFIG_DEBUG_ASSERTIONS is
defined, DEBUGASSERT() will cause the system to halt if the
assertion fails. If CONFIG_DEBUG_ASSERTIONS is not defined
DEBUGASSERT() compiled out of the system. In general, you would
set CONFIG_DEBUG_ASSERTIONS=y during debug, but disable the
assertions on a final, buckled up system.
config DEBUG_ASSERTIONS_EXPRESSION
bool "Enable Debug Assertions show expression"
default n
depends on DEBUG_ASSERTIONS
---help---
This option can display the content information of the ASSERT()
function when it is triggered. This option maybe will take up a lot
of space.
config DEBUG_ASSERTIONS_FILENAME
bool "Enable Debug Assertions show file name"
default !DEFAULT_SMALL
depends on DEBUG_ASSERTIONS
---help---
This option can display the file information of the ASSERT()
function when it is enabled. This option maybe will take up a lot
of space.
comment "Subsystem Debug Options"
config DEBUG_AUDIO
bool "Audio Device Debug Features"
default n
2016-02-27 00:07:04 +01:00
depends on AUDIO
---help---
Enable audio device debug features.
Enable low level debug features for the audio subsystem and for audio
device drivers. (disabled by default). Support for this debug option
is architecture-specific and may not be available for some MCUs.
if DEBUG_AUDIO
config DEBUG_AUDIO_ERROR
bool "Audio Device Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable audio device error output to SYSLOG.
config DEBUG_AUDIO_WARN
bool "Audio Device Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable audio device warning output to SYSLOG.
config DEBUG_AUDIO_INFO
bool "Audio Device Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable audio device informational output to SYSLOG.
endif # DEBUG_AUDIO
config DEBUG_BINFMT
bool "Binary Loader Debug Features"
default n
depends on !BINFMT_DISABLE || LIBC_MODLIB
---help---
Enable binary loader debug features.
if DEBUG_BINFMT
config DEBUG_BINFMT_ERROR
bool "Binary Loader Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable binary loader error output to SYSLOG.
config DEBUG_BINFMT_WARN
bool "Binary Loader Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable binary loader warning output to SYSLOG.
config DEBUG_BINFMT_INFO
bool "Binary Loader Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable binary loader informational output to SYSLOG.
endif # DEBUG_BINFMT
config DEBUG_CONTACTLESS
bool "Contactless Debug Features"
default n
depends on DRIVERS_CONTACTLESS
---help---
Enable debug features for contactless (aka RFID) subsystem.
if DEBUG_CONTACTLESS
config DEBUG_CONTACTLESS_ERROR
bool "Contactless Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable contactless (aka RFID) subsystem error output to
SYSLOG.
config DEBUG_CONTACTLESS_WARN
bool "Contactless Warnings Output"
default n
depends on DEBUG_ERROR
---help---
Enable contactless (aka RFID) subsystem warning output to
SYSLOG.
config DEBUG_CONTACTLESS_INFO
bool "Contactless Informational Output"
default n
depends on DEBUG_ERROR
---help---
Enable contactless (aka RFID) subsystem informational output
to SYSLOG.
endif # DEBUG_CONTACTLESS
config DEBUG_CRYPTO
bool "Crypto Debug Features"
default n
depends on CRYPTO
---help---
Enable cryptographic debug features.
if DEBUG_CRYPTO
config DEBUG_CRYPTO_ERROR
bool "Crypto Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable cryptographic error output to SYSLOG.
config DEBUG_CRYPTO_WARN
bool "Crypto Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable cryptographic warning output to SYSLOG.
config DEBUG_CRYPTO_INFO
bool "Crypto Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable cryptographic informational output to SYSLOG.
endif # DEBUG_CRYPTO
config DEBUG_FS
bool "File System Debug Features"
default n
---help---
Enable file system debug features.
if DEBUG_FS
config DEBUG_FS_ERROR
bool "File System Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable file system error output to SYSLOG.
config DEBUG_FS_WARN
bool "File System Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable file system warning output to SYSLOG.
config DEBUG_FS_INFO
bool "File System Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable file system informational output to SYSLOG.
endif # DEBUG_FS
config DEBUG_GRAPHICS
bool "Graphics Debug Features"
default n
---help---
Enable NX graphics subsystem debug features.
if DEBUG_GRAPHICS
config DEBUG_GRAPHICS_ERROR
bool "Graphics Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable NX graphics subsystem error output to SYSLOG.
config DEBUG_GRAPHICS_WARN
bool "Graphics Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable NX graphics subsystem warning output to SYSLOG.
config DEBUG_GRAPHICS_INFO
bool "Graphics Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable NX graphics subsystem informational output to SYSLOG.
endif # DEBUG_GRAPHICS
config DEBUG_LIB
bool "C Library Debug Features"
default n
---help---
Enable C library debug features.
if DEBUG_LIB
config DEBUG_LIB_ERROR
bool "C Library Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable C library error output to SYSLOG.
config DEBUG_LIB_WARN
bool "C Library Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable C library warning output to SYSLOG.
config DEBUG_LIB_INFO
bool "C Library Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable C library informational output to SYSLOG.
config DEBUG_SYS_QUEUE
bool "Queue Debug option"
default n
---help---
Enable sys queue debug.
endif # DEBUG_LIB
config DEBUG_MM
bool "Memory Manager Debug Features"
default n
---help---
Enable memory management debug features.
if DEBUG_MM
config DEBUG_MM_ERROR
bool "Memory Manager Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable memory management error output to SYSLOG.
config DEBUG_MM_WARN
bool "Memory Manager Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable memory management warning output to SYSLOG.
config DEBUG_MM_INFO
bool "Memory Manager Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable memory management informational output to SYSLOG.
endif # DEBUG_MM
2014-09-23 16:46:31 +02:00
config DEBUG_SHM
bool "Shared Memory Debug Output"
default n
depends on MM_SHM
---help---
Enable shared memory management debug SYSLOG output (disabled by default)
config DEBUG_NET
bool "Network Debug Features"
default n
depends on ARCH_HAVE_NET
---help---
Enable network debug features.
if DEBUG_NET
config DEBUG_NET_ERROR
bool "Network Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable network error output to SYSLOG.
config DEBUG_NET_WARN
bool "Network Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable network warning output to SYSLOG.
config DEBUG_NET_INFO
bool "Network Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable network informational output to SYSLOG.
endif # DEBUG_NET
2017-07-23 15:17:56 +02:00
config DEBUG_POWER
bool "Power-related Debug Features"
default n
---help---
Enable power-related debug features.
if DEBUG_POWER
config DEBUG_POWER_ERROR
bool "Power-related Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable power-related error output to SYSLOG.
config DEBUG_POWER_WARN
bool "Power-related Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable power-related warning output to SYSLOG.
config DEBUG_POWER_INFO
bool "Power-related Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable power-related informational output to SYSLOG.
endif # DEBUG_POWER
config DEBUG_BATTERY
bool "Battery-related Debug Features"
default n
---help---
Enable Battery-related debug features.
if DEBUG_BATTERY
config DEBUG_BATTERY_ERROR
bool "Battery-related Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable battery-related error output to SYSLOG.
config DEBUG_BATTERY_WARN
bool "Battery-related Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable battery-related warning output to SYSLOG.
config DEBUG_BATTERY_INFO
bool "Battery-related Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable battery-related informational output to SYSLOG.
endif # DEBUG_BATTERY
config DEBUG_WIRELESS
bool "Wireless Debug Features"
default n
depends on WIRELESS || DRIVERS_WIRELESS
---help---
Enable wireless debug features.
if DEBUG_WIRELESS
config DEBUG_WIRELESS_ERROR
bool "Wireless Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable wireless error output to SYSLOG.
config DEBUG_WIRELESS_WARN
bool "Wireless Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable wireless warning output to SYSLOG.
config DEBUG_WIRELESS_INFO
bool "Wireless Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable wireless informational output to SYSLOG.
endif # DEBUG_WIRELESS
config DEBUG_SCHED
bool "Scheduler Debug Features"
default n
depends on !SYSLOG_TIMESTAMP
---help---
Enable OS scheduler debug features.
if DEBUG_SCHED
config DEBUG_SCHED_ERROR
bool "Scheduler Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable OS scheduler error output to SYSLOG.
config DEBUG_SCHED_WARN
bool "Scheduler Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable OS scheduler warning output to SYSLOG.
config DEBUG_SCHED_INFO
bool "Scheduler Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable OS scheduler informational output to SYSLOG.
endif # DEBUG_SCHED
config DEBUG_SYSCALL
bool "SYSCALL Debug Features"
default n
depends on LIB_SYSCALL
---help---
Enable very low level features related to system calls. If SYSCAL
output is enabled, this gives you basically a poor man's version of
strace.
if DEBUG_SYSCALL
config DEBUG_SYSCALL_ERROR
bool "SYSCALL Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable OS SYSCALL error output to SYSLOG.
config DEBUG_SYSCALL_WARN
bool "SYSCALL Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable OS SYSCALL warning output to SYSLOG.
config DEBUG_SYSCALL_INFO
bool "SYSCALL Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable OS SYSCALL informational output to SYSLOG.
endif # DEBUG_SYSCALL
comment "OS Function Debug Options"
config DEBUG_DMA
bool "DMA Debug Features"
2013-09-24 19:45:13 +02:00
default n
depends on ARCH_DMA
2013-09-24 19:45:13 +02:00
---help---
Enable DMA debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
2013-09-24 19:45:13 +02:00
if DEBUG_DMA
config DEBUG_DMA_ERROR
bool "DMA Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable DMA error output to SYSLOG.
config DEBUG_DMA_WARN
bool "DMA Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable DMA warning output to SYSLOG.
config DEBUG_DMA_INFO
bool "DMA Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable DMA informational output to SYSLOG.
endif # DEBUG_DMA
config DEBUG_IRQ
bool "Interrupt Controller Debug Features"
default n
---help---
Enable interrupt controller debug features.
Some (but not all) architectures support debug output to verify
interrupt controller logic. If supported, then option will enable
that output. This may interfere with normal operations! You
should *not* enable interrupt controller debug unless you suspect
that here is a problem with that logic. On some platforms, this
option may even cause crashes! Use with care!
if DEBUG_IRQ
config DEBUG_IRQ_ERROR
bool "Interrupt Controller Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable interrupt controller error output to SYSLOG.
config DEBUG_IRQ_WARN
bool "Interrupt Controller Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable interrupt controller warning output to SYSLOG.
config DEBUG_IRQ_INFO
bool "Interrupt Controller Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable interrupt controller informational output to SYSLOG.
endif # DEBUG_IRQ
config DEBUG_PAGING
bool "Paging Debug Features"
default n
depends on PAGING
---help---
Enable OS demand paging debug features.
if DEBUG_PAGING
config DEBUG_PAGING_ERROR
bool "Paging Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable OS demand paging error output to SYSLOG.
config DEBUG_PAGING_WARN
bool "Paging Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable OS demand paging warning output to SYSLOG.
config DEBUG_PAGING_INFO
bool "Paging Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable OS demand paging informational output to SYSLOG.
endif # DEBUG_PAGING
comment "Driver Debug Options"
config DEBUG_LCD
bool "Low-level LCD Debug Features"
default n
depends on LCD || SLCD
---help---
Enable LCD driver debug features.
Support for this debug option is board-specific and may not
be available for some boards.
if DEBUG_LCD
config DEBUG_LCD_ERROR
bool "LCD Driver Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable LCD driver error output to SYSLOG.
config DEBUG_LCD_WARN
bool "LCD Driver Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable LCD driver warning output to SYSLOG.
config DEBUG_LCD_INFO
bool "LCD Driver Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable LCD driver informational output to SYSLOG.
endif # DEBUG_LCD
config DEBUG_LEDS
bool "Low-level LED Debug Features"
default n
depends on ARCH_HAVE_LEDS || WS2812
---help---
Enable LED driver debug features.
Support for this debug option is board-specific and may not
be available for some boards.
if DEBUG_LEDS
config DEBUG_LEDS_ERROR
bool "LED Driver Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable LED driver error output to SYSLOG.
config DEBUG_LEDS_WARN
bool "LED Driver Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable LED driver warning output to SYSLOG.
config DEBUG_LEDS_INFO
bool "LED Driver Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable LED driver informational output to SYSLOG.
endif # DEBUG_LEDS
config DEBUG_INPUT
bool "Input Device Debug Features"
default n
depends on INPUT
---help---
Enable input d.
Enable low level device debug features for the input device drivers
such as mice and touchscreens (disabled by default). Support for
this debug option is board-specific and may not be available for
some boards.
if DEBUG_INPUT
config DEBUG_INPUT_ERROR
bool "Input Device Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable input device error output to SYSLOG.
config DEBUG_INPUT_WARN
bool "Input Device Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable input device warning output to SYSLOG.
config DEBUG_INPUT_INFO
bool "Input Device Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable input device informational output to SYSLOG.
endif # DEBUG_INPUT
config DEBUG_ANALOG
bool "Analog Device Debug Features"
default n
depends on ANALOG
---help---
Enable analog device debug features.
Enable low level debug features the analog device drivers such as
A/D and D/A converters (disabled by default). Support for this
debug option is architecture-specific and may not be available for
some MCUs.
if DEBUG_ANALOG
config DEBUG_ANALOG_ERROR
bool "Analog Device Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable analog device error output to SYSLOG.
config DEBUG_ANALOG_WARN
bool "Analog Device Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable analog device warning output to SYSLOG.
config DEBUG_ANALOG_INFO
bool "Analog Device Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable CAN driver informational output to SYSLOG.
endif # DEBUG_ANALOG
config DEBUG_CAN
bool "CAN Debug Features"
default n
depends on CAN
---help---
Enable CAN driver debug features.
2013-10-19 18:35:01 +02:00
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_CAN
config DEBUG_CAN_ERROR
bool "CAN Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable CAN driver error output to SYSLOG.
config DEBUG_CAN_WARN
bool "CAN Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable CAN driver warning output to SYSLOG.
config DEBUG_CAN_INFO
bool "CAN Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable CAN driver informational output to SYSLOG.
endif # DEBUG_CAN
config DEBUG_GPIO
bool "GPIO Debug Features"
default n
---help---
Enable GPIO debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_GPIO
config DEBUG_GPIO_ERROR
bool "GPIO Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable GPIO error output to SYSLOG.
config DEBUG_GPIO_WARN
bool "GPIO Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable GPIO warning output to SYSLOG.
config DEBUG_GPIO_INFO
bool "GPIO Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable GPIO informational output to SYSLOG.
endif # DEBUG_GPIO
config DEBUG_I2C
bool "I2C Debug Features"
default n
depends on I2C
---help---
Enable I2C debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_I2C
config DEBUG_I2C_ERROR
bool "I2C Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable I2C driver error output to SYSLOG.
config DEBUG_I2C_WARN
bool "I2C Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable I2C driver warning output to SYSLOG.
config DEBUG_I2C_INFO
bool "I2C Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable I2C driver informational output to SYSLOG.
endif # DEBUG_I2C
config DEBUG_I2S
bool "I2S Debug Features"
default n
depends on I2S
---help---
Enable I2S debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_I2S
config DEBUG_I2S_ERROR
bool "I2S Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable I2S driver error output to SYSLOG.
2013-10-19 18:35:01 +02:00
Support for this debug option is architecture-specific and may not
be available for some MCUs.
config DEBUG_I2S_WARN
bool "I2S Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable I2S driver warning output to SYSLOG.
config DEBUG_I2S_INFO
bool "I2S Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable I2S driver informational output to SYSLOG.
endif # DEBUG_I2S
config DEBUG_PWM
bool "PWM Debug Features"
default n
depends on PWM
---help---
Enable PWM debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_PWM
config DEBUG_PWM_ERROR
bool "PWM Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable PWM driver error output to SYSLOG.
2013-10-19 18:35:01 +02:00
Support for this debug option is architecture-specific and may not
be available for some MCUs.
config DEBUG_PWM_WARN
bool "PWM Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable PWM driver warning output to SYSLOG.
config DEBUG_PWM_INFO
bool "PWM Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable PWM driver informational output to SYSLOG.
endif # DEBUG_PWM
config DEBUG_CAPTURE
bool "CAPTURE Debug Features"
default n
depends on CAPTURE
---help---
Enable CAPTURE debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_CAPTURE
config DEBUG_CAPTURE_ERROR
bool "CAPTURE Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable CAPTURE driver error output to SYSLOG.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
config DEBUG_CAPTURE_WARN
bool "CAPTURE Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable CAPTURE driver warning output to SYSLOG.
config DEBUG_CAPTURE_INFO
bool "CAPTURE Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable CAPTURE driver informational output to SYSLOG.
endif # DEBUG_CAPTURE
config DEBUG_RC
bool "RC Debug Features"
default n
depends on DRIVERS_RC
---help---
Enable RC debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_RC
config DEBUG_RC_ERROR
bool "RC Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable RC driver error output to SYSLOG.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
config DEBUG_RC_WARN
bool "RC Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable RC driver warning output to SYSLOG.
config DEBUG_RC_INFO
bool "RC Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable RC driver informational output to SYSLOG.
endif # DEBUG_RC
config DEBUG_REGMAP
bool "REGMAP Debug Features"
default n
depends on REGMAP
---help---
Enable REGMAP debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_REGMAP
config DEBUG_REGMAP_ERROR
bool "Regmap Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable regmap subsystems error output to SYSLOG.
config DEBUG_REGMAP_WARN
bool "Regmap Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable regmap subsystems warning output to SYSLOG.
config DEBUG_REGMAP_INFO
bool "Regmap Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable regmap subsystems informational output to SYSLOG.
endif # DEBUG_REGMAP
config DEBUG_RMT
bool "RMT Debug Features"
default n
depends on RMT
---help---
Enable RMT debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_RMT
config DEBUG_RMT_ERROR
bool "RMT Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable RMT driver error output to SYSLOG.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
config DEBUG_RMT_WARN
bool "RMT Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable RMT driver warning output to SYSLOG.
config DEBUG_RMT_INFO
bool "RMT Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable RMT driver informational output to SYSLOG.
endif # DEBUG_RMT
config DEBUG_RTC
bool "RTC Debug Features"
default n
depends on RTC
---help---
Enable RTC debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_RTC
config DEBUG_RTC_ERROR
bool "RTC Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable RTC driver error output to SYSLOG.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
config DEBUG_RTC_WARN
bool "RTC Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable RTC driver warning output to SYSLOG.
config DEBUG_RTC_INFO
bool "RTC Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable RTC driver informational output to SYSLOG.
endif # DEBUG_RTC
config DEBUG_MEMCARD
bool "Memory Card Driver Debug Features"
default n
depends on MMCSD
---help---
Enable MMC/SD memory card Driver debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_MEMCARD
config DEBUG_MEMCARD_ERROR
bool "Memory Card Driver Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable MMC/SD memory card driver error output to SYSLOG.
2013-10-19 18:35:01 +02:00
Support for this debug option is architecture-specific and may not
be available for some MCUs.
config DEBUG_MEMCARD_WARN
bool "Memory Card Driver Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable MMC/SD memory card driver warning output to SYSLOG.
config DEBUG_MEMCARD_INFO
bool "Memory Card Driver Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable MMC/SD memory card driver informational output to SYSLOG.
endif # DEBUG_MEMCARD
config DEBUG_SENSORS
bool "Sensor Debug Features"
default n
depends on SENSORS
---help---
Enable sensor driver debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_SENSORS
config DEBUG_SENSORS_ERROR
bool "Sensor Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable sensor driver error output to SYSLOG.
config DEBUG_SENSORS_WARN
bool "Sensor Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable sensor driver warning output to SYSLOG.
config DEBUG_SENSORS_INFO
bool "Sensor Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable sensor driver informational output to SYSLOG.
endif # DEBUG_SENSORS
config DEBUG_SPI
bool "SPI Debug Features"
default n
depends on SPI
---help---
Enable SPI debug features.
2013-10-19 18:35:01 +02:00
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_SPI
config DEBUG_SPI_ERROR
bool "SPI Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable SPI error output to SYSLOG.
config DEBUG_SPI_WARN
bool "SPI Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable SPI warning output to SYSLOG.
config DEBUG_SPI_INFO
bool "SPI Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable SPI informational output to SYSLOG.
endif # DEBUG_SPI
config DEBUG_TIMER
bool "Timer Debug Features"
default n
---help---
Enable timer debug features.
2013-10-19 18:35:01 +02:00
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_TIMER
config DEBUG_TIMER_ERROR
bool "Timer Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable timer error output to SYSLOG.
config DEBUG_TIMER_WARN
bool "Timer Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable timer warning output to SYSLOG.
config DEBUG_TIMER_INFO
bool "Timer Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable timer informational output to SYSLOG.
endif # DEBUG_TIMER
config DEBUG_USB
bool "USB Debug Features"
2013-10-19 18:35:01 +02:00
default n
depends on USBDEV || USBHOST
2013-10-19 18:35:01 +02:00
---help---
Enable USB debug features.
if DEBUG_USB
config DEBUG_USB_ERROR
bool "USB Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable USB error output to SYSLOG.
config DEBUG_USB_WARN
bool "USB Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable USB warning output to SYSLOG.
config DEBUG_USB_INFO
bool "USB Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable USB informational output to SYSLOG.
endif # DEBUG_USB
config DEBUG_WATCHDOG
bool "Watchdog Timer Debug Features"
default n
depends on WATCHDOG
---help---
Enable watchdog timer debug features.
2013-10-19 18:35:01 +02:00
Support for this debug option is architecture-specific and may not
be available for some MCUs.
if DEBUG_WATCHDOG
config DEBUG_WATCHDOG_ERROR
bool "Watchdog Timer Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable watchdog time error output to SYSLOG.
config DEBUG_WATCHDOG_WARN
bool "Watchdog Timer Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable watchdog time warning output to SYSLOG.
config DEBUG_WATCHDOG_INFO
bool "Watchdog Timer Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable watchdog time informational output to SYSLOG.
endif # DEBUG_WATCHDOG
config DEBUG_MOTOR
bool "Motor Debug Features"
default n
depends on MOTOR
---help---
Enable motor debug features.
if DEBUG_MOTOR
config DEBUG_MOTOR_ERROR
bool "Motor Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable motor error output to SYSLOG.
config DEBUG_MOTOR_WARN
bool "Motor Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable motor warning output to SYSLOG.
config DEBUG_MOTOR_INFO
bool "Motor Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable motor informational output to SYSLOG.
endif # DEBUG_MOTOR
config DEBUG_STEPPER
bool "Stepper Motor Debug Features"
default n
depends on STEPPER
---help---
Enable motor debug features.
if DEBUG_STEPPER
config DEBUG_STEPPER_ERROR
bool "Stepper Motor Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable motor error output to SYSLOG.
config DEBUG_STEPPER_WARN
bool "Stepper Motor Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable motor warning output to SYSLOG.
config DEBUG_STEPPER_INFO
bool "Stepper Motor Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable motor informational output to SYSLOG.
endif # DEBUG_STEPPER
config DEBUG_VIDEO
bool "Video Debug Features"
default n
depends on DRIVERS_VIDEO
---help---
Enable video debug features.
if DEBUG_VIDEO
config DEBUG_VIDEO_ERROR
bool "Video Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable video error output to SYSLOG.
config DEBUG_VIDEO_WARN
bool "Video Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable video warning output to SYSLOG.
config DEBUG_VIDEO_INFO
bool "Video Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable video informational output to SYSLOG.
endif # DEBUG_VIDEO
config DEBUG_VIRTIO
bool "Virtio Debug Features"
default n
depends on DRIVERS_VIRTIO
---help---
Enable virtio debug features.
if DEBUG_VIRTIO
config DEBUG_VIRTIO_ERROR
bool "Virtio Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable virtio error output to SYSLOG.
config DEBUG_VIRTIO_WARN
bool "Virtio Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable virtio warning output to SYSLOG.
config DEBUG_VIRTIO_INFO
bool "Virtio Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable virtio informational output to SYSLOG.
endif # DEBUG_VIDEO
config DEBUG_RESET
bool "RESET Debug Features"
default n
depends on RESET
---help---
Enable RESET debug features.
if DEBUG_RESET
config DEBUG_RESET_ERROR
bool "RESET Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable RESET driver error output to SYSLOG.
config DEBUG_RESET_INFO
bool "RESET Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable RESET driver informational output to SYSLOG.
endif # DEBUG_RESET
config DEBUG_IPC
bool "IPC (Interprocessor communication) Debug Features"
default n
---help---
Enable IPC debug features.
if DEBUG_IPC
config DEBUG_IPC_ERROR
bool "IPC Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable IPC error output to SYSLOG.
config DEBUG_IPC_WARN
bool "IPC Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable IPC warning output to SYSLOG.
config DEBUG_IPC_INFO
bool "IPC Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable IPC informational output to SYSLOG.
endif # DEBUG_IPC
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
config DEBUG_PCI
bool "PCI Debug Features"
default n
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
depends on PCI
---help---
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
Enable PCI driver debug features.
Support for this debug option is architecture-specific and may not
be available for some MCUs.
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
if DEBUG_PCI
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
config DEBUG_PCI_ERROR
bool "PCI Error Output"
default n
depends on DEBUG_ERROR
---help---
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
Enable PCI driver error output to SYSLOG.
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
config DEBUG_PCI_WARN
bool "PCI Warnings Output"
default n
depends on DEBUG_WARN
---help---
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
Enable PCI driver warning output to SYSLOG.
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
config DEBUG_PCI_INFO
bool "PCI Informational Output"
default n
depends on DEBUG_INFO
---help---
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
Enable PCI driver informational output to SYSLOG.
Various fixes for PCI work Squashed commits: 1. Porting prior PCI work in place of jailhouse code At this point the PCI enumeration works for x86_64 including over pci-pci bridges. Running QEMU with this configuration we see the bridge and the device on the bridge. It also detected the qemu test device qemu-system-x86_64 \ -cpu host,+pcid,+x2apic,+tsc-deadline,+xsave,+rdrand \ --enable-kvm -smp 1 -m 2G -cdrom boot.iso --nographic -no-reboot \ -device pci-testdev \ -device pci-bridge,id=bridge0,chassis_nr=2 \ -device e1000,bus=bridge0,addr=0x3 qemu_pci_init: Initializing PCI Bus pci_probe_device: [00:00.0] Found 8086:1237, class/revision 06000002 pci_probe_device: [00:01.1] Found 8086:7010, class/revision 01018000 pci_probe_device: [00:01.2] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.3] Found 8086:7113, class/revision 06800003 pci_probe_device: [00:01.4] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.5] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.6] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:01.7] Found ffff:ffff, class/revision ffffffff pci_probe_device: [00:02.0] Found 1234:1111, class/revision 03000002 pci_probe_device: [00:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:04.0] Found 1b36:0005, class/revision 00ff0000 pci_probe_device: [00:04.0] Probing pci_check_pci_bridge: [00:05.0] Found Bridge pci_probe_device: [01:03.0] Found 8086:100e, class/revision 02000003 pci_probe_device: [00:05.0] Found 1b36:0001, class/revision 06040000 2. Remove unused CONFIG_PCI_MAX_BDF option 3. Add a workaround for Jailhouse pci scanning 4. Extend BAR parsing and handle PIO and MMIO for pci-testdev Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 5. PCI: Add initial support for QEMU 'edu' test device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 6. Bring up PCI later in boot process Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 7. Add ISR and DMA support to QEMU edu test pci device Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 8. Fix bad function prototype definition in qemu_edu 9. intel64: Add a pci test configuration and instructions Signed-off-by: Brennan Ashton <bashton@brennanashton.com> 10. PCI: Fix issue in identification of 64bit bar Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
2020-05-07 11:59:29 +02:00
endif # DEBUG_PCI
config DEBUG_RPMSG
bool "RPMSG Debug Features"
default n
depends on RPMSG
---help---
Enable RPMSG driver debug features.
if DEBUG_RPMSG
config DEBUG_RPMSG_ERROR
bool "RPMSG Error Output"
default n
depends on DEBUG_ERROR
---help---
Enable RPMSG driver error output to SYSLOG.
config DEBUG_RPMSG_WARN
bool "RPMSG Warnings Output"
default n
depends on DEBUG_WARN
---help---
Enable RPMSG driver warning output to SYSLOG.
config DEBUG_RPMSG_INFO
bool "RPMSG Informational Output"
default n
depends on DEBUG_INFO
---help---
Enable RPMSG driver informational output to SYSLOG.
endif # DEBUG_RPMSG
endif # DEBUG_FEATURES
config ARCH_HAVE_STACKCHECK
bool
default n
config STACK_COLORATION
bool "Stack coloration"
default n
depends on ARCH_HAVE_STACKCHECK
---help---
Enable stack coloration to initialize the stack memory to the value
of STACK_COLOR and enable the stack checking APIs that can be used
to monitor the level of stack usage.
Only supported by a few architectures.
config STACK_CANARIES
bool "Compiler stack canaries"
depends on ARCH_HAVE_STACKCHECK
default n
---help---
This option enables compiler stack canaries.
If stack canaries are supported by the compiler, it will emit
extra code that inserts a canary value into the stack frame when
a function is entered and validates this value upon exit.
Stack corruption (such as that caused by buffer overflow) results
in a fatal error condition for the running entity.
Enabling this option can result in a significant increase
in footprint and an associated decrease in performance.
config STACK_USAGE
bool "Generate stack usage information"
---help---
Generate an extra file that specifies the maximum amount of stack used,
on a per-function basis. Please use https://github.com/HBehrens/puncover
or tools/showstack.sh to generate the more useful report.
config STACK_USAGE_WARNING
int "Detect use of large stack variables"
default 0
---help---
Set the stack warning threshold, if the stack usage exceeds the
threshold, a warning will be generated
config ARCH_HAVE_HEAPCHECK
bool
default n
config HEAP_COLORATION
bool "Heap coloration"
default n
depends on ARCH_HAVE_HEAPCHECK
---help---
Enable heap coloration to check heap usage. Only supported by a few
architectures.
config DEBUG_SYMBOLS
bool "Generate Debug Symbols"
default n
---help---
Build with debug symbols (needed for use with a debugger).
config FRAME_POINTER
bool "Compile the NuttX with frame pointers"
default n
---help---
If you say Y here the resulting NuttX image will be slightly
larger and slower, but it gives very useful debugging information
in case of bugs.
endmenu # Debug Options
menuconfig TRACE
bool "Enable tracepoints"
default n
depends on SCHED_INSTRUMENTATION_DUMP
---help---
If this option is enabled, tracepoints at critical code in
the kernel will be enabled.
if TRACE
config TRACE_AUDIO
bool "Enable tracepoints in audio"
default n
config TRACE_ARCH
bool "Enable tracepoints in arch"
default n
config TRACE_BOARDS
bool "Enable tracepoints in boards"
default n
config TRACE_CRYPTO
bool "Enable tracepoints in crypto"
default n
config TRACE_DRIVERS
bool "Enable tracepoints in drivers"
default n
config TRACE_FS
bool "Enable tracepoints in fs"
default n
config TRACE_GRAPHICS
bool "Enable tracepoints in graphics"
default n
config TRACE_LIBS
bool "Enable tracepoints in libs"
default n
config TRACE_NET
bool "Enable tracepoints in net"
default n
config TRACE_SCHED
bool "Enable tracepoints in sched"
default n
config TRACE_VIDEO
bool "Enable tracepoints in video"
default n
config TRACE_WIRELESS
bool "Enable tracepoints in wireless"
default n
endif #TRACE
config ARCH_HAVE_CUSTOMOPT
bool
default n
choice
prompt "Optimization Level"
default DEBUG_NOOPT if DEBUG_SYMBOLS
default DEBUG_FULLOPT if !DEBUG_SYMBOLS
config DEBUG_NOOPT
bool "Suppress Optimization"
---help---
Build without optimization. This is often helpful when debugging code.
config DEBUG_CUSTOMOPT
bool "Custom Optimization"
depends on ARCH_HAVE_CUSTOMOPT
---help---
Select a custom debug level. This is often helpful if you suspect an
optimization level error and want to lower the level of optimization.
config DEBUG_FULLOPT
bool "Normal, Full optimization"
---help---
Build full optimization. This is the normal case for production
firmware.
endchoice # Optimization Level
config DEBUG_OPTLEVEL
string "Custom Optimization Level"
default "/O2" if HOST_WINDOWS
default "-O2"
depends on DEBUG_CUSTOMOPT
---help---
2016-03-19 15:08:18 +01:00
This string represents the custom optimization level that will be
used if DEBUG_CUSTOMOPT.
choice
prompt "Link Time Optimization (LTO)"
default LTO_NONE
---help---
This option enables Link Time Optimization (LTO), which allows the
compiler to optimize binaries globally.
If unsure, select LTO_NONE. Note that LTO is very resource-intensive
so it's disabled by default.
config LTO_NONE
bool "None"
---help---
Build the kernel normally, without Link Time Optimization (LTO).
config LTO_FULL
bool "GNU Full LTO (EXPERIMENTAL)"
depends on ARCH_TOOLCHAIN_GNU
---help---
Link time optimization is implemented as a GCC front end for a bytecode
bytecode representation of GIMPLE that is emitted in special sections
of .o files. Currently, LTO support is enabled in most ELF-based systems,
as well as darwin, cygwin and mingw systems.
config LTO_THIN
bool "Clang ThinLTO (EXPERIMENTAL)"
depends on ARCH_TOOLCHAIN_CLANG
---help---
This option enables Clang's ThinLTO, which allows for parallel
optimization and faster incremental compiles compared to the
CONFIG_LTO_FULL option. More information can be found
from Clang's documentation:
https://clang.llvm.org/docs/ThinLTO.html
If unsure, say Y.
endchoice
config DEBUG_OPT_UNUSED_SECTIONS
bool "Optimization to eliminate the unused input sections"
default y
depends on ARCH_TOOLCHAIN_GNU
---help---
Use these options on systems where the linker can perform optimizations
to improve locality of reference in the instruction space. Most systems
using the ELF object format have linkers with such optimizations.
Enable this option to optimization the unused input sections with the
linker by compiling with " -ffunction-sections -fdata-sections ", and
linking with " --gc-sections ".
config DEBUG_LINK_WHOLE_ARCHIVE
bool "Force every object to be included in the resulting shared library."
default n
depends on DEBUG_OPT_UNUSED_SECTIONS
---help---
Selecting this option will pass "--whole-archive" to ld
when linking NuttX ELF.
config DEBUG_LINK_MAP
bool "Generate link map file"
default y
---help---
Selecting this option will pass "-Map=$(TOPDIR)$(DELIM)nuttx.map" to ld
when linking NuttX ELF. That file can be useful for verifying
and debugging magic section games, and for seeing which
pieces of code get eliminated with DEBUG_OPT_UNUSED_SECTIONS.
2022-10-10 15:42:36 +02:00
config CCACHE
bool "Use ccache"
default n
---help---
If enabled, ccache will be used during the build.
Build artifacts will be cached to a local storage, considerably
reducing build times.
endmenu # Build Setup
menu "System Type"
source "arch/Kconfig"
endmenu
menu "Board Selection"
Merged in alinjerpelea/nuttx (pull request #963) Move boards to boards folder * boards: rename configs folder to boards This is the proposed layout after the change: boards: - folder containing board folders <board>: - name of each board drivers: - extra drivers specific for platform include: - header files for the boars scripts: - extra scripts specific for platform src: - board specific code tools: - extra tools specific for platform <config>: - board specific configuration(s) Note: <xxx> names are dependent on platform This is a logical change to aim to the arch layout but this is a huge change it should be done in several steps to lower the risk. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * Kconfig: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * Makefile: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * Makefile.*: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * Make.defs: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * .sh: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * .mk: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * .c & .h: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> * .bat: replace configs with boards The change is needed after the path change Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> Approved-by: Gregory Nutt <gnutt@nuttx.org>
2019-08-05 14:04:14 +02:00
source "boards/Kconfig"
endmenu
menu "RTOS Features"
source "sched/Kconfig"
source "syscall/Kconfig"
endmenu
menu "Device Drivers"
source "drivers/Kconfig"
endmenu
menu "Networking Support"
source "net/Kconfig"
endmenu
menu "Crypto API"
source "crypto/Kconfig"
endmenu
menu "File Systems"
source "fs/Kconfig"
endmenu
menu "Graphics Support"
source "graphics/Kconfig"
source "libs/libnx/Kconfig"
endmenu
menu "Memory Management"
source "mm/Kconfig"
endmenu
menu "Audio Support"
source "audio/Kconfig"
endmenu
menu "Video Support"
source "video/Kconfig"
endmenu
2016-02-27 00:07:04 +01:00
menu "Wireless Support"
source "wireless/Kconfig"
2016-02-27 00:07:04 +01:00
endmenu
2014-10-15 18:57:04 +02:00
menu "Binary Loader"
source "binfmt/Kconfig"
endmenu
menu "Library Routines"
source "libs/libc/Kconfig"
source "libs/libm/Kconfig"
source "libs/libxx/Kconfig"
source "libs/libdsp/Kconfig"
endmenu
This commit brings in the drivers needed to support OpenAMP. These changes were ported from https://github.com/FishsemiCode/nuttx. The current state: Most drivers do now compile but are not yet verfied. This port was effort of a number of people, I rather arbitrarily gave authorship to Guiding Li because he has the largest number of fundamental quashed commits from the Xiamoi repository. Squashed commit of the following: Author: Xiang Xiao <xiaoxiang@pinecone.net> include/nuttx/b2c.h and libx/libc/string: Add non-standard string functions to deal with cases where there are more than 8-bits in a type char. Author: Gregory Nutt <gnutt@nuttx.org> Fix several build issues/missing definitiona needed for OpenAMP build in drivers/. Add OpenAMP code has been reviewed and ran through tools/nxstyle (with all reports accounted for). Author: Xiang Xiao <xiaoxiang@xiaomi.com> tools/: Fix the minor issue in Makefile Author: Gregory Nutt <gnutt@nuttx.org> drivers/rptun/rptun.c: Review for coding standard. Run against tools/nxstyle. tools/LibTargets.mk: Fix some TABs that were turned into spaces by a copy-paste. fs/hostfs: Add configure and build support for hostfs RPC. drivers/timer: Add configure and build support for syslog RTC. drivers/syslog: Add configure and build support for syslog RPC. drivers/serial: Add configure and build support for serial RPC. Kconfig, tools/*.mk. openamp/: Add basic OpenAMP build support. drivers/rptun: Add configure and build support for OpenAMP tunnel drivers. drivers/net: Update Make.defs and Kconfig for OpenSDA support. Remove drivers/clk/clk-rpmsg.c drivers/power/rpmsg_regulator.c. These depend on upstreaming support for a new subsystem based on the clk/regulator is model from Linux. Removed because we want to separate the activities. We will just try to get the basic OpenAMP support in place for now. Remove drivers/misc/misc_rpmsg.c and include/nuttx/misc/misc_rpmsg.h. These are specific to the Xiaomi application. Author: zhuyanlin <zhuyanlin@pinecone.net> This commit brings in the OpenAMP OS driver/RPC components from https://github.com/FishsemiCode/nuttx. Initial commit is source files only. Additional changes to Kconfig and Make.defs files still needed. Author: Jianli Dong <dongjianli@pinecone.net> This commit brings in the OpenAMP OS driver/RPC components from https://github.com/FishsemiCode/nuttx. Initial commit is source files only. Additional changes to Kconfig and Make.defs files still needed. Author: Guiding Li <liguiding@pinecone.net> This commit brings in the OpenAMP OS driver/RPC components from https://github.com/FishsemiCode/nuttx. Initial commit is source files only. Additional changes to Kconfig and Make.defs files still needed.
2019-11-02 18:30:33 +01:00
menu "Open Asymmetric Multi Processing"
source "openamp/Kconfig"
This commit brings in the drivers needed to support OpenAMP. These changes were ported from https://github.com/FishsemiCode/nuttx. The current state: Most drivers do now compile but are not yet verfied. This port was effort of a number of people, I rather arbitrarily gave authorship to Guiding Li because he has the largest number of fundamental quashed commits from the Xiamoi repository. Squashed commit of the following: Author: Xiang Xiao <xiaoxiang@pinecone.net> include/nuttx/b2c.h and libx/libc/string: Add non-standard string functions to deal with cases where there are more than 8-bits in a type char. Author: Gregory Nutt <gnutt@nuttx.org> Fix several build issues/missing definitiona needed for OpenAMP build in drivers/. Add OpenAMP code has been reviewed and ran through tools/nxstyle (with all reports accounted for). Author: Xiang Xiao <xiaoxiang@xiaomi.com> tools/: Fix the minor issue in Makefile Author: Gregory Nutt <gnutt@nuttx.org> drivers/rptun/rptun.c: Review for coding standard. Run against tools/nxstyle. tools/LibTargets.mk: Fix some TABs that were turned into spaces by a copy-paste. fs/hostfs: Add configure and build support for hostfs RPC. drivers/timer: Add configure and build support for syslog RTC. drivers/syslog: Add configure and build support for syslog RPC. drivers/serial: Add configure and build support for serial RPC. Kconfig, tools/*.mk. openamp/: Add basic OpenAMP build support. drivers/rptun: Add configure and build support for OpenAMP tunnel drivers. drivers/net: Update Make.defs and Kconfig for OpenSDA support. Remove drivers/clk/clk-rpmsg.c drivers/power/rpmsg_regulator.c. These depend on upstreaming support for a new subsystem based on the clk/regulator is model from Linux. Removed because we want to separate the activities. We will just try to get the basic OpenAMP support in place for now. Remove drivers/misc/misc_rpmsg.c and include/nuttx/misc/misc_rpmsg.h. These are specific to the Xiaomi application. Author: zhuyanlin <zhuyanlin@pinecone.net> This commit brings in the OpenAMP OS driver/RPC components from https://github.com/FishsemiCode/nuttx. Initial commit is source files only. Additional changes to Kconfig and Make.defs files still needed. Author: Jianli Dong <dongjianli@pinecone.net> This commit brings in the OpenAMP OS driver/RPC components from https://github.com/FishsemiCode/nuttx. Initial commit is source files only. Additional changes to Kconfig and Make.defs files still needed. Author: Guiding Li <liguiding@pinecone.net> This commit brings in the OpenAMP OS driver/RPC components from https://github.com/FishsemiCode/nuttx. Initial commit is source files only. Additional changes to Kconfig and Make.defs files still needed.
2019-11-02 18:30:33 +01:00
endmenu
menu "Application Configuration"
source "$APPSBINDIR/Kconfig"
endmenu
# Support optionally including external code
# into the OS build. EXTERNALDIR will be used
# to either point to 'nuttx/external' or
# 'nuttx/dummy', if 'nuttx/external'
# does not contain a Kconfig file
config EXTERNALDIR
string
option env="EXTERNALDIR"
source "$EXTERNALDIR/Kconfig"