Orange Pi5 kernel

Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards

3 Commits   0 Branches   0 Tags
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   1) # SPDX-License-Identifier: GPL-2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   2) menu "Generic Driver Options"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   3) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   4) config UEVENT_HELPER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   5) 	bool "Support for uevent helper"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   6) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   7) 	  The uevent helper program is forked by the kernel for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   8) 	  every uevent.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   9) 	  Before the switch to the netlink-based uevent source, this was
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  10) 	  used to hook hotplug scripts into kernel device events. It
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  11) 	  usually pointed to a shell script at /sbin/hotplug.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  12) 	  This should not be used today, because usual systems create
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  13) 	  many events at bootup or device discovery in a very short time
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  14) 	  frame. One forked process per event can create so many processes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  15) 	  that it creates a high system load, or on smaller systems
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  16) 	  it is known to create out-of-memory situations during bootup.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  17) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  18) config UEVENT_HELPER_PATH
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  19) 	string "path to uevent helper"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  20) 	depends on UEVENT_HELPER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  21) 	default ""
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  22) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  23) 	  To disable user space helper program execution at by default
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  24) 	  specify an empty string here. This setting can still be altered
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  25) 	  via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  26) 	  later at runtime.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  27) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  28) config DEVTMPFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  29) 	bool "Maintain a devtmpfs filesystem to mount at /dev"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  30) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  31) 	  This creates a tmpfs/ramfs filesystem instance early at bootup.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  32) 	  In this filesystem, the kernel driver core maintains device
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  33) 	  nodes with their default names and permissions for all
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  34) 	  registered devices with an assigned major/minor number.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  35) 	  Userspace can modify the filesystem content as needed, add
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  36) 	  symlinks, and apply needed permissions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  37) 	  It provides a fully functional /dev directory, where usually
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  38) 	  udev runs on top, managing permissions and adding meaningful
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  39) 	  symlinks.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  40) 	  In very limited environments, it may provide a sufficient
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  41) 	  functional /dev without any further help. It also allows simple
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  42) 	  rescue systems, and reliably handles dynamic major/minor numbers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  43) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  44) 	  Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  45) 	  file system will be used instead.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  46) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  47) config DEVTMPFS_MOUNT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  48) 	bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  49) 	depends on DEVTMPFS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  50) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  51) 	  This will instruct the kernel to automatically mount the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  52) 	  devtmpfs filesystem at /dev, directly after the kernel has
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  53) 	  mounted the root filesystem. The behavior can be overridden
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  54) 	  with the commandline parameter: devtmpfs.mount=0|1.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  55) 	  This option does not affect initramfs based booting, here
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  56) 	  the devtmpfs filesystem always needs to be mounted manually
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  57) 	  after the rootfs is mounted.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  58) 	  With this option enabled, it allows to bring up a system in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  59) 	  rescue mode with init=/bin/sh, even when the /dev directory
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  60) 	  on the rootfs is completely empty.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  61) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  62) config STANDALONE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  63) 	bool "Select only drivers that don't need compile-time external firmware"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  64) 	default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  65) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  66) 	  Select this option if you don't have magic firmware for drivers that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  67) 	  need it.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  68) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  69) 	  If unsure, say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  70) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  71) config PREVENT_FIRMWARE_BUILD
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  72) 	bool "Disable drivers features which enable custom firmware building"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  73) 	default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  74) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  75) 	  Say yes to disable driver features which enable building a custom
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  76) 	  driver firmware at kernel build time. These drivers do not use the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  77) 	  kernel firmware API to load firmware (CONFIG_FW_LOADER), instead they
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  78) 	  use their own custom loading mechanism. The required firmware is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  79) 	  usually shipped with the driver, building the driver firmware
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  80) 	  should only be needed if you have an updated firmware source.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  81) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  82) 	  Firmware should not be being built as part of kernel, these days
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  83) 	  you should always prevent this and say Y here. There are only two
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  84) 	  old drivers which enable building of its firmware at kernel build
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  85) 	  time:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  86) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  87) 	    o CONFIG_WANXL through CONFIG_WANXL_BUILD_FIRMWARE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  88) 	    o CONFIG_SCSI_AIC79XX through CONFIG_AIC79XX_BUILD_FIRMWARE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  89) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  90) source "drivers/base/firmware_loader/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  91) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  92) config WANT_DEV_COREDUMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  93) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  94) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  95) 	  Drivers should "select" this option if they desire to use the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  96) 	  device coredump mechanism.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  97) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  98) config ALLOW_DEV_COREDUMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  99) 	bool "Allow device coredump" if EXPERT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) 	default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) 	  This option controls if the device coredump mechanism is available or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) 	  not; if disabled, the mechanism will be omitted even if drivers that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) 	  can use it are enabled.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) 	  Say 'N' for more sensitive systems or systems that don't want
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) 	  to ever access the information to not have the code, nor keep any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) 	  data.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) 	  If unsure, say Y.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) config DEV_COREDUMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) 	default y if WANT_DEV_COREDUMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) 	depends on ALLOW_DEV_COREDUMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) config DEBUG_DRIVER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) 	bool "Driver Core verbose debug messages"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) 	depends on DEBUG_KERNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) 	  Say Y here if you want the Driver core to produce a bunch of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) 	  debug messages to the system log. Select this if you are having a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) 	  problem with the driver core and want to see more of what is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) 	  going on.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) 	  If you are unsure about this, say N here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) config DEBUG_DEVRES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) 	bool "Managed device resources verbose debug messages"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) 	depends on DEBUG_KERNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) 	  This option enables kernel parameter devres.log. If set to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) 	  non-zero, devres debug messages are printed. Select this if
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) 	  you are having a problem with devres or want to debug
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) 	  resource management for a managed device. devres.log can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) 	  switched on and off from sysfs node.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) 	  If you are unsure about this, Say N here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) config DEBUG_TEST_DRIVER_REMOVE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) 	bool "Test driver remove calls during probe (UNSTABLE)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) 	depends on DEBUG_KERNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) 	  Say Y here if you want the Driver core to test driver remove functions
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) 	  by calling probe, remove, probe. This tests the remove path without
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) 	  having to unbind the driver or unload the driver module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) 	  This option is expected to find errors and may render your system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) 	  unusable. You should say N here unless you are explicitly looking to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) 	  test this functionality.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) config PM_QOS_KUNIT_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) 	bool "KUnit Test for PM QoS features" if !KUNIT_ALL_TESTS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) 	depends on KUNIT=y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) 	default KUNIT_ALL_TESTS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) config HMEM_REPORTING
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) 	default n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) 	depends on NUMA
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) 	  Enable reporting for heterogenous memory access attributes under
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) 	  their non-uniform memory nodes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) source "drivers/base/test/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) config SYS_HYPERVISOR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) 	default n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) config GENERIC_CPU_DEVICES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) 	default n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) config GENERIC_CPU_AUTOPROBE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) config GENERIC_CPU_VULNERABILITIES
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) config SOC_BUS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) 	select GLOB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) source "drivers/base/regmap/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) source "drivers/base/arm/Kconfig"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) config DMA_SHARED_BUFFER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) 	default n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) 	select IRQ_WORK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) 	  This option enables the framework for buffer-sharing between
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) 	  multiple drivers. A buffer is associated with a file using driver
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) 	  APIs extension; the file's descriptor can then be passed on to other
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) 	  driver.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) config DMA_FENCE_TRACE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) 	bool "Enable verbose DMA_FENCE_TRACE messages"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) 	depends on DMA_SHARED_BUFFER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) 	  Enable the DMA_FENCE_TRACE printks. This will add extra
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) 	  spam to the console log, but will make it easier to diagnose
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) 	  lockup related problems for dma-buffers shared across multiple
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) 	  devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) config GENERIC_ARCH_TOPOLOGY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) 	bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) 	help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) 	  Enable support for architectures common topology code: e.g., parsing
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) 	  CPU capacity information from DT, usage of such information for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) 	  appropriate scaling, sysfs interface for reading capacity values at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) 	  runtime.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) endmenu