treewide: replace '---help---' in Kconfig files with 'help'
Since commit 84af7a6194 ("checkpatch: kconfig: prefer 'help' over
'---help---'"), the number of '---help---' has been gradually
decreasing, but there are still more than 2400 instances.
This commit finishes the conversion. While I touched the lines,
I also fixed the indentation.
There are a variety of indentation styles found.
a) 4 spaces + '---help---'
b) 7 spaces + '---help---'
c) 8 spaces + '---help---'
d) 1 space + 1 tab + '---help---'
e) 1 tab + '---help---' (correct indentation)
f) 1 tab + 1 space + '---help---'
g) 1 tab + 2 spaces + '---help---'
In order to convert all of them to 1 tab + 'help', I ran the
following commend:
$ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
This commit is contained in:
Masahiro Yamada
Родитель
e4a42c82e9
Коммит
a7f7f6248d
|
|
@ -876,7 +876,7 @@ config VMAP_STACK
|
|||
bool "Use a virtually-mapped stack"
|
||||
depends on HAVE_ARCH_VMAP_STACK
|
||||
depends on !KASAN || KASAN_VMALLOC
|
||||
---help---
|
||||
help
|
||||
Enable this if you want the use virtually-mapped kernel stacks
|
||||
with guard pages. This causes kernel stack overflows to be
|
||||
caught immediately rather than causing difficult-to-diagnose
|
||||
|
|
@ -948,7 +948,7 @@ config ARCH_USE_MEMREMAP_PROT
|
|||
config LOCK_EVENT_COUNTS
|
||||
bool "Locking event counts collection"
|
||||
depends on DEBUG_FS
|
||||
---help---
|
||||
help
|
||||
Enable light-weight counting of various locking related events
|
||||
in the system with minimal performance impact. This reduces
|
||||
the chance of application behavior change because of timing
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ menu "System setup"
|
|||
choice
|
||||
prompt "Alpha system type"
|
||||
default ALPHA_GENERIC
|
||||
---help---
|
||||
help
|
||||
This is the system type of your hardware. A "generic" kernel will
|
||||
run on any supported Alpha system. However, if you configure a
|
||||
kernel for your specific system, it will be faster and smaller.
|
||||
|
|
@ -480,7 +480,7 @@ config VGA_HOSE
|
|||
config ALPHA_QEMU
|
||||
bool "Run under QEMU emulation"
|
||||
depends on !ALPHA_GENERIC
|
||||
---help---
|
||||
help
|
||||
Assume the presence of special features supported by QEMU PALcode
|
||||
that reduce the overhead of system emulation.
|
||||
|
||||
|
|
@ -495,7 +495,7 @@ config ALPHA_SRM
|
|||
bool "Use SRM as bootloader" if ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_NAUTILUS || ALPHA_NONAME
|
||||
depends on TTY
|
||||
default y if ALPHA_JENSEN || ALPHA_MIKASA || ALPHA_SABLE || ALPHA_LYNX || ALPHA_NORITAKE || ALPHA_DP264 || ALPHA_RAWHIDE || ALPHA_EIGER || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK || ALPHA_MARVEL
|
||||
---help---
|
||||
help
|
||||
There are two different types of booting firmware on Alphas: SRM,
|
||||
which is command line driven, and ARC, which uses menus and arrow
|
||||
keys. Details about the Linux/Alpha booting process are contained in
|
||||
|
|
@ -521,7 +521,7 @@ config ARCH_MAY_HAVE_PC_FDC
|
|||
config SMP
|
||||
bool "Symmetric multi-processing support"
|
||||
depends on ALPHA_SABLE || ALPHA_LYNX || ALPHA_RAWHIDE || ALPHA_DP264 || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_GENERIC || ALPHA_SHARK || ALPHA_MARVEL
|
||||
---help---
|
||||
help
|
||||
This enables support for systems with more than one CPU. If you have
|
||||
a system with only one CPU, say N. If you have a system with more
|
||||
than one CPU, say Y.
|
||||
|
|
@ -569,7 +569,7 @@ config ALPHA_WTINT
|
|||
default n if ALPHA_EV5 || ALPHA_EV56 || (ALPHA_EV4 && !ALPHA_LCA)
|
||||
default n if !ALPHA_SRM && !ALPHA_GENERIC
|
||||
default y if SMP
|
||||
---help---
|
||||
help
|
||||
The Wait for Interrupt (WTINT) PALcall attempts to place the CPU
|
||||
to sleep until the next interrupt. This may reduce the power
|
||||
consumed, and the heat produced by the computer. However, it has
|
||||
|
|
@ -595,7 +595,7 @@ config NODES_SHIFT
|
|||
# LARGE_VMALLOC is racy, if you *really* need it then fix it first
|
||||
config ALPHA_LARGE_VMALLOC
|
||||
bool
|
||||
---help---
|
||||
help
|
||||
Process creation and other aspects of virtual memory management can
|
||||
be streamlined if we restrict the kernel to one PGD for all vmalloc
|
||||
allocations. This equates to about 8GB.
|
||||
|
|
@ -614,7 +614,7 @@ config VERBOSE_MCHECK_ON
|
|||
int "Verbose Printing Mode (0=off, 1=on, 2=all)"
|
||||
depends on VERBOSE_MCHECK
|
||||
default 1
|
||||
---help---
|
||||
help
|
||||
This option allows the default printing mode to be set, and then
|
||||
possibly overridden by a boot command argument.
|
||||
|
||||
|
|
@ -633,7 +633,7 @@ choice
|
|||
default HZ_128 if ALPHA_QEMU
|
||||
default HZ_1200 if ALPHA_RAWHIDE
|
||||
default HZ_1024
|
||||
---help---
|
||||
help
|
||||
The frequency at which timer interrupts occur. A high frequency
|
||||
minimizes latency, whereas a low frequency minimizes overhead of
|
||||
process accounting. The later effect is especially significant
|
||||
|
|
@ -668,7 +668,7 @@ config HZ
|
|||
config SRM_ENV
|
||||
tristate "SRM environment through procfs"
|
||||
depends on PROC_FS
|
||||
---help---
|
||||
help
|
||||
If you enable this option, a subdirectory inside /proc called
|
||||
/proc/srm_environment will give you access to the all important
|
||||
SRM environment variables (those which have a name) and also
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ config ALPHA_LEGACY_START_ADDRESS
|
|||
bool "Legacy kernel start address"
|
||||
depends on ALPHA_GENERIC
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
The 2.4 kernel changed the kernel start address from 0x310000
|
||||
to 0x810000 to make room for the Wildfire's larger SRM console.
|
||||
Recent consoles on Titan and Marvel machines also require the
|
||||
|
|
|
|||
|
|
@ -348,7 +348,7 @@ config NODES_SHIFT
|
|||
default "0" if !DISCONTIGMEM
|
||||
default "1" if DISCONTIGMEM
|
||||
depends on NEED_MULTIPLE_NODES
|
||||
---help---
|
||||
help
|
||||
Accessing memory beyond 1GB (with or w/o PAE) requires 2 memory
|
||||
zones.
|
||||
|
||||
|
|
|
|||
|
|
@ -1655,7 +1655,7 @@ config UACCESS_WITH_MEMCPY
|
|||
config SECCOMP
|
||||
bool
|
||||
prompt "Enable seccomp to safely compute untrusted bytecode"
|
||||
---help---
|
||||
help
|
||||
This kernel feature is useful for number crunching applications
|
||||
that may need to compute untrusted bytecode during their
|
||||
execution. By using pipes or other transports made available to
|
||||
|
|
@ -1963,7 +1963,7 @@ config EFI
|
|||
select EFI_STUB
|
||||
select EFI_GENERIC_STUB
|
||||
select EFI_RUNTIME_WRAPPERS
|
||||
---help---
|
||||
help
|
||||
This option provides support for runtime services provided
|
||||
by UEFI firmware (such as non-volatile variables, realtime
|
||||
clock, and platform reset). A UEFI stub is also provided to
|
||||
|
|
@ -2005,7 +2005,7 @@ comment "At least one emulation must be selected"
|
|||
config FPE_NWFPE
|
||||
bool "NWFPE math emulation"
|
||||
depends on (!AEABI || OABI_COMPAT) && !THUMB2_KERNEL
|
||||
---help---
|
||||
help
|
||||
Say Y to include the NWFPE floating point emulator in the kernel.
|
||||
This is necessary to run most binaries. Linux does not currently
|
||||
support floating point hardware so you need to say Y here even if
|
||||
|
|
@ -2029,7 +2029,7 @@ config FPE_NWFPE_XP
|
|||
config FPE_FASTFPE
|
||||
bool "FastFPE math emulation (EXPERIMENTAL)"
|
||||
depends on (!AEABI || OABI_COMPAT) && !CPU_32v3
|
||||
---help---
|
||||
help
|
||||
Say Y here to include the FAST floating point emulator in the kernel.
|
||||
This is an experimental much faster emulator which now also has full
|
||||
precision for the mantissa. It does not support any exceptions.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ config ARM_PTDUMP_DEBUGFS
|
|||
depends on MMU
|
||||
select ARM_PTDUMP_CORE
|
||||
select DEBUG_FS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to show the kernel pagetable layout in a
|
||||
debugfs file. This information is only useful for kernel developers
|
||||
who are working in architecture specific areas of the kernel.
|
||||
|
|
@ -21,7 +21,7 @@ config DEBUG_WX
|
|||
bool "Warn on W+X mappings at boot"
|
||||
depends on MMU
|
||||
select ARM_PTDUMP_CORE
|
||||
---help---
|
||||
help
|
||||
Generate a warning if any W+X mappings are found at boot.
|
||||
|
||||
This is useful for discovering cases where the kernel is leaving
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ config ARCH_PERSONAL_SERVER
|
|||
select ISA
|
||||
select ISA_DMA
|
||||
select FORCE_PCI
|
||||
---help---
|
||||
help
|
||||
Say Y here if you intend to run this kernel on the Compaq
|
||||
Personal Server.
|
||||
|
||||
|
|
|
|||
|
|
@ -1035,7 +1035,7 @@ config CC_HAVE_SHADOW_CALL_STACK
|
|||
|
||||
config SECCOMP
|
||||
bool "Enable seccomp to safely compute untrusted bytecode"
|
||||
---help---
|
||||
help
|
||||
This kernel feature is useful for number crunching applications
|
||||
that may need to compute untrusted bytecode during their
|
||||
execution. By using pipes or other transports made available to
|
||||
|
|
@ -1068,7 +1068,7 @@ config KEXEC
|
|||
depends on PM_SLEEP_SMP
|
||||
select KEXEC_CORE
|
||||
bool "kexec system call"
|
||||
---help---
|
||||
help
|
||||
kexec is a system call that implements the ability to shutdown your
|
||||
current kernel, and to start another kernel. It is like a reboot
|
||||
but it is independent of the system firmware. And like a reboot
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ source "virt/lib/Kconfig"
|
|||
|
||||
menuconfig VIRTUALIZATION
|
||||
bool "Virtualization"
|
||||
---help---
|
||||
help
|
||||
Say Y here to get to see options for using your Linux host to run
|
||||
other operating systems inside virtual machines (guests).
|
||||
This option alone does not add any kernel code.
|
||||
|
|
@ -40,7 +40,7 @@ menuconfig KVM
|
|||
select HAVE_KVM_VCPU_RUN_PID_CHANGE
|
||||
select TASKSTATS
|
||||
select TASK_DELAY_ACCT
|
||||
---help---
|
||||
help
|
||||
Support hosting virtualized guest machines.
|
||||
|
||||
If unsure, say N.
|
||||
|
|
@ -53,7 +53,7 @@ config KVM_ARM_PMU
|
|||
bool "Virtual Performance Monitoring Unit (PMU) support"
|
||||
depends on HW_PERF_EVENTS
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Adds support for a virtual Performance Monitoring Unit (PMU) in
|
||||
virtual machines.
|
||||
|
||||
|
|
|
|||
|
|
@ -31,13 +31,13 @@ config HEXAGON
|
|||
select GENERIC_CLOCKEVENTS_BROADCAST
|
||||
select MODULES_USE_ELF_RELA
|
||||
select GENERIC_CPU_DEVICES
|
||||
---help---
|
||||
help
|
||||
Qualcomm Hexagon is a processor architecture designed for high
|
||||
performance and low power across a wide variety of applications.
|
||||
|
||||
config HEXAGON_PHYS_OFFSET
|
||||
def_bool y
|
||||
---help---
|
||||
help
|
||||
Platforms that don't load the kernel at zero set this.
|
||||
|
||||
config FRAME_POINTER
|
||||
|
|
@ -83,7 +83,7 @@ choice
|
|||
|
||||
config HEXAGON_COMET
|
||||
bool "Comet Board"
|
||||
---help---
|
||||
help
|
||||
Support for the Comet platform.
|
||||
|
||||
endchoice
|
||||
|
|
@ -104,7 +104,7 @@ config CMDLINE
|
|||
|
||||
config SMP
|
||||
bool "Multi-Processing support"
|
||||
---help---
|
||||
help
|
||||
Enables SMP support in the kernel. If unsure, say "Y"
|
||||
|
||||
config NR_CPUS
|
||||
|
|
@ -112,7 +112,7 @@ config NR_CPUS
|
|||
range 2 6 if SMP
|
||||
default "1" if !SMP
|
||||
default "6" if SMP
|
||||
---help---
|
||||
help
|
||||
This allows you to specify the maximum number of CPUs which this
|
||||
kernel will support. The maximum supported value is 6 and the
|
||||
minimum value which makes sense is 2.
|
||||
|
|
@ -123,7 +123,7 @@ config NR_CPUS
|
|||
choice
|
||||
prompt "Kernel page size"
|
||||
default PAGE_SIZE_4KB
|
||||
---help---
|
||||
help
|
||||
Changes the default page size; use with caution.
|
||||
|
||||
config PAGE_SIZE_4KB
|
||||
|
|
|
|||
|
|
@ -243,7 +243,7 @@ config HOTPLUG_CPU
|
|||
bool "Support for hot-pluggable CPUs"
|
||||
depends on SMP
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
Say Y here to experiment with turning CPUs off and on. CPUs
|
||||
can be controlled through /sys/devices/system/cpu/cpu#.
|
||||
Say N if you want to disable CPU hotplug.
|
||||
|
|
@ -266,7 +266,7 @@ config PERMIT_BSP_REMOVE
|
|||
bool "Support removal of Bootstrap Processor"
|
||||
depends on HOTPLUG_CPU
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
|
||||
support.
|
||||
|
||||
|
|
@ -274,7 +274,7 @@ config FORCE_CPEI_RETARGET
|
|||
bool "Force assumption that CPEI can be re-targeted"
|
||||
depends on PERMIT_BSP_REMOVE
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
Say Y if you need to force the assumption that CPEI can be re-targeted to
|
||||
any cpu in the system. This hint is available via ACPI 3.0 specifications.
|
||||
Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
|
||||
|
|
|
|||
|
|
@ -343,7 +343,7 @@ config M68KFPU_EMU_ONLY
|
|||
config ADVANCED
|
||||
bool "Advanced configuration options"
|
||||
depends on MMU
|
||||
---help---
|
||||
help
|
||||
This gives you access to some advanced options for the CPU. The
|
||||
defaults should be fine for most users, but these options may make
|
||||
it possible for you to improve performance somewhat if you know what
|
||||
|
|
@ -358,7 +358,7 @@ config ADVANCED
|
|||
config RMW_INSNS
|
||||
bool "Use read-modify-write instructions"
|
||||
depends on ADVANCED
|
||||
---help---
|
||||
help
|
||||
This allows to use certain instructions that work with indivisible
|
||||
read-modify-write bus cycles. While this is faster than the
|
||||
workaround of disabling interrupts, it can conflict with DMA
|
||||
|
|
@ -386,7 +386,7 @@ config ARCH_DISCONTIGMEM_ENABLE
|
|||
config 060_WRITETHROUGH
|
||||
bool "Use write-through caching for 68060 supervisor accesses"
|
||||
depends on ADVANCED && M68060
|
||||
---help---
|
||||
help
|
||||
The 68060 generally uses copyback caching of recently accessed data.
|
||||
Copyback caching means that memory writes will be held in an on-chip
|
||||
cache and only written back to memory some time later. Saying Y
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ config NFETH
|
|||
config ATARI_ETHERNAT
|
||||
bool "Atari EtherNAT Ethernet support"
|
||||
depends on ATARI
|
||||
---help---
|
||||
help
|
||||
Say Y to include support for the EtherNAT network adapter for the
|
||||
CT/60 extension port.
|
||||
|
||||
|
|
@ -69,7 +69,7 @@ config ATARI_ETHERNAT
|
|||
config ATARI_ETHERNEC
|
||||
bool "Atari EtherNEC Ethernet support"
|
||||
depends on ATARI_ROM_ISA
|
||||
---help---
|
||||
help
|
||||
Say Y to include support for the EtherNEC network adapter for the
|
||||
ROM port. The driver works by polling instead of interrupts, so it
|
||||
is quite slow.
|
||||
|
|
@ -120,7 +120,7 @@ config HPAPCI
|
|||
config SERIAL_CONSOLE
|
||||
bool "Support for serial port console"
|
||||
depends on AMIGA_BUILTIN_SERIAL=y
|
||||
---help---
|
||||
help
|
||||
If you say Y here, it will be possible to use a serial port as the
|
||||
system console (the system console is the device which receives all
|
||||
kernel messages and warnings and which allows logins in single user
|
||||
|
|
|
|||
|
|
@ -437,7 +437,7 @@ config ROMSIZE
|
|||
|
||||
choice
|
||||
prompt "Kernel executes from"
|
||||
---help---
|
||||
help
|
||||
Choose the memory type that the kernel will be running in.
|
||||
|
||||
config RAMKERNEL
|
||||
|
|
|
|||
|
|
@ -2741,7 +2741,7 @@ config RELOCATION_TABLE_SIZE
|
|||
depends on RELOCATABLE
|
||||
range 0x0 0x01000000
|
||||
default "0x00100000"
|
||||
---help---
|
||||
help
|
||||
A table of relocation data will be appended to the kernel binary
|
||||
and parsed at boot to fix up the relocated kernel.
|
||||
|
||||
|
|
@ -2755,7 +2755,7 @@ config RELOCATION_TABLE_SIZE
|
|||
config RANDOMIZE_BASE
|
||||
bool "Randomize the address of the kernel image"
|
||||
depends on RELOCATABLE
|
||||
---help---
|
||||
help
|
||||
Randomizes the physical and virtual address at which the
|
||||
kernel image is loaded, as a security feature that
|
||||
deters exploit attempts relying on knowledge of the location
|
||||
|
|
@ -2773,7 +2773,7 @@ config RANDOMIZE_BASE_MAX_OFFSET
|
|||
range 0x0 0x40000000 if EVA || 64BIT
|
||||
range 0x0 0x08000000
|
||||
default "0x01000000"
|
||||
---help---
|
||||
help
|
||||
When kASLR is active, this provides the maximum offset that will
|
||||
be applied to the kernel image. It should be set according to the
|
||||
amount of physical RAM available in the target system minus
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ source "virt/kvm/Kconfig"
|
|||
|
||||
menuconfig VIRTUALIZATION
|
||||
bool "Virtualization"
|
||||
---help---
|
||||
help
|
||||
Say Y here to get to see options for using your Linux host to run
|
||||
other operating systems inside virtual machines (guests).
|
||||
This option alone does not add any kernel code.
|
||||
|
|
@ -26,7 +26,7 @@ config KVM
|
|||
select KVM_MMIO
|
||||
select MMU_NOTIFIER
|
||||
select SRCU
|
||||
---help---
|
||||
help
|
||||
Support for hosting Guest kernels.
|
||||
|
||||
choice
|
||||
|
|
@ -36,7 +36,7 @@ choice
|
|||
|
||||
config KVM_MIPS_TE
|
||||
bool "Trap & Emulate"
|
||||
---help---
|
||||
help
|
||||
Use trap and emulate to virtualize 32-bit guests in user mode. This
|
||||
does not require any special hardware Virtualization support beyond
|
||||
standard MIPS32/64 r2 or later, but it does require the guest kernel
|
||||
|
|
@ -45,7 +45,7 @@ config KVM_MIPS_TE
|
|||
|
||||
config KVM_MIPS_VZ
|
||||
bool "MIPS Virtualization (VZ) ASE"
|
||||
---help---
|
||||
help
|
||||
Use the MIPS Virtualization (VZ) ASE to virtualize guests. This
|
||||
supports running unmodified guest kernels (with CONFIG_KVM_GUEST=n),
|
||||
but requires hardware support.
|
||||
|
|
@ -56,7 +56,7 @@ config KVM_MIPS_DYN_TRANS
|
|||
bool "KVM/MIPS: Dynamic binary translation to reduce traps"
|
||||
depends on KVM_MIPS_TE
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
When running in Trap & Emulate mode patch privileged
|
||||
instructions to reduce the number of traps.
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ config KVM_MIPS_DYN_TRANS
|
|||
config KVM_MIPS_DEBUG_COP0_COUNTERS
|
||||
bool "Maintain counters for COP0 accesses"
|
||||
depends on KVM
|
||||
---help---
|
||||
help
|
||||
Maintain statistics for Guest COP0 accesses.
|
||||
A histogram of COP0 accesses is printed when the VM is
|
||||
shutdown.
|
||||
|
|
|
|||
|
|
@ -147,7 +147,7 @@ choice
|
|||
|
||||
config PA7000
|
||||
bool "PA7000/PA7100"
|
||||
---help---
|
||||
help
|
||||
This is the processor type of your CPU. This information is
|
||||
used for optimizing purposes. In order to compile a kernel
|
||||
that can run on all 32-bit PA CPUs (albeit not optimally fast),
|
||||
|
|
@ -275,7 +275,7 @@ config PARISC_SELF_EXTRACT
|
|||
|
||||
config SMP
|
||||
bool "Symmetric multi-processing support"
|
||||
---help---
|
||||
help
|
||||
This enables support for systems with more than one CPU. If you have
|
||||
a system with only one CPU, say N. If you have a system with more
|
||||
than one CPU, say Y.
|
||||
|
|
@ -382,7 +382,7 @@ source "drivers/parisc/Kconfig"
|
|||
config SECCOMP
|
||||
def_bool y
|
||||
prompt "Enable seccomp to safely compute untrusted bytecode"
|
||||
---help---
|
||||
help
|
||||
This kernel feature is useful for number crunching applications
|
||||
that may need to compute untrusted bytecode during their
|
||||
execution. By using pipes or other transports made available to
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ source "virt/kvm/Kconfig"
|
|||
|
||||
menuconfig VIRTUALIZATION
|
||||
bool "Virtualization"
|
||||
---help---
|
||||
help
|
||||
Say Y here to get to see options for using your Linux host to run
|
||||
other operating systems inside virtual machines (guests).
|
||||
This option alone does not add any kernel code.
|
||||
|
|
@ -54,7 +54,7 @@ config KVM_BOOK3S_32
|
|||
select KVM
|
||||
select KVM_BOOK3S_32_HANDLER
|
||||
select KVM_BOOK3S_PR_POSSIBLE
|
||||
---help---
|
||||
help
|
||||
Support running unmodified book3s_32 guest kernels
|
||||
in virtual machines on book3s_32 host processors.
|
||||
|
||||
|
|
@ -70,7 +70,7 @@ config KVM_BOOK3S_64
|
|||
select KVM
|
||||
select KVM_BOOK3S_PR_POSSIBLE if !KVM_BOOK3S_HV_POSSIBLE
|
||||
select SPAPR_TCE_IOMMU if IOMMU_SUPPORT && (PPC_PSERIES || PPC_POWERNV)
|
||||
---help---
|
||||
help
|
||||
Support running unmodified book3s_64 and book3s_32 guest kernels
|
||||
in virtual machines on book3s_64 host processors.
|
||||
|
||||
|
|
@ -85,7 +85,7 @@ config KVM_BOOK3S_64_HV
|
|||
select KVM_BOOK3S_HV_POSSIBLE
|
||||
select MMU_NOTIFIER
|
||||
select CMA
|
||||
---help---
|
||||
help
|
||||
Support running unmodified book3s_64 guest kernels in
|
||||
virtual machines on POWER7 and newer processors that have
|
||||
hypervisor mode available to the host.
|
||||
|
|
@ -104,7 +104,7 @@ config KVM_BOOK3S_64_PR
|
|||
tristate "KVM support without using hypervisor mode in host"
|
||||
depends on KVM_BOOK3S_64
|
||||
select KVM_BOOK3S_PR_POSSIBLE
|
||||
---help---
|
||||
help
|
||||
Support running guest kernels in virtual machines on processors
|
||||
without using hypervisor mode in the host, by running the
|
||||
guest in user mode (problem state) and emulating all
|
||||
|
|
@ -119,7 +119,7 @@ config KVM_BOOK3S_64_PR
|
|||
config KVM_BOOK3S_HV_EXIT_TIMING
|
||||
bool "Detailed timing for hypervisor real-mode code"
|
||||
depends on KVM_BOOK3S_HV_POSSIBLE && DEBUG_FS
|
||||
---help---
|
||||
help
|
||||
Calculate time taken for each vcpu in the real-mode guest entry,
|
||||
exit, and interrupt handling code, plus time spent in the guest
|
||||
and in nap mode due to idle (cede) while other threads are still
|
||||
|
|
@ -136,7 +136,7 @@ config KVM_BOOKE_HV
|
|||
config KVM_EXIT_TIMING
|
||||
bool "Detailed exit timing"
|
||||
depends on KVM_E500V2 || KVM_E500MC
|
||||
---help---
|
||||
help
|
||||
Calculate elapsed time for every exit/enter cycle. A per-vcpu
|
||||
report is available in debugfs kvm/vm#_vcpu#_timing.
|
||||
The overhead is relatively small, however it is not recommended for
|
||||
|
|
@ -150,7 +150,7 @@ config KVM_E500V2
|
|||
select KVM
|
||||
select KVM_MMIO
|
||||
select MMU_NOTIFIER
|
||||
---help---
|
||||
help
|
||||
Support running unmodified E500 guest kernels in virtual machines on
|
||||
E500v2 host processors.
|
||||
|
||||
|
|
@ -166,7 +166,7 @@ config KVM_E500MC
|
|||
select KVM_MMIO
|
||||
select KVM_BOOKE_HV
|
||||
select MMU_NOTIFIER
|
||||
---help---
|
||||
help
|
||||
Support running unmodified E500MC/E5500/E6500 guest kernels in
|
||||
virtual machines on E500MC/E5500/E6500 host processors.
|
||||
|
||||
|
|
@ -194,7 +194,7 @@ config KVM_XICS
|
|||
select HAVE_KVM_IRQCHIP
|
||||
select HAVE_KVM_IRQFD
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Include support for the XICS (eXternal Interrupt Controller
|
||||
Specification) interrupt controller architecture used on
|
||||
IBM POWER (pSeries) servers.
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ source "arch/powerpc/platforms/amigaone/Kconfig"
|
|||
config KVM_GUEST
|
||||
bool "KVM Guest support"
|
||||
select EPAPR_PARAVIRT
|
||||
---help---
|
||||
help
|
||||
This option enables various optimizations for running under the KVM
|
||||
hypervisor. Overhead for the kernel when not running inside KVM should
|
||||
be minimal.
|
||||
|
|
@ -230,7 +230,7 @@ config TAU
|
|||
config TAU_INT
|
||||
bool "Interrupt driven TAU driver (DANGEROUS)"
|
||||
depends on TAU
|
||||
---help---
|
||||
help
|
||||
The TAU supports an interrupt driven mode which causes an interrupt
|
||||
whenever the temperature goes out of range. This is the fastest way
|
||||
to get notified the temp has exceeded a range. With this option off,
|
||||
|
|
@ -246,7 +246,7 @@ config TAU_INT
|
|||
config TAU_AVERAGE
|
||||
bool "Average high and low temp"
|
||||
depends on TAU
|
||||
---help---
|
||||
help
|
||||
The TAU hardware can compare the temperature to an upper and lower
|
||||
bound. The default behavior is to show both the upper and lower
|
||||
bound in /proc/cpuinfo. If the range is large, the temperature is
|
||||
|
|
|
|||
|
|
@ -280,7 +280,7 @@ config PHYS_64BIT
|
|||
bool 'Large physical address support' if E500 || PPC_86xx
|
||||
depends on (44x || E500 || PPC_86xx) && !PPC_83xx && !PPC_82xx
|
||||
select PHYS_ADDR_T_64BIT
|
||||
---help---
|
||||
help
|
||||
This option enables kernel support for larger than 32-bit physical
|
||||
addresses. This feature may not be available on all cores.
|
||||
|
||||
|
|
@ -293,7 +293,7 @@ config PHYS_64BIT
|
|||
config ALTIVEC
|
||||
bool "AltiVec Support"
|
||||
depends on PPC_BOOK3S_32 || PPC_BOOK3S_64 || (PPC_E500MC && PPC64)
|
||||
---help---
|
||||
help
|
||||
This option enables kernel support for the Altivec extensions to the
|
||||
PowerPC processor. The kernel currently supports saving and restoring
|
||||
altivec registers, and turning on the 'altivec enable' bit so user
|
||||
|
|
@ -309,7 +309,7 @@ config ALTIVEC
|
|||
config VSX
|
||||
bool "VSX Support"
|
||||
depends on PPC_BOOK3S_64 && ALTIVEC && PPC_FPU
|
||||
---help---
|
||||
help
|
||||
|
||||
This option enables kernel support for the Vector Scaler extensions
|
||||
to the PowerPC processor. The kernel currently supports saving and
|
||||
|
|
@ -330,7 +330,7 @@ config SPE
|
|||
bool "SPE Support"
|
||||
depends on SPE_POSSIBLE
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
This option enables kernel support for the Signal Processing
|
||||
Extensions (SPE) to the PowerPC processor. The kernel currently
|
||||
supports saving and restoring SPE registers, and turning on the
|
||||
|
|
@ -446,7 +446,7 @@ config SMP
|
|||
depends on PPC_BOOK3S || PPC_BOOK3E || FSL_BOOKE || PPC_47x
|
||||
select GENERIC_IRQ_MIGRATION
|
||||
bool "Symmetric multi-processing support" if !FORCE_SMP
|
||||
---help---
|
||||
help
|
||||
This enables support for systems with more than one CPU. If you have
|
||||
a system with only one CPU, say N. If you have a system with more
|
||||
than one CPU, say Y. Note that the kernel does not currently
|
||||
|
|
|
|||
|
|
@ -696,7 +696,7 @@ menu "I/O subsystem"
|
|||
config QDIO
|
||||
def_tristate y
|
||||
prompt "QDIO support"
|
||||
---help---
|
||||
help
|
||||
This driver provides the Queued Direct I/O base support for
|
||||
IBM System z.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ config S390_PTDUMP
|
|||
bool "Export kernel pagetable layout to userspace via debugfs"
|
||||
depends on DEBUG_KERNEL
|
||||
select DEBUG_FS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to show the kernel pagetable layout in a
|
||||
debugfs file. This information is only useful for kernel developers
|
||||
who are working in architecture specific areas of the kernel.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ source "virt/kvm/Kconfig"
|
|||
menuconfig VIRTUALIZATION
|
||||
def_bool y
|
||||
prompt "KVM"
|
||||
---help---
|
||||
help
|
||||
Say Y here to get to see options for using your Linux host to run other
|
||||
operating systems inside virtual machines (guests).
|
||||
This option alone does not add any kernel code.
|
||||
|
|
@ -33,7 +33,7 @@ config KVM
|
|||
select HAVE_KVM_NO_POLL
|
||||
select SRCU
|
||||
select KVM_VFIO
|
||||
---help---
|
||||
help
|
||||
Support hosting paravirtualized guest machines using the SIE
|
||||
virtualization capability on the mainframe. This should work
|
||||
on any 64bit machine.
|
||||
|
|
@ -49,7 +49,7 @@ config KVM
|
|||
config KVM_S390_UCONTROL
|
||||
bool "Userspace controlled virtual machines"
|
||||
depends on KVM
|
||||
---help---
|
||||
help
|
||||
Allow CAP_SYS_ADMIN users to create KVM virtual machines that are
|
||||
controlled by userspace.
|
||||
|
||||
|
|
|
|||
|
|
@ -588,7 +588,7 @@ config KEXEC_JUMP
|
|||
config PHYSICAL_START
|
||||
hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)
|
||||
default MEMORY_START
|
||||
---help---
|
||||
help
|
||||
This gives the physical address where the kernel is loaded
|
||||
and is ordinarily the same as MEMORY_START.
|
||||
|
||||
|
|
@ -615,7 +615,7 @@ config SECCOMP
|
|||
config SMP
|
||||
bool "Symmetric multi-processing support"
|
||||
depends on SYS_SUPPORTS_SMP
|
||||
---help---
|
||||
help
|
||||
This enables support for systems with more than one CPU. If you have
|
||||
a system with only one CPU, say N. If you have a system with more
|
||||
than one CPU, say Y.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ choice
|
|||
|
||||
config HD64461
|
||||
bool "Hitachi HD64461 companion chip support"
|
||||
---help---
|
||||
help
|
||||
The Hitachi HD64461 provides an interface for
|
||||
the SH7709 CPU, supporting a LCD controller,
|
||||
CRT color controller, IrDA up to 4 Mbps, and a
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ config FORCE_MAX_ZONEORDER
|
|||
config MEMORY_START
|
||||
hex "Physical memory start address"
|
||||
default "0x08000000"
|
||||
---help---
|
||||
help
|
||||
Computers built with Hitachi SuperH processors always
|
||||
map the ROM starting at address zero. But the processor
|
||||
does not specify the range that RAM takes.
|
||||
|
|
|
|||
|
|
@ -159,7 +159,7 @@ menu "Processor type and features"
|
|||
|
||||
config SMP
|
||||
bool "Symmetric multi-processing support"
|
||||
---help---
|
||||
help
|
||||
This enables support for systems with more than one CPU. If you have
|
||||
a system with only one CPU, say N. If you have a system with more
|
||||
than one CPU, say Y.
|
||||
|
|
@ -366,7 +366,7 @@ config SERIAL_CONSOLE
|
|||
bool
|
||||
depends on SPARC32
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
If you say Y here, it will be possible to use a serial port as the
|
||||
system console (the system console is the device which receives all
|
||||
kernel messages and warnings and which allows logins in single user
|
||||
|
|
@ -393,7 +393,7 @@ config SPARC_LEON
|
|||
select USB_EHCI_BIG_ENDIAN_DESC
|
||||
select USB_UHCI_BIG_ENDIAN_MMIO
|
||||
select USB_UHCI_BIG_ENDIAN_DESC
|
||||
---help---
|
||||
help
|
||||
If you say Y here if you are running on a SPARC-LEON processor.
|
||||
The LEON processor is a synthesizable VHDL model of the
|
||||
SPARC-v8 standard. LEON is part of the GRLIB collection of
|
||||
|
|
@ -407,7 +407,7 @@ menu "U-Boot options"
|
|||
config UBOOT_LOAD_ADDR
|
||||
hex "uImage Load Address"
|
||||
default 0x40004000
|
||||
---help---
|
||||
help
|
||||
U-Boot kernel load address, the address in physical address space
|
||||
where u-boot will place the Linux kernel before booting it.
|
||||
This address is normally the base address of main memory + 0x4000.
|
||||
|
|
@ -415,7 +415,7 @@ config UBOOT_LOAD_ADDR
|
|||
config UBOOT_FLASH_ADDR
|
||||
hex "uImage.o Load Address"
|
||||
default 0x00080000
|
||||
---help---
|
||||
help
|
||||
Optional setting only affecting the uImage.o ELF-image used to
|
||||
download the uImage file to the target using a ELF-loader other than
|
||||
U-Boot. It may for example be used to download an uImage to FLASH with
|
||||
|
|
@ -424,7 +424,7 @@ config UBOOT_FLASH_ADDR
|
|||
config UBOOT_ENTRY_ADDR
|
||||
hex "uImage Entry Address"
|
||||
default 0xf0004000
|
||||
---help---
|
||||
help
|
||||
Do not change this unless you know what you're doing. This is
|
||||
hardcoded by the SPARC32 and LEON port.
|
||||
|
||||
|
|
|
|||
|
|
@ -179,7 +179,7 @@ config PGTABLE_LEVELS
|
|||
config SECCOMP
|
||||
def_bool y
|
||||
prompt "Enable seccomp to safely compute untrusted bytecode"
|
||||
---help---
|
||||
help
|
||||
This kernel feature is useful for number crunching applications
|
||||
that may need to compute untrusted bytecode during their
|
||||
execution. By using pipes or other transports made available to
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ config GCOV
|
|||
config EARLY_PRINTK
|
||||
bool "Early printk"
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Write kernel log output directly to stdout.
|
||||
|
||||
This is useful for kernel debugging when your machine crashes very
|
||||
|
|
|
|||
276
arch/x86/Kconfig
276
arch/x86/Kconfig
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
|
|
@ -4,7 +4,7 @@ choice
|
|||
prompt "Processor family"
|
||||
default M686 if X86_32
|
||||
default GENERIC_CPU if X86_64
|
||||
---help---
|
||||
help
|
||||
This is the processor type of your CPU. This information is
|
||||
used for optimizing purposes. In order to compile a kernel
|
||||
that can run on all supported x86 CPU types (albeit not
|
||||
|
|
@ -53,21 +53,21 @@ choice
|
|||
config M486SX
|
||||
bool "486SX"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for an 486-class CPU without an FPU such as
|
||||
AMD/Cyrix/IBM/Intel SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5S.
|
||||
|
||||
config M486
|
||||
bool "486DX"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for an 486-class CPU such as AMD/Cyrix/IBM/Intel
|
||||
486DX/DX2/DX4 and UMC U5D.
|
||||
|
||||
config M586
|
||||
bool "586/K5/5x86/6x86/6x86MX"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for an 586 or 686 series processor such as the AMD K5,
|
||||
the Cyrix 5x86, 6x86 and 6x86MX. This choice does not
|
||||
assume the RDTSC (Read Time Stamp Counter) instruction.
|
||||
|
|
@ -75,21 +75,21 @@ config M586
|
|||
config M586TSC
|
||||
bool "Pentium-Classic"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for a Pentium Classic processor with the RDTSC (Read
|
||||
Time Stamp Counter) instruction for benchmarking.
|
||||
|
||||
config M586MMX
|
||||
bool "Pentium-MMX"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for a Pentium with the MMX graphics/multimedia
|
||||
extended instructions.
|
||||
|
||||
config M686
|
||||
bool "Pentium-Pro"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for Intel Pentium Pro chips. This enables the use of
|
||||
Pentium Pro extended instructions, and disables the init-time guard
|
||||
against the f00f bug found in earlier Pentiums.
|
||||
|
|
@ -97,7 +97,7 @@ config M686
|
|||
config MPENTIUMII
|
||||
bool "Pentium-II/Celeron(pre-Coppermine)"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for Intel chips based on the Pentium-II and
|
||||
pre-Coppermine Celeron core. This option enables an unaligned
|
||||
copy optimization, compiles the kernel with optimization flags
|
||||
|
|
@ -107,7 +107,7 @@ config MPENTIUMII
|
|||
config MPENTIUMIII
|
||||
bool "Pentium-III/Celeron(Coppermine)/Pentium-III Xeon"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for Intel chips based on the Pentium-III and
|
||||
Celeron-Coppermine core. This option enables use of some
|
||||
extended prefetch instructions in addition to the Pentium II
|
||||
|
|
@ -116,14 +116,14 @@ config MPENTIUMIII
|
|||
config MPENTIUMM
|
||||
bool "Pentium M"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for Intel Pentium M (not Pentium-4 M)
|
||||
notebook chips.
|
||||
|
||||
config MPENTIUM4
|
||||
bool "Pentium-4/Celeron(P4-based)/Pentium-4 M/older Xeon"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for Intel Pentium 4 chips. This includes the
|
||||
Pentium 4, Pentium D, P4-based Celeron and Xeon, and
|
||||
Pentium-4 M (not Pentium M) chips. This option enables compile
|
||||
|
|
@ -159,7 +159,7 @@ config MPENTIUM4
|
|||
config MK6
|
||||
bool "K6/K6-II/K6-III"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for an AMD K6-family processor. Enables use of
|
||||
some extended instructions, and passes appropriate optimization
|
||||
flags to GCC.
|
||||
|
|
@ -167,14 +167,14 @@ config MK6
|
|||
config MK7
|
||||
bool "Athlon/Duron/K7"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for an AMD Athlon K7-family processor. Enables use of
|
||||
some extended instructions, and passes appropriate optimization
|
||||
flags to GCC.
|
||||
|
||||
config MK8
|
||||
bool "Opteron/Athlon64/Hammer/K8"
|
||||
---help---
|
||||
help
|
||||
Select this for an AMD Opteron or Athlon64 Hammer-family processor.
|
||||
Enables use of some extended instructions, and passes appropriate
|
||||
optimization flags to GCC.
|
||||
|
|
@ -182,7 +182,7 @@ config MK8
|
|||
config MCRUSOE
|
||||
bool "Crusoe"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for a Transmeta Crusoe processor. Treats the processor
|
||||
like a 586 with TSC, and sets some GCC optimization flags (like a
|
||||
Pentium Pro with no alignment requirements).
|
||||
|
|
@ -190,13 +190,13 @@ config MCRUSOE
|
|||
config MEFFICEON
|
||||
bool "Efficeon"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for a Transmeta Efficeon processor.
|
||||
|
||||
config MWINCHIPC6
|
||||
bool "Winchip-C6"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for an IDT Winchip C6 chip. Linux and GCC
|
||||
treat this chip as a 586TSC with some extended instructions
|
||||
and alignment requirements.
|
||||
|
|
@ -204,7 +204,7 @@ config MWINCHIPC6
|
|||
config MWINCHIP3D
|
||||
bool "Winchip-2/Winchip-2A/Winchip-3"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for an IDT Winchip-2, 2A or 3. Linux and GCC
|
||||
treat this chip as a 586TSC with some extended instructions
|
||||
and alignment requirements. Also enable out of order memory
|
||||
|
|
@ -214,7 +214,7 @@ config MWINCHIP3D
|
|||
config MELAN
|
||||
bool "AMD Elan"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for an AMD Elan processor.
|
||||
|
||||
Do not use this option for K6/Athlon/Opteron processors!
|
||||
|
|
@ -222,19 +222,19 @@ config MELAN
|
|||
config MGEODEGX1
|
||||
bool "GeodeGX1"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for a Geode GX1 (Cyrix MediaGX) chip.
|
||||
|
||||
config MGEODE_LX
|
||||
bool "Geode GX/LX"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for AMD Geode GX and LX processors.
|
||||
|
||||
config MCYRIXIII
|
||||
bool "CyrixIII/VIA-C3"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for a Cyrix III or C3 chip. Presently Linux and GCC
|
||||
treat this chip as a generic 586. Whilst the CPU is 686 class,
|
||||
it lacks the cmov extension which gcc assumes is present when
|
||||
|
|
@ -246,7 +246,7 @@ config MCYRIXIII
|
|||
config MVIAC3_2
|
||||
bool "VIA C3-2 (Nehemiah)"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for a VIA C3 "Nehemiah". Selecting this enables usage
|
||||
of SSE and tells gcc to treat the CPU as a 686.
|
||||
Note, this kernel will not boot on older (pre model 9) C3s.
|
||||
|
|
@ -254,14 +254,14 @@ config MVIAC3_2
|
|||
config MVIAC7
|
||||
bool "VIA C7"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Select this for a VIA C7. Selecting this uses the correct cache
|
||||
shift and tells gcc to treat the CPU as a 686.
|
||||
|
||||
config MPSC
|
||||
bool "Intel P4 / older Netburst based Xeon"
|
||||
depends on X86_64
|
||||
---help---
|
||||
help
|
||||
Optimize for Intel Pentium 4, Pentium D and older Nocona/Dempsey
|
||||
Xeon CPUs with Intel 64bit which is compatible with x86-64.
|
||||
Note that the latest Xeons (Xeon 51xx and 53xx) are not based on the
|
||||
|
|
@ -271,7 +271,7 @@ config MPSC
|
|||
|
||||
config MCORE2
|
||||
bool "Core 2/newer Xeon"
|
||||
---help---
|
||||
help
|
||||
|
||||
Select this for Intel Core 2 and newer Core 2 Xeons (Xeon 51xx and
|
||||
53xx) CPUs. You can distinguish newer from older Xeons by the CPU
|
||||
|
|
@ -280,7 +280,7 @@ config MCORE2
|
|||
|
||||
config MATOM
|
||||
bool "Intel Atom"
|
||||
---help---
|
||||
help
|
||||
|
||||
Select this for the Intel Atom platform. Intel Atom CPUs have an
|
||||
in-order pipelining architecture and thus can benefit from
|
||||
|
|
@ -290,7 +290,7 @@ config MATOM
|
|||
config GENERIC_CPU
|
||||
bool "Generic-x86-64"
|
||||
depends on X86_64
|
||||
---help---
|
||||
help
|
||||
Generic x86-64 CPU.
|
||||
Run equally well on all x86-64 CPUs.
|
||||
|
||||
|
|
@ -299,7 +299,7 @@ endchoice
|
|||
config X86_GENERIC
|
||||
bool "Generic x86 support"
|
||||
depends on X86_32
|
||||
---help---
|
||||
help
|
||||
Instead of just including optimizations for the selected
|
||||
x86 variant (e.g. PII, Crusoe or Athlon), include some more
|
||||
generic optimizations as well. This will make the kernel
|
||||
|
|
@ -397,14 +397,14 @@ config X86_VMX_FEATURE_NAMES
|
|||
|
||||
menuconfig PROCESSOR_SELECT
|
||||
bool "Supported processor vendors" if EXPERT
|
||||
---help---
|
||||
help
|
||||
This lets you choose what x86 vendor support code your kernel
|
||||
will include.
|
||||
|
||||
config CPU_SUP_INTEL
|
||||
default y
|
||||
bool "Support Intel processors" if PROCESSOR_SELECT
|
||||
---help---
|
||||
help
|
||||
This enables detection, tunings and quirks for Intel processors
|
||||
|
||||
You need this enabled if you want your kernel to run on an
|
||||
|
|
@ -418,7 +418,7 @@ config CPU_SUP_CYRIX_32
|
|||
default y
|
||||
bool "Support Cyrix processors" if PROCESSOR_SELECT
|
||||
depends on M486SX || M486 || M586 || M586TSC || M586MMX || (EXPERT && !64BIT)
|
||||
---help---
|
||||
help
|
||||
This enables detection, tunings and quirks for Cyrix processors
|
||||
|
||||
You need this enabled if you want your kernel to run on a
|
||||
|
|
@ -431,7 +431,7 @@ config CPU_SUP_CYRIX_32
|
|||
config CPU_SUP_AMD
|
||||
default y
|
||||
bool "Support AMD processors" if PROCESSOR_SELECT
|
||||
---help---
|
||||
help
|
||||
This enables detection, tunings and quirks for AMD processors
|
||||
|
||||
You need this enabled if you want your kernel to run on an
|
||||
|
|
@ -458,7 +458,7 @@ config CPU_SUP_HYGON
|
|||
config CPU_SUP_CENTAUR
|
||||
default y
|
||||
bool "Support Centaur processors" if PROCESSOR_SELECT
|
||||
---help---
|
||||
help
|
||||
This enables detection, tunings and quirks for Centaur processors
|
||||
|
||||
You need this enabled if you want your kernel to run on a
|
||||
|
|
@ -472,7 +472,7 @@ config CPU_SUP_TRANSMETA_32
|
|||
default y
|
||||
bool "Support Transmeta processors" if PROCESSOR_SELECT
|
||||
depends on !64BIT
|
||||
---help---
|
||||
help
|
||||
This enables detection, tunings and quirks for Transmeta processors
|
||||
|
||||
You need this enabled if you want your kernel to run on a
|
||||
|
|
@ -486,7 +486,7 @@ config CPU_SUP_UMC_32
|
|||
default y
|
||||
bool "Support UMC processors" if PROCESSOR_SELECT
|
||||
depends on M486SX || M486 || (EXPERT && !64BIT)
|
||||
---help---
|
||||
help
|
||||
This enables detection, tunings and quirks for UMC processors
|
||||
|
||||
You need this enabled if you want your kernel to run on a
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ config EARLY_PRINTK_USB
|
|||
config X86_VERBOSE_BOOTUP
|
||||
bool "Enable verbose x86 bootup info messages"
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Enables the informational output from the decompression stage
|
||||
(e.g. bzImage) of the boot. If you disable this you will still
|
||||
see errors. Disable this if you want silent bootup.
|
||||
|
|
@ -17,7 +17,7 @@ config X86_VERBOSE_BOOTUP
|
|||
config EARLY_PRINTK
|
||||
bool "Early printk" if EXPERT
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Write kernel log output directly into the VGA buffer or to a serial
|
||||
port.
|
||||
|
||||
|
|
@ -31,7 +31,7 @@ config EARLY_PRINTK_DBGP
|
|||
bool "Early printk via EHCI debug port"
|
||||
depends on EARLY_PRINTK && PCI
|
||||
select EARLY_PRINTK_USB
|
||||
---help---
|
||||
help
|
||||
Write kernel log output directly into the EHCI debug port.
|
||||
|
||||
This is useful for kernel debugging when your machine crashes very
|
||||
|
|
@ -44,7 +44,7 @@ config EARLY_PRINTK_USB_XDBC
|
|||
bool "Early printk via the xHCI debug port"
|
||||
depends on EARLY_PRINTK && PCI
|
||||
select EARLY_PRINTK_USB
|
||||
---help---
|
||||
help
|
||||
Write kernel log output directly into the xHCI debug port.
|
||||
|
||||
One use for this feature is kernel debugging, for example when your
|
||||
|
|
@ -66,7 +66,7 @@ config EFI_PGT_DUMP
|
|||
bool "Dump the EFI pagetable"
|
||||
depends on EFI
|
||||
select PTDUMP_CORE
|
||||
---help---
|
||||
help
|
||||
Enable this if you want to dump the EFI page table before
|
||||
enabling virtual mode. This can be used to debug miscellaneous
|
||||
issues with the mapping of the EFI runtime regions into that
|
||||
|
|
@ -75,7 +75,7 @@ config EFI_PGT_DUMP
|
|||
config DEBUG_TLBFLUSH
|
||||
bool "Set upper limit of TLB entries to flush one-by-one"
|
||||
depends on DEBUG_KERNEL
|
||||
---help---
|
||||
help
|
||||
|
||||
X86-only for now.
|
||||
|
||||
|
|
@ -95,7 +95,7 @@ config IOMMU_DEBUG
|
|||
bool "Enable IOMMU debugging"
|
||||
depends on GART_IOMMU && DEBUG_KERNEL
|
||||
depends on X86_64
|
||||
---help---
|
||||
help
|
||||
Force the IOMMU to on even when you have less than 4GB of
|
||||
memory and add debugging code. On overflow always panic. And
|
||||
allow to enable IOMMU leak tracing. Can be disabled at boot
|
||||
|
|
@ -110,7 +110,7 @@ config IOMMU_DEBUG
|
|||
config IOMMU_LEAK
|
||||
bool "IOMMU leak tracing"
|
||||
depends on IOMMU_DEBUG && DMA_API_DEBUG
|
||||
---help---
|
||||
help
|
||||
Add a simple leak tracer to the IOMMU code. This is useful when you
|
||||
are debugging a buggy device driver that leaks IOMMU mappings.
|
||||
|
||||
|
|
@ -121,7 +121,7 @@ config X86_DECODER_SELFTEST
|
|||
bool "x86 instruction decoder selftest"
|
||||
depends on DEBUG_KERNEL && INSTRUCTION_DECODER
|
||||
depends on !COMPILE_TEST
|
||||
---help---
|
||||
help
|
||||
Perform x86 instruction decoder selftests at build time.
|
||||
This option is useful for checking the sanity of x86 instruction
|
||||
decoder code.
|
||||
|
|
@ -133,25 +133,25 @@ choice
|
|||
|
||||
config IO_DELAY_0X80
|
||||
bool "port 0x80 based port-IO delay [recommended]"
|
||||
---help---
|
||||
help
|
||||
This is the traditional Linux IO delay used for in/out_p.
|
||||
It is the most tested hence safest selection here.
|
||||
|
||||
config IO_DELAY_0XED
|
||||
bool "port 0xed based port-IO delay"
|
||||
---help---
|
||||
help
|
||||
Use port 0xed as the IO delay. This frees up port 0x80 which is
|
||||
often used as a hardware-debug port.
|
||||
|
||||
config IO_DELAY_UDELAY
|
||||
bool "udelay based port-IO delay"
|
||||
---help---
|
||||
help
|
||||
Use udelay(2) as the IO delay method. This provides the delay
|
||||
while not having any side-effect on the IO port space.
|
||||
|
||||
config IO_DELAY_NONE
|
||||
bool "no port-IO delay"
|
||||
---help---
|
||||
help
|
||||
No port-IO delay. Will break on old boxes that require port-IO
|
||||
delay for certain operations. Should work on most new machines.
|
||||
|
||||
|
|
@ -161,19 +161,19 @@ config DEBUG_BOOT_PARAMS
|
|||
bool "Debug boot parameters"
|
||||
depends on DEBUG_KERNEL
|
||||
depends on DEBUG_FS
|
||||
---help---
|
||||
help
|
||||
This option will cause struct boot_params to be exported via debugfs.
|
||||
|
||||
config CPA_DEBUG
|
||||
bool "CPA self-test code"
|
||||
depends on DEBUG_KERNEL
|
||||
---help---
|
||||
help
|
||||
Do change_page_attr() self-tests every 30 seconds.
|
||||
|
||||
config DEBUG_ENTRY
|
||||
bool "Debug low-level entry code"
|
||||
depends on DEBUG_KERNEL
|
||||
---help---
|
||||
help
|
||||
This option enables sanity checks in x86's low-level entry code.
|
||||
Some of these sanity checks may slow down kernel entries and
|
||||
exits or otherwise impact performance.
|
||||
|
|
@ -183,7 +183,7 @@ config DEBUG_ENTRY
|
|||
config DEBUG_NMI_SELFTEST
|
||||
bool "NMI Selftest"
|
||||
depends on DEBUG_KERNEL && X86_LOCAL_APIC
|
||||
---help---
|
||||
help
|
||||
Enabling this option turns on a quick NMI selftest to verify
|
||||
that the NMI behaves correctly.
|
||||
|
||||
|
|
@ -195,7 +195,7 @@ config DEBUG_NMI_SELFTEST
|
|||
config DEBUG_IMR_SELFTEST
|
||||
bool "Isolated Memory Region self test"
|
||||
depends on INTEL_IMR
|
||||
---help---
|
||||
help
|
||||
This option enables automated sanity testing of the IMR code.
|
||||
Some simple tests are run to verify IMR bounds checking, alignment
|
||||
and overlapping. This option is really only useful if you are
|
||||
|
|
@ -208,7 +208,7 @@ config X86_DEBUG_FPU
|
|||
bool "Debug the x86 FPU code"
|
||||
depends on DEBUG_KERNEL
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
If this option is enabled then there will be extra sanity
|
||||
checks and (boot time) debug printouts added to the kernel.
|
||||
This debugging adds some small amount of runtime overhead
|
||||
|
|
@ -221,7 +221,7 @@ config PUNIT_ATOM_DEBUG
|
|||
depends on PCI
|
||||
select DEBUG_FS
|
||||
select IOSF_MBI
|
||||
---help---
|
||||
help
|
||||
This is a debug driver, which gets the power states
|
||||
of all Punit North Complex devices. The power states of
|
||||
each device is exposed as part of the debugfs interface.
|
||||
|
|
@ -232,7 +232,7 @@ choice
|
|||
prompt "Choose kernel unwinder"
|
||||
default UNWINDER_ORC if X86_64
|
||||
default UNWINDER_FRAME_POINTER if X86_32
|
||||
---help---
|
||||
help
|
||||
This determines which method will be used for unwinding kernel stack
|
||||
traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
|
||||
livepatch, lockdep, and more.
|
||||
|
|
@ -241,7 +241,7 @@ config UNWINDER_ORC
|
|||
bool "ORC unwinder"
|
||||
depends on X86_64
|
||||
select STACK_VALIDATION
|
||||
---help---
|
||||
help
|
||||
This option enables the ORC (Oops Rewind Capability) unwinder for
|
||||
unwinding kernel stack traces. It uses a custom data format which is
|
||||
a simplified version of the DWARF Call Frame Information standard.
|
||||
|
|
@ -256,7 +256,7 @@ config UNWINDER_ORC
|
|||
config UNWINDER_FRAME_POINTER
|
||||
bool "Frame pointer unwinder"
|
||||
select FRAME_POINTER
|
||||
---help---
|
||||
help
|
||||
This option enables the frame pointer unwinder for unwinding kernel
|
||||
stack traces.
|
||||
|
||||
|
|
@ -268,7 +268,7 @@ config UNWINDER_GUESS
|
|||
bool "Guess unwinder"
|
||||
depends on EXPERT
|
||||
depends on !STACKDEPOT
|
||||
---help---
|
||||
help
|
||||
This option enables the "guess" unwinder for unwinding kernel stack
|
||||
traces. It scans the stack and reports every kernel text address it
|
||||
finds. Some of the addresses it reports may be incorrect.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ config PERF_EVENTS_INTEL_UNCORE
|
|||
tristate "Intel uncore performance events"
|
||||
depends on PERF_EVENTS && CPU_SUP_INTEL && PCI
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Include support for Intel uncore performance events. These are
|
||||
available on NehalemEX and more modern processors.
|
||||
|
||||
|
|
@ -13,7 +13,7 @@ config PERF_EVENTS_INTEL_RAPL
|
|||
tristate "Intel/AMD rapl performance events"
|
||||
depends on PERF_EVENTS && (CPU_SUP_INTEL || CPU_SUP_AMD) && PCI
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Include support for Intel and AMD rapl performance events for power
|
||||
monitoring on modern processors.
|
||||
|
||||
|
|
@ -21,14 +21,14 @@ config PERF_EVENTS_INTEL_CSTATE
|
|||
tristate "Intel cstate performance events"
|
||||
depends on PERF_EVENTS && CPU_SUP_INTEL && PCI
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Include support for Intel cstate performance events for power
|
||||
monitoring on modern processors.
|
||||
|
||||
config PERF_EVENTS_AMD_POWER
|
||||
depends on PERF_EVENTS && CPU_SUP_AMD
|
||||
tristate "AMD Processor Power Reporting Mechanism"
|
||||
---help---
|
||||
help
|
||||
Provide power reporting mechanism support for AMD processors.
|
||||
Currently, it leverages X86_FEATURE_ACC_POWER
|
||||
(CPUID Fn8000_0007_EDX[12]) interface to calculate the
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ menuconfig VIRTUALIZATION
|
|||
bool "Virtualization"
|
||||
depends on HAVE_KVM || X86
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Say Y here to get to see options for using your Linux host to run other
|
||||
operating systems inside virtual machines (guests).
|
||||
This option alone does not add any kernel code.
|
||||
|
|
@ -45,7 +45,7 @@ config KVM
|
|||
select KVM_GENERIC_DIRTYLOG_READ_PROTECT
|
||||
select KVM_VFIO
|
||||
select SRCU
|
||||
---help---
|
||||
help
|
||||
Support hosting fully virtualized guest machines using hardware
|
||||
virtualization extensions. You will need a fairly recent
|
||||
processor equipped with virtualization extensions. You will also
|
||||
|
|
@ -75,7 +75,7 @@ config KVM_WERROR
|
|||
config KVM_INTEL
|
||||
tristate "KVM for Intel (and compatible) processors support"
|
||||
depends on KVM && IA32_FEAT_CTL
|
||||
---help---
|
||||
help
|
||||
Provides support for KVM on processors equipped with Intel's VT
|
||||
extensions, a.k.a. Virtual Machine Extensions (VMX).
|
||||
|
||||
|
|
@ -85,7 +85,7 @@ config KVM_INTEL
|
|||
config KVM_AMD
|
||||
tristate "KVM for AMD processors support"
|
||||
depends on KVM
|
||||
---help---
|
||||
help
|
||||
Provides support for KVM on AMD processors equipped with the AMD-V
|
||||
(SVM) extensions.
|
||||
|
||||
|
|
@ -97,13 +97,13 @@ config KVM_AMD_SEV
|
|||
bool "AMD Secure Encrypted Virtualization (SEV) support"
|
||||
depends on KVM_AMD && X86_64
|
||||
depends on CRYPTO_DEV_SP_PSP && !(KVM_AMD=y && CRYPTO_DEV_CCP_DD=m)
|
||||
---help---
|
||||
help
|
||||
Provides support for launching Encrypted VMs on AMD processors.
|
||||
|
||||
config KVM_MMU_AUDIT
|
||||
bool "Audit KVM MMU"
|
||||
depends on KVM && TRACEPOINTS
|
||||
---help---
|
||||
help
|
||||
This option adds a R/W kVM module parameter 'mmu_audit', which allows
|
||||
auditing of KVM MMU events at runtime.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
config RAS_CEC
|
||||
bool "Correctable Errors Collector"
|
||||
depends on X86_MCE && MEMORY_FAILURE && DEBUG_FS
|
||||
---help---
|
||||
help
|
||||
This is a small cache which collects correctable memory errors per 4K
|
||||
page PFN and counts their repeated occurrence. Once the counter for a
|
||||
PFN overflows, we try to soft-offline that page as we take it to mean
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ config BLK_DEV_BSGLIB
|
|||
|
||||
config BLK_DEV_INTEGRITY
|
||||
bool "Block layer data integrity support"
|
||||
---help---
|
||||
help
|
||||
Some storage devices allow extra information to be
|
||||
stored/retrieved to help protect the data. The block layer
|
||||
data integrity option provides hooks which can be used by
|
||||
|
|
@ -84,7 +84,7 @@ config BLK_DEV_INTEGRITY_T10
|
|||
config BLK_DEV_ZONED
|
||||
bool "Zoned block device support"
|
||||
select MQ_IOSCHED_DEADLINE
|
||||
---help---
|
||||
help
|
||||
Block layer zoned block device support. This option enables
|
||||
support for ZAC/ZBC host-managed and host-aware zoned block devices.
|
||||
|
||||
|
|
@ -94,7 +94,7 @@ config BLK_DEV_THROTTLING
|
|||
bool "Block layer bio throttling support"
|
||||
depends on BLK_CGROUP=y
|
||||
select BLK_CGROUP_RWSTAT
|
||||
---help---
|
||||
help
|
||||
Block layer bio throttling support. It can be used to limit
|
||||
the IO rate to a device. IO rate policies are per cgroup and
|
||||
one needs to mount and use blkio cgroup controller for creating
|
||||
|
|
@ -105,7 +105,7 @@ config BLK_DEV_THROTTLING
|
|||
config BLK_DEV_THROTTLING_LOW
|
||||
bool "Block throttling .low limit interface support (EXPERIMENTAL)"
|
||||
depends on BLK_DEV_THROTTLING
|
||||
---help---
|
||||
help
|
||||
Add .low limit interface for block throttling. The low limit is a best
|
||||
effort limit to prioritize cgroups. Depending on the setting, the limit
|
||||
can be used to protect cgroups in terms of bandwidth/iops and better
|
||||
|
|
@ -115,7 +115,7 @@ config BLK_DEV_THROTTLING_LOW
|
|||
|
||||
config BLK_CMDLINE_PARSER
|
||||
bool "Block device command line partition parser"
|
||||
---help---
|
||||
help
|
||||
Enabling this option allows you to specify the partition layout from
|
||||
the kernel boot args. This is typically of use for embedded devices
|
||||
which don't otherwise have any standardized method for listing the
|
||||
|
|
@ -125,7 +125,7 @@ config BLK_CMDLINE_PARSER
|
|||
|
||||
config BLK_WBT
|
||||
bool "Enable support for block device writeback throttling"
|
||||
---help---
|
||||
help
|
||||
Enabling this option enables the block layer to throttle buffered
|
||||
background writeback from the VM, making it more smooth and having
|
||||
less impact on foreground operations. The throttling is done
|
||||
|
|
@ -135,7 +135,7 @@ config BLK_WBT
|
|||
config BLK_CGROUP_IOLATENCY
|
||||
bool "Enable support for latency based cgroup IO protection"
|
||||
depends on BLK_CGROUP=y
|
||||
---help---
|
||||
help
|
||||
Enabling this option enables the .latency interface for IO throttling.
|
||||
The IO controller will attempt to maintain average IO latencies below
|
||||
the configured latency target, throttling anybody with a higher latency
|
||||
|
|
@ -148,7 +148,7 @@ config BLK_CGROUP_IOCOST
|
|||
depends on BLK_CGROUP=y
|
||||
select BLK_RQ_IO_DATA_LEN
|
||||
select BLK_RQ_ALLOC_TIME
|
||||
---help---
|
||||
help
|
||||
Enabling this option enables the .weight interface for cost
|
||||
model based proportional IO control. The IO controller
|
||||
distributes IO capacity between different groups based on
|
||||
|
|
@ -158,7 +158,7 @@ config BLK_WBT_MQ
|
|||
bool "Multiqueue writeback throttling"
|
||||
default y
|
||||
depends on BLK_WBT
|
||||
---help---
|
||||
help
|
||||
Enable writeback throttling by default on multiqueue devices.
|
||||
Multiqueue currently doesn't have support for IO scheduling,
|
||||
enabling this option is recommended.
|
||||
|
|
@ -167,7 +167,7 @@ config BLK_DEBUG_FS
|
|||
bool "Block layer debugging information in debugfs"
|
||||
default y
|
||||
depends on DEBUG_FS
|
||||
---help---
|
||||
help
|
||||
Include block layer debugging information in debugfs. This information
|
||||
is mostly useful for kernel developers, but it doesn't incur any cost
|
||||
at runtime.
|
||||
|
|
@ -181,7 +181,7 @@ config BLK_DEBUG_FS_ZONED
|
|||
|
||||
config BLK_SED_OPAL
|
||||
bool "Logic for interfacing with Opal enabled SEDs"
|
||||
---help---
|
||||
help
|
||||
Builds Logic for interfacing with Opal enabled controllers.
|
||||
Enabling this option enables users to setup/unlock/lock
|
||||
Locking ranges for SED devices using the Opal protocol.
|
||||
|
|
|
|||
|
|
@ -6,13 +6,13 @@ menu "IO Schedulers"
|
|||
config MQ_IOSCHED_DEADLINE
|
||||
tristate "MQ deadline I/O scheduler"
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
MQ version of the deadline IO scheduler.
|
||||
|
||||
config MQ_IOSCHED_KYBER
|
||||
tristate "Kyber I/O scheduler"
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
The Kyber I/O scheduler is a low-overhead scheduler suitable for
|
||||
multiqueue and other fast devices. Given target latencies for reads and
|
||||
synchronous writes, it will self-tune queue depths to achieve that
|
||||
|
|
@ -20,7 +20,7 @@ config MQ_IOSCHED_KYBER
|
|||
|
||||
config IOSCHED_BFQ
|
||||
tristate "BFQ I/O scheduler"
|
||||
---help---
|
||||
help
|
||||
BFQ I/O scheduler for BLK-MQ. BFQ distributes the bandwidth of
|
||||
of the device among all processes according to their weights,
|
||||
regardless of the device parameters and with any workload. It
|
||||
|
|
@ -32,7 +32,7 @@ config BFQ_GROUP_IOSCHED
|
|||
bool "BFQ hierarchical scheduling support"
|
||||
depends on IOSCHED_BFQ && BLK_CGROUP
|
||||
select BLK_CGROUP_RWSTAT
|
||||
---help---
|
||||
help
|
||||
|
||||
Enable hierarchical scheduling in BFQ, using the blkio
|
||||
(cgroups-v1) or io (cgroups-v2) controller.
|
||||
|
|
@ -40,7 +40,7 @@ config BFQ_GROUP_IOSCHED
|
|||
config BFQ_CGROUP_DEBUG
|
||||
bool "BFQ IO controller debugging"
|
||||
depends on BFQ_GROUP_IOSCHED
|
||||
---help---
|
||||
help
|
||||
Enable some debugging help. Currently it exports additional stat
|
||||
files in a cgroup which can be useful for debugging.
|
||||
|
||||
|
|
|
|||
|
|
@ -156,7 +156,7 @@ config SOLARIS_X86_PARTITION
|
|||
config UNIXWARE_DISKLABEL
|
||||
bool "Unixware slices support"
|
||||
depends on PARTITION_ADVANCED && MSDOS_PARTITION
|
||||
---help---
|
||||
help
|
||||
Like some systems, UnixWare uses its own slice table inside a
|
||||
partition (VTOC - Virtual Table of Contents). Its format is
|
||||
incompatible with all other OSes. Saying Y here allows you to read
|
||||
|
|
@ -176,7 +176,7 @@ config UNIXWARE_DISKLABEL
|
|||
config LDM_PARTITION
|
||||
bool "Windows Logical Disk Manager (Dynamic Disk) support"
|
||||
depends on PARTITION_ADVANCED
|
||||
---help---
|
||||
help
|
||||
Say Y here if you would like to use hard disks under Linux which
|
||||
were partitioned using Windows 2000's/XP's or Vista's Logical Disk
|
||||
Manager. They are also known as "Dynamic Disks".
|
||||
|
|
@ -226,7 +226,7 @@ config ULTRIX_PARTITION
|
|||
config SUN_PARTITION
|
||||
bool "Sun partition tables support" if PARTITION_ADVANCED
|
||||
default y if (SPARC || SUN3 || SUN3X)
|
||||
---help---
|
||||
help
|
||||
Like most systems, SunOS uses its own hard disk partition table
|
||||
format, incompatible with all others. Saying Y here allows you to
|
||||
read these partition tables and further mount SunOS partitions from
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# SPDX-License-Identifier: GPL-2.0
|
||||
menuconfig ACCESSIBILITY
|
||||
bool "Accessibility support"
|
||||
---help---
|
||||
help
|
||||
Accessibility handles all special kinds of hardware devices or
|
||||
software adapters which help people with disabilities (e.g.
|
||||
blindness) to use computers.
|
||||
|
|
@ -21,7 +21,7 @@ config A11Y_BRAILLE_CONSOLE
|
|||
bool "Console on braille device"
|
||||
depends on VT
|
||||
depends on SERIAL_CORE_CONSOLE
|
||||
---help---
|
||||
help
|
||||
Enables console output on a braille device connected to a 8250
|
||||
serial port. For now only the VisioBraille device is supported.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ menu "Android"
|
|||
|
||||
config ANDROID
|
||||
bool "Android Drivers"
|
||||
---help---
|
||||
help
|
||||
Enable support for various drivers needed on the Android platform
|
||||
|
||||
if ANDROID
|
||||
|
|
@ -12,7 +12,7 @@ config ANDROID_BINDER_IPC
|
|||
bool "Android Binder IPC Driver"
|
||||
depends on MMU
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
Binder is used in Android for both communication between processes,
|
||||
and remote method invocation.
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ config ANDROID_BINDERFS
|
|||
bool "Android Binderfs filesystem"
|
||||
depends on ANDROID_BINDER_IPC
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
Binderfs is a pseudo-filesystem for the Android Binder IPC driver
|
||||
which can be mounted per-ipc namespace allowing to run multiple
|
||||
instances of Android.
|
||||
|
|
@ -36,7 +36,7 @@ config ANDROID_BINDER_DEVICES
|
|||
string "Android Binder devices"
|
||||
depends on ANDROID_BINDER_IPC
|
||||
default "binder,hwbinder,vndbinder"
|
||||
---help---
|
||||
help
|
||||
Default value for the binder.devices parameter.
|
||||
|
||||
The binder.devices parameter is a comma-separated list of strings
|
||||
|
|
@ -47,7 +47,7 @@ config ANDROID_BINDER_DEVICES
|
|||
config ANDROID_BINDER_IPC_SELFTEST
|
||||
bool "Android Binder IPC Driver Selftest"
|
||||
depends on ANDROID_BINDER_IPC
|
||||
---help---
|
||||
help
|
||||
This feature allows binder selftest to run.
|
||||
|
||||
Binder selftest checks the allocation and free of binder buffers
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ menuconfig ATA
|
|||
depends on BLOCK
|
||||
select SCSI
|
||||
select GLOB
|
||||
---help---
|
||||
help
|
||||
If you want to use an ATA hard disk, ATA tape drive, ATA CD-ROM or
|
||||
any other ATA device under Linux, say Y and make sure that you know
|
||||
the name of your ATA host adapter (the card inside your computer
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ menuconfig ATM_DRIVERS
|
|||
bool "ATM drivers"
|
||||
depends on NETDEVICES && ATM
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Say Y here to get to see options for Asynchronous Transfer Mode
|
||||
device drivers. This option alone does not add any kernel code.
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ config ATM_LANAI
|
|||
config ATM_ENI
|
||||
tristate "Efficient Networks ENI155P"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
Driver for the Efficient Networks ENI155p series and SMC ATM
|
||||
Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
|
||||
2MB on-board RAM (Efficient calls them "C" and "S", respectively),
|
||||
|
|
@ -64,7 +64,7 @@ config ATM_ENI_DEBUG
|
|||
config ATM_ENI_TUNE_BURST
|
||||
bool "Fine-tune burst settings"
|
||||
depends on ATM_ENI
|
||||
---help---
|
||||
help
|
||||
In order to obtain good throughput, the ENI NIC can transfer
|
||||
multiple words of data per PCI bus access cycle. Such a multi-word
|
||||
transfer is called a burst.
|
||||
|
|
@ -256,7 +256,7 @@ config ATM_AMBASSADOR
|
|||
config ATM_AMBASSADOR_DEBUG
|
||||
bool "Enable debugging messages"
|
||||
depends on ATM_AMBASSADOR
|
||||
---help---
|
||||
help
|
||||
Somewhat useful debugging messages are available. The choice of
|
||||
messages is controlled by a bitmap. This may be specified as a
|
||||
module argument (kernel command line argument as well?), changed
|
||||
|
|
@ -280,7 +280,7 @@ config ATM_HORIZON
|
|||
config ATM_HORIZON_DEBUG
|
||||
bool "Enable debugging messages"
|
||||
depends on ATM_HORIZON
|
||||
---help---
|
||||
help
|
||||
Somewhat useful debugging messages are available. The choice of
|
||||
messages is controlled by a bitmap. This may be specified as a
|
||||
module argument (kernel command line argument as well?), changed
|
||||
|
|
@ -296,7 +296,7 @@ config ATM_HORIZON_DEBUG
|
|||
config ATM_IA
|
||||
tristate "Interphase ATM PCI x575/x525/x531"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This is a driver for the Interphase (i)ChipSAR adapter cards
|
||||
which include a variety of variants in term of the size of the
|
||||
control memory (128K-1KVC, 512K-4KVC), the size of the packet
|
||||
|
|
@ -312,7 +312,7 @@ config ATM_IA
|
|||
config ATM_IA_DEBUG
|
||||
bool "Enable debugging messages"
|
||||
depends on ATM_IA
|
||||
---help---
|
||||
help
|
||||
Somewhat useful debugging messages are available. The choice of
|
||||
messages is controlled by a bitmap. This may be specified as a
|
||||
module argument (kernel command line argument as well?), changed
|
||||
|
|
@ -330,7 +330,7 @@ config ATM_FORE200E
|
|||
tristate "FORE Systems 200E-series"
|
||||
depends on (PCI || SBUS)
|
||||
select FW_LOADER
|
||||
---help---
|
||||
help
|
||||
This is a driver for the FORE Systems 200E-series ATM adapter
|
||||
cards. It simultaneously supports PCA-200E and SBA-200E models
|
||||
on PCI and SBUS hosts. Say Y (or M to compile as a module
|
||||
|
|
@ -352,7 +352,7 @@ config ATM_FORE200E_TX_RETRY
|
|||
int "Maximum number of tx retries"
|
||||
depends on ATM_FORE200E
|
||||
default "16"
|
||||
---help---
|
||||
help
|
||||
Specifies the number of times the driver attempts to transmit
|
||||
a message before giving up, if the transmit queue of the ATM card
|
||||
is transiently saturated.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
|
||||
menuconfig AUXDISPLAY
|
||||
bool "Auxiliary Display support"
|
||||
---help---
|
||||
help
|
||||
Say Y here to get to see options for auxiliary display drivers.
|
||||
This option alone does not add any kernel code.
|
||||
|
||||
|
|
@ -20,7 +20,7 @@ config HD44780
|
|||
tristate "HD44780 Character LCD support"
|
||||
depends on GPIOLIB || COMPILE_TEST
|
||||
select CHARLCD
|
||||
---help---
|
||||
help
|
||||
Enable support for Character LCDs using a HD44780 controller.
|
||||
The LCD is accessible through the /dev/lcd char device (10, 156).
|
||||
This code can either be compiled as a module, or linked into the
|
||||
|
|
@ -31,7 +31,7 @@ config KS0108
|
|||
tristate "KS0108 LCD Controller"
|
||||
depends on PARPORT_PC
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
If you have a LCD controlled by one or more KS0108
|
||||
controllers, say Y. You will need also another more specific
|
||||
driver for your LCD.
|
||||
|
|
@ -49,7 +49,7 @@ config KS0108_PORT
|
|||
hex "Parallel port where the LCD is connected"
|
||||
depends on KS0108
|
||||
default 0x378
|
||||
---help---
|
||||
help
|
||||
The address of the parallel port where the LCD is connected.
|
||||
|
||||
The first standard parallel port address is 0x378.
|
||||
|
|
@ -71,7 +71,7 @@ config KS0108_DELAY
|
|||
int "Delay between each control writing (microseconds)"
|
||||
depends on KS0108
|
||||
default "2"
|
||||
---help---
|
||||
help
|
||||
Amount of time the ks0108 should wait between each control write
|
||||
to the parallel port.
|
||||
|
||||
|
|
@ -92,7 +92,7 @@ config CFAG12864B
|
|||
select FB_SYS_IMAGEBLIT
|
||||
select FB_SYS_FOPS
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
If you have a Crystalfontz 128x64 2-color LCD, cfag12864b Series,
|
||||
say Y. You also need the ks0108 LCD Controller driver.
|
||||
|
||||
|
|
@ -114,7 +114,7 @@ config CFAG12864B_RATE
|
|||
int "Refresh rate (hertz)"
|
||||
depends on CFAG12864B
|
||||
default "20"
|
||||
---help---
|
||||
help
|
||||
Refresh rate of the LCD.
|
||||
|
||||
As the LCD is not memory mapped, the driver has to make the work by
|
||||
|
|
@ -168,7 +168,7 @@ menuconfig PARPORT_PANEL
|
|||
tristate "Parallel port LCD/Keypad Panel support"
|
||||
depends on PARPORT
|
||||
select CHARLCD
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have an HD44780 or KS-0074 LCD connected to your
|
||||
parallel port. This driver also features 4 and 6-key keypads. The LCD
|
||||
is accessible through the /dev/lcd char device (10, 156), and the
|
||||
|
|
@ -182,7 +182,7 @@ config PANEL_PARPORT
|
|||
int "Default parallel port number (0=LPT1)"
|
||||
range 0 255
|
||||
default "0"
|
||||
---help---
|
||||
help
|
||||
This is the index of the parallel port the panel is connected to. One
|
||||
driver instance only supports one parallel port, so if your keypad
|
||||
and LCD are connected to two separate ports, you have to start two
|
||||
|
|
@ -193,7 +193,7 @@ config PANEL_PROFILE
|
|||
int "Default panel profile (0-5, 0=custom)"
|
||||
range 0 5
|
||||
default "5"
|
||||
---help---
|
||||
help
|
||||
To ease configuration, the driver supports different configuration
|
||||
profiles for past and recent wirings. These profiles can also be
|
||||
used to define an approximative configuration, completed by a few
|
||||
|
|
@ -215,7 +215,7 @@ config PANEL_KEYPAD
|
|||
int "Keypad type (0=none, 1=old 6 keys, 2=new 6 keys, 3=Nexcom 4 keys)"
|
||||
range 0 3
|
||||
default 0
|
||||
---help---
|
||||
help
|
||||
This enables and configures a keypad connected to the parallel port.
|
||||
The keys will be read from character device 10,185. Valid values are :
|
||||
|
||||
|
|
@ -232,7 +232,7 @@ config PANEL_LCD
|
|||
int "LCD type (0=none, 1=custom, 2=old //, 3=ks0074, 4=hantronix, 5=Nexcom)"
|
||||
range 0 5
|
||||
default 0
|
||||
---help---
|
||||
help
|
||||
This enables and configures an LCD connected to the parallel port.
|
||||
The driver includes an interpreter for escape codes starting with
|
||||
'\e[L' which are specific to the LCD, and a few ANSI codes. The
|
||||
|
|
@ -255,7 +255,7 @@ config PANEL_LCD_HEIGHT
|
|||
int "Number of lines on the LCD (1-2)"
|
||||
range 1 2
|
||||
default 2
|
||||
---help---
|
||||
help
|
||||
This is the number of visible character lines on the LCD in custom profile.
|
||||
It can either be 1 or 2.
|
||||
|
||||
|
|
@ -264,7 +264,7 @@ config PANEL_LCD_WIDTH
|
|||
int "Number of characters per line on the LCD (1-40)"
|
||||
range 1 40
|
||||
default 40
|
||||
---help---
|
||||
help
|
||||
This is the number of characters per line on the LCD in custom profile.
|
||||
Common values are 16,20,24,40.
|
||||
|
||||
|
|
@ -273,7 +273,7 @@ config PANEL_LCD_BWIDTH
|
|||
int "Internal LCD line width (1-40, 40 by default)"
|
||||
range 1 40
|
||||
default 40
|
||||
---help---
|
||||
help
|
||||
Most LCDs use a standard controller which supports hardware lines of 40
|
||||
characters, although sometimes only 16, 20 or 24 of them are really wired
|
||||
to the terminal. This results in some non-visible but addressable characters,
|
||||
|
|
@ -289,7 +289,7 @@ config PANEL_LCD_HWIDTH
|
|||
int "Hardware LCD line width (1-64, 64 by default)"
|
||||
range 1 64
|
||||
default 64
|
||||
---help---
|
||||
help
|
||||
Most LCDs use a single address bit to differentiate line 0 and line 1. Since
|
||||
some of them need to be able to address 40 chars with the lower bits, they
|
||||
often use the immediately superior power of 2, which is 64, to address the
|
||||
|
|
@ -303,7 +303,7 @@ config PANEL_LCD_CHARSET
|
|||
int "LCD character set (0=normal, 1=KS0074)"
|
||||
range 0 1
|
||||
default 0
|
||||
---help---
|
||||
help
|
||||
Some controllers such as the KS0074 use a somewhat strange character set
|
||||
where many symbols are at unusual places. The driver knows how to map
|
||||
'standard' ASCII characters to the character sets used by these controllers.
|
||||
|
|
@ -319,7 +319,7 @@ config PANEL_LCD_PROTO
|
|||
int "LCD communication mode (0=parallel 8 bits, 1=serial)"
|
||||
range 0 1
|
||||
default 0
|
||||
---help---
|
||||
help
|
||||
This driver now supports any serial or parallel LCD wired to a parallel
|
||||
port. But before assigning signals, the driver needs to know if it will
|
||||
be driving a serial LCD or a parallel one. Serial LCDs only use 2 wires
|
||||
|
|
@ -332,7 +332,7 @@ config PANEL_LCD_PIN_E
|
|||
int "Parallel port pin number & polarity connected to the LCD E signal (-17...17) "
|
||||
range -17 17
|
||||
default 14
|
||||
---help---
|
||||
help
|
||||
This describes the number of the parallel port pin to which the LCD 'E'
|
||||
signal has been connected. It can be :
|
||||
|
||||
|
|
@ -347,7 +347,7 @@ config PANEL_LCD_PIN_RS
|
|||
int "Parallel port pin number & polarity connected to the LCD RS signal (-17...17) "
|
||||
range -17 17
|
||||
default 17
|
||||
---help---
|
||||
help
|
||||
This describes the number of the parallel port pin to which the LCD 'RS'
|
||||
signal has been connected. It can be :
|
||||
|
||||
|
|
@ -362,7 +362,7 @@ config PANEL_LCD_PIN_RW
|
|||
int "Parallel port pin number & polarity connected to the LCD RW signal (-17...17) "
|
||||
range -17 17
|
||||
default 16
|
||||
---help---
|
||||
help
|
||||
This describes the number of the parallel port pin to which the LCD 'RW'
|
||||
signal has been connected. It can be :
|
||||
|
||||
|
|
@ -377,7 +377,7 @@ config PANEL_LCD_PIN_SCL
|
|||
int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) "
|
||||
range -17 17
|
||||
default 1
|
||||
---help---
|
||||
help
|
||||
This describes the number of the parallel port pin to which the serial
|
||||
LCD 'SCL' signal has been connected. It can be :
|
||||
|
||||
|
|
@ -392,7 +392,7 @@ config PANEL_LCD_PIN_SDA
|
|||
int "Parallel port pin number & polarity connected to the LCD SDA signal (-17...17) "
|
||||
range -17 17
|
||||
default 2
|
||||
---help---
|
||||
help
|
||||
This describes the number of the parallel port pin to which the serial
|
||||
LCD 'SDA' signal has been connected. It can be :
|
||||
|
||||
|
|
@ -407,7 +407,7 @@ config PANEL_LCD_PIN_BL
|
|||
int "Parallel port pin number & polarity connected to the LCD backlight signal (-17...17) "
|
||||
range -17 17
|
||||
default 0
|
||||
---help---
|
||||
help
|
||||
This describes the number of the parallel port pin to which the LCD 'BL' signal
|
||||
has been connected. It can be :
|
||||
|
||||
|
|
@ -423,7 +423,7 @@ config PANEL_CHANGE_MESSAGE
|
|||
bool "Change LCD initialization message ?"
|
||||
depends on CHARLCD
|
||||
default "n"
|
||||
---help---
|
||||
help
|
||||
This allows you to replace the boot message indicating the kernel version
|
||||
and the driver version with a custom message. This is useful on appliances
|
||||
where a simple 'Starting system' message can be enough to stop a customer
|
||||
|
|
@ -436,7 +436,7 @@ config PANEL_BOOT_MESSAGE
|
|||
depends on PANEL_CHANGE_MESSAGE="y"
|
||||
string "New initialization message"
|
||||
default ""
|
||||
---help---
|
||||
help
|
||||
This allows you to replace the boot message indicating the kernel version
|
||||
and the driver version with a custom message. This is useful on appliances
|
||||
where a simple 'Starting system' message can be enough to stop a customer
|
||||
|
|
@ -448,7 +448,7 @@ config PANEL_BOOT_MESSAGE
|
|||
choice
|
||||
prompt "Backlight initial state"
|
||||
default CHARLCD_BL_FLASH
|
||||
---help---
|
||||
help
|
||||
Select the initial backlight state on boot or module load.
|
||||
|
||||
Previously, there was no option for this: the backlight flashed
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ menuconfig BLK_DEV
|
|||
bool "Block devices"
|
||||
depends on BLOCK
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Say Y here to get to see options for various different block device
|
||||
drivers. This option alone does not add any kernel code.
|
||||
|
||||
|
|
@ -27,7 +27,7 @@ config BLK_DEV_NULL_BLK_FAULT_INJECTION
|
|||
config BLK_DEV_FD
|
||||
tristate "Normal floppy disk support"
|
||||
depends on ARCH_MAY_HAVE_PC_FDC
|
||||
---help---
|
||||
help
|
||||
If you want to use the floppy disk drive(s) of your PC under Linux,
|
||||
say Y. Information about this driver, especially important for IBM
|
||||
Thinkpad users, is contained in
|
||||
|
|
@ -91,7 +91,7 @@ config GDROM
|
|||
config PARIDE
|
||||
tristate "Parallel port IDE device support"
|
||||
depends on PARPORT_PC
|
||||
---help---
|
||||
help
|
||||
There are many external CD-ROM and disk devices that connect through
|
||||
your computer's parallel port. Most of them are actually IDE devices
|
||||
using a parallel port IDE adapter. This option enables the PARIDE
|
||||
|
|
@ -124,7 +124,7 @@ source "drivers/block/zram/Kconfig"
|
|||
config BLK_DEV_UMEM
|
||||
tristate "Micro Memory MM5415 Battery Backed RAM support"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
Saying Y here will include support for the MM5415 family of
|
||||
battery backed (Non-volatile) RAM cards.
|
||||
<http://www.umem.com/>
|
||||
|
|
@ -141,7 +141,7 @@ config BLK_DEV_UMEM
|
|||
config BLK_DEV_UBD
|
||||
bool "Virtual block device"
|
||||
depends on UML
|
||||
---help---
|
||||
help
|
||||
The User-Mode Linux port includes a driver called UBD which will let
|
||||
you access arbitrary files on the host computer as block devices.
|
||||
Unless you know that you do not need such virtual block devices say
|
||||
|
|
@ -150,7 +150,7 @@ config BLK_DEV_UBD
|
|||
config BLK_DEV_UBD_SYNC
|
||||
bool "Always do synchronous disk IO for UBD"
|
||||
depends on BLK_DEV_UBD
|
||||
---help---
|
||||
help
|
||||
Writes to the virtual block device are not immediately written to the
|
||||
host's disk; this may cause problems if, for example, the User-Mode
|
||||
Linux 'Virtual Machine' uses a journalling filesystem and the host
|
||||
|
|
@ -173,7 +173,7 @@ config BLK_DEV_COW_COMMON
|
|||
|
||||
config BLK_DEV_LOOP
|
||||
tristate "Loopback device support"
|
||||
---help---
|
||||
help
|
||||
Saying Y here will allow you to use a regular file as a block
|
||||
device; you can then create a file system on that block device and
|
||||
mount it just as you would mount other block devices such as hard
|
||||
|
|
@ -234,7 +234,7 @@ config BLK_DEV_CRYPTOLOOP
|
|||
select CRYPTO
|
||||
select CRYPTO_CBC
|
||||
depends on BLK_DEV_LOOP
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to be able to use the ciphers that are
|
||||
provided by the CryptoAPI as loop transformation. This might be
|
||||
used as hard disk encryption.
|
||||
|
|
@ -249,7 +249,7 @@ source "drivers/block/drbd/Kconfig"
|
|||
config BLK_DEV_NBD
|
||||
tristate "Network block device support"
|
||||
depends on NET
|
||||
---help---
|
||||
help
|
||||
Saying Y here will allow your computer to be a client for network
|
||||
block devices, i.e. it will be able to use block devices exported by
|
||||
servers (mount file systems on them etc.). Communication between
|
||||
|
|
@ -277,7 +277,7 @@ config BLK_DEV_SKD
|
|||
tristate "STEC S1120 Block Driver"
|
||||
depends on PCI
|
||||
depends on 64BIT
|
||||
---help---
|
||||
help
|
||||
Saying Y or M here will enable support for the
|
||||
STEC, Inc. S1120 PCIe SSD.
|
||||
|
||||
|
|
@ -286,7 +286,7 @@ config BLK_DEV_SKD
|
|||
config BLK_DEV_SX8
|
||||
tristate "Promise SATA SX8 support"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
Saying Y or M here will enable support for the
|
||||
Promise SATA SX8 controllers.
|
||||
|
||||
|
|
@ -294,7 +294,7 @@ config BLK_DEV_SX8
|
|||
|
||||
config BLK_DEV_RAM
|
||||
tristate "RAM block device support"
|
||||
---help---
|
||||
help
|
||||
Saying Y here will allow you to use a portion of your RAM memory as
|
||||
a block device, so that you can make file systems on it, read and
|
||||
write to it and do all the other things that you can do with normal
|
||||
|
|
@ -428,7 +428,7 @@ config XEN_BLKDEV_BACKEND
|
|||
config VIRTIO_BLK
|
||||
tristate "Virtio block driver"
|
||||
depends on VIRTIO
|
||||
---help---
|
||||
help
|
||||
This is the virtual block driver for virtio. It can be used with
|
||||
QEMU based VMMs (like KVM or Xen). Say Y or M.
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ config PARIDE_PCD
|
|||
depends on PARIDE
|
||||
select CDROM
|
||||
select BLK_SCSI_REQUEST # only for the generic cdrom code
|
||||
---help---
|
||||
help
|
||||
This option enables the high-level driver for ATAPI CD-ROM devices
|
||||
connected through a parallel port. If you chose to build PARIDE
|
||||
support into your kernel, you may answer Y here to build in the
|
||||
|
|
@ -71,7 +71,7 @@ config PARIDE_PT
|
|||
config PARIDE_PG
|
||||
tristate "Parallel port generic ATAPI devices"
|
||||
depends on PARIDE
|
||||
---help---
|
||||
help
|
||||
This option enables a special high-level driver for generic ATAPI
|
||||
devices connected through a parallel port. The driver allows user
|
||||
programs, such as cdrtools, to send ATAPI commands directly to a
|
||||
|
|
@ -111,7 +111,7 @@ config PARIDE_ATEN
|
|||
config PARIDE_BPCK
|
||||
tristate "MicroSolutions backpack (Series 5) protocol"
|
||||
depends on PARIDE
|
||||
---help---
|
||||
help
|
||||
This option enables support for the Micro Solutions BACKPACK
|
||||
parallel port Series 5 IDE protocol. (Most BACKPACK drives made
|
||||
before 1999 were Series 5) Series 5 drives will NOT always have the
|
||||
|
|
@ -129,7 +129,7 @@ config PARIDE_BPCK
|
|||
config PARIDE_BPCK6
|
||||
tristate "MicroSolutions backpack (Series 6) protocol"
|
||||
depends on PARIDE && !64BIT
|
||||
---help---
|
||||
help
|
||||
This option enables support for the Micro Solutions BACKPACK
|
||||
parallel port Series 6 IDE protocol. (Most BACKPACK drives made
|
||||
after 1999 were Series 6) Series 6 drives will have the Series noted
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ config TTY_PRINTK
|
|||
tristate "TTY driver to output user messages via printk"
|
||||
depends on EXPERT && TTY
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
If you say Y here, the support for writing user messages (i.e.
|
||||
console messages) via printk is available.
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ config TTY_PRINTK_LEVEL
|
|||
config PRINTER
|
||||
tristate "Parallel printer support"
|
||||
depends on PARPORT
|
||||
---help---
|
||||
help
|
||||
If you intend to attach a printer to the parallel port of your Linux
|
||||
box (as opposed to using a serial printer; if the connector at the
|
||||
printer has 9 or 25 holes ["female"], then it's serial), say Y.
|
||||
|
|
@ -59,7 +59,7 @@ config PRINTER
|
|||
config LP_CONSOLE
|
||||
bool "Support for console on line printer"
|
||||
depends on PRINTER
|
||||
---help---
|
||||
help
|
||||
If you want kernel messages to be printed out as they occur, you
|
||||
can have a console on the printer. This option adds support for
|
||||
doing that; to actually get it to happen you need to pass the
|
||||
|
|
@ -76,7 +76,7 @@ config LP_CONSOLE
|
|||
config PPDEV
|
||||
tristate "Support for user-space parallel port device drivers"
|
||||
depends on PARPORT
|
||||
---help---
|
||||
help
|
||||
Saying Y to this adds support for /dev/parport device nodes. This
|
||||
is needed for programs that want portable access to the parallel
|
||||
port, for instance deviceid (which displays Plug-and-Play device
|
||||
|
|
@ -146,7 +146,7 @@ config DS1620
|
|||
config NWBUTTON
|
||||
tristate "NetWinder Button"
|
||||
depends on ARCH_NETWINDER
|
||||
---help---
|
||||
help
|
||||
If you say Y here and create a character device node /dev/nwbutton
|
||||
with major and minor numbers 10 and 158 ("man mknod"), then every
|
||||
time the orange button is pressed a number of times, the number of
|
||||
|
|
@ -182,7 +182,7 @@ config NWBUTTON_REBOOT
|
|||
config NWFLASH
|
||||
tristate "NetWinder flash support"
|
||||
depends on ARCH_NETWINDER
|
||||
---help---
|
||||
help
|
||||
If you say Y here and create a character device /dev/flash with
|
||||
major 10 and minor 160 you can manipulate the flash ROM containing
|
||||
the NetWinder firmware. Be careful as accidentally overwriting the
|
||||
|
|
@ -220,7 +220,7 @@ config XILINX_HWICAP
|
|||
config R3964
|
||||
tristate "Siemens R3964 line discipline"
|
||||
depends on TTY && BROKEN
|
||||
---help---
|
||||
help
|
||||
This driver allows synchronous communication with devices using the
|
||||
Siemens R3964 packet protocol. Unless you are dealing with special
|
||||
hardware like PLCs, you are unlikely to need this.
|
||||
|
|
@ -233,7 +233,7 @@ config R3964
|
|||
config APPLICOM
|
||||
tristate "Applicom intelligent fieldbus card support"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This driver provides the kernel-side support for the intelligent
|
||||
fieldbus cards made by Applicom International. More information
|
||||
about these cards can be found on the WWW at the address
|
||||
|
|
@ -248,7 +248,7 @@ config APPLICOM
|
|||
config SONYPI
|
||||
tristate "Sony Vaio Programmable I/O Control Device support"
|
||||
depends on X86_32 && PCI && INPUT
|
||||
---help---
|
||||
help
|
||||
This driver enables access to the Sony Programmable I/O Control
|
||||
Device which can be found in many (all ?) Sony Vaio laptops.
|
||||
|
||||
|
|
@ -269,7 +269,7 @@ config MWAVE
|
|||
tristate "ACP Modem (Mwave) support"
|
||||
depends on X86 && TTY
|
||||
select SERIAL_8250
|
||||
---help---
|
||||
help
|
||||
The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
|
||||
kernel driver and a user level application. Together these components
|
||||
support direct attachment to public switched telephone networks (PSTNs)
|
||||
|
|
@ -347,7 +347,7 @@ config NVRAM
|
|||
tristate "/dev/nvram support"
|
||||
depends on X86 || HAVE_ARCH_NVRAM_OPS
|
||||
default M68K || PPC
|
||||
---help---
|
||||
help
|
||||
If you say Y here and create a character special file /dev/nvram
|
||||
with major number 10 and minor number 144 using mknod ("man mknod"),
|
||||
you get read and write access to the non-volatile memory.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ menuconfig AGP
|
|||
tristate "/dev/agpgart (AGP Support)"
|
||||
depends on ALPHA || IA64 || PARISC || PPC || X86
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
AGP (Accelerated Graphics Port) is a bus system mainly used to
|
||||
connect graphics cards to the rest of the system.
|
||||
|
||||
|
|
@ -30,7 +30,7 @@ menuconfig AGP
|
|||
config AGP_ALI
|
||||
tristate "ALI chipset support"
|
||||
depends on AGP && X86_32
|
||||
---help---
|
||||
help
|
||||
This option gives you AGP support for the GLX component of
|
||||
X on the following ALi chipsets. The supported chipsets
|
||||
include M1541, M1621, M1631, M1632, M1641,M1647,and M1651.
|
||||
|
|
@ -45,7 +45,7 @@ config AGP_ALI
|
|||
config AGP_ATI
|
||||
tristate "ATI chipset support"
|
||||
depends on AGP && X86_32
|
||||
---help---
|
||||
help
|
||||
This option gives you AGP support for the GLX component of
|
||||
X on the ATI RadeonIGP family of chipsets.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
menuconfig HW_RANDOM
|
||||
tristate "Hardware Random Number Generator Core support"
|
||||
default m
|
||||
---help---
|
||||
help
|
||||
Hardware Random Number Generator Core infrastructure.
|
||||
|
||||
To compile this driver as a module, choose M here: the
|
||||
|
|
@ -24,7 +24,7 @@ if HW_RANDOM
|
|||
config HW_RANDOM_TIMERIOMEM
|
||||
tristate "Timer IOMEM HW Random Number Generator support"
|
||||
depends on HAS_IOMEM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for a generic Random
|
||||
Number Generator used by reading a 'dumb' iomem address that
|
||||
is to be read no faster than, for example, once a second;
|
||||
|
|
@ -39,7 +39,7 @@ config HW_RANDOM_INTEL
|
|||
tristate "Intel HW Random Number Generator support"
|
||||
depends on (X86 || IA64) && PCI
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on Intel i8xx-based motherboards.
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ config HW_RANDOM_AMD
|
|||
tristate "AMD HW Random Number Generator support"
|
||||
depends on (X86 || PPC_MAPLE) && PCI
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on AMD 76x-based motherboards.
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ config HW_RANDOM_ATMEL
|
|||
tristate "Atmel Random Number Generator support"
|
||||
depends on ARCH_AT91 && HAVE_CLK && OF
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on Atmel AT91 devices.
|
||||
|
||||
|
|
@ -79,7 +79,7 @@ config HW_RANDOM_BCM2835
|
|||
depends on ARCH_BCM2835 || ARCH_BCM_NSP || ARCH_BCM_5301X || \
|
||||
ARCH_BCM_63XX || BCM63XX || BMIPS_GENERIC
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on the Broadcom BCM2835 and BCM63xx SoCs.
|
||||
|
||||
|
|
@ -92,7 +92,7 @@ config HW_RANDOM_IPROC_RNG200
|
|||
tristate "Broadcom iProc/STB RNG200 support"
|
||||
depends on ARCH_BCM_IPROC || ARCH_BCM2835 || ARCH_BRCMSTB
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the RNG200
|
||||
hardware found on the Broadcom iProc and STB SoCs.
|
||||
|
||||
|
|
@ -105,7 +105,7 @@ config HW_RANDOM_GEODE
|
|||
tristate "AMD Geode HW Random Number Generator support"
|
||||
depends on X86_32 && PCI
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on the AMD Geode LX.
|
||||
|
||||
|
|
@ -118,7 +118,7 @@ config HW_RANDOM_N2RNG
|
|||
tristate "Niagara2 Random Number Generator support"
|
||||
depends on SPARC64
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on Niagara2 cpus.
|
||||
|
||||
|
|
@ -131,7 +131,7 @@ config HW_RANDOM_VIA
|
|||
tristate "VIA HW Random Number Generator support"
|
||||
depends on X86
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on VIA based motherboards.
|
||||
|
||||
|
|
@ -144,7 +144,7 @@ config HW_RANDOM_IXP4XX
|
|||
tristate "Intel IXP4xx NPU HW Pseudo-Random Number Generator support"
|
||||
depends on ARCH_IXP4XX
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Pseudo-Random
|
||||
Number Generator hardware found on the Intel IXP45x/46x NPU.
|
||||
|
||||
|
|
@ -157,7 +157,7 @@ config HW_RANDOM_OMAP
|
|||
tristate "OMAP Random Number Generator support"
|
||||
depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || ARCH_MVEBU
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on OMAP16xx, OMAP2/3/4/5, AM33xx/AM43xx
|
||||
multimedia processors, and Marvell Armada 7k/8k SoCs.
|
||||
|
|
@ -171,7 +171,7 @@ config HW_RANDOM_OMAP3_ROM
|
|||
tristate "OMAP3 ROM Random Number Generator support"
|
||||
depends on ARCH_OMAP3
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on OMAP34xx processors.
|
||||
|
||||
|
|
@ -184,7 +184,7 @@ config HW_RANDOM_OCTEON
|
|||
tristate "Octeon Random Number Generator support"
|
||||
depends on CAVIUM_OCTEON_SOC
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on Octeon processors.
|
||||
|
||||
|
|
@ -197,7 +197,7 @@ config HW_RANDOM_PASEMI
|
|||
tristate "PA Semi HW Random Number Generator support"
|
||||
depends on PPC_PASEMI
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on PA Semi PWRficient SoCs.
|
||||
|
||||
|
|
@ -209,7 +209,7 @@ config HW_RANDOM_PASEMI
|
|||
config HW_RANDOM_VIRTIO
|
||||
tristate "VirtIO Random Number Generator support"
|
||||
depends on VIRTIO
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the virtual Random Number
|
||||
Generator hardware.
|
||||
|
||||
|
|
@ -220,7 +220,7 @@ config HW_RANDOM_TX4939
|
|||
tristate "TX4939 Random Number Generator support"
|
||||
depends on SOC_TX4939
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on TX4939 SoC.
|
||||
|
||||
|
|
@ -233,7 +233,7 @@ config HW_RANDOM_MXC_RNGA
|
|||
tristate "Freescale i.MX RNGA Random Number Generator"
|
||||
depends on SOC_IMX31
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on Freescale i.MX processors.
|
||||
|
||||
|
|
@ -247,7 +247,7 @@ config HW_RANDOM_IMX_RNGC
|
|||
depends on HAS_IOMEM && HAVE_CLK
|
||||
depends on SOC_IMX25 || COMPILE_TEST
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator Version C hardware found on some Freescale i.MX
|
||||
processors. Version B is also supported by this driver.
|
||||
|
|
@ -261,7 +261,7 @@ config HW_RANDOM_NOMADIK
|
|||
tristate "ST-Ericsson Nomadik Random Number Generator support"
|
||||
depends on ARCH_NOMADIK
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on ST-Ericsson SoCs (8815 and 8500).
|
||||
|
||||
|
|
@ -274,7 +274,7 @@ config HW_RANDOM_PSERIES
|
|||
tristate "pSeries HW Random Number Generator support"
|
||||
depends on PPC64 && IBMVIO
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on POWER7+ machines and above
|
||||
|
||||
|
|
@ -287,7 +287,7 @@ config HW_RANDOM_POWERNV
|
|||
tristate "PowerNV Random Number Generator support"
|
||||
depends on PPC_POWERNV
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This is the driver for Random Number Generator hardware found
|
||||
in POWER7+ and above machines for PowerNV platform.
|
||||
|
||||
|
|
@ -300,7 +300,7 @@ config HW_RANDOM_HISI
|
|||
tristate "Hisilicon Random Number Generator support"
|
||||
depends on HW_RANDOM && ARCH_HISI
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on Hisilicon Hip04 and Hip05 SoC.
|
||||
|
||||
|
|
@ -325,7 +325,7 @@ config HW_RANDOM_HISI_V2
|
|||
config HW_RANDOM_ST
|
||||
tristate "ST Microelectronics HW Random Number Generator support"
|
||||
depends on HW_RANDOM && ARCH_STI
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on STi series of SoCs.
|
||||
|
||||
|
|
@ -336,7 +336,7 @@ config HW_RANDOM_XGENE
|
|||
tristate "APM X-Gene True Random Number Generator (TRNG) support"
|
||||
depends on HW_RANDOM && ARCH_XGENE
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on APM X-Gene SoC.
|
||||
|
||||
|
|
@ -363,7 +363,7 @@ config HW_RANDOM_PIC32
|
|||
tristate "Microchip PIC32 Random Number Generator support"
|
||||
depends on HW_RANDOM && MACH_PIC32
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on a PIC32.
|
||||
|
||||
|
|
@ -377,7 +377,7 @@ config HW_RANDOM_MESON
|
|||
depends on HW_RANDOM
|
||||
depends on ARCH_MESON || COMPILE_TEST
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on Amlogic Meson SoCs.
|
||||
|
||||
|
|
@ -390,7 +390,7 @@ config HW_RANDOM_CAVIUM
|
|||
tristate "Cavium ThunderX Random Number Generator support"
|
||||
depends on HW_RANDOM && PCI && (ARM64 || (COMPILE_TEST && 64BIT))
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on Cavium SoCs.
|
||||
|
||||
|
|
@ -404,7 +404,7 @@ config HW_RANDOM_MTK
|
|||
depends on HW_RANDOM
|
||||
depends on ARCH_MEDIATEK || COMPILE_TEST
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the Random Number
|
||||
Generator hardware found on Mediatek SoCs.
|
||||
|
||||
|
|
@ -417,7 +417,7 @@ config HW_RANDOM_S390
|
|||
tristate "S390 True Random Number Generator support"
|
||||
depends on S390
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support for the True
|
||||
Random Number Generator available as CPACF extension
|
||||
on modern s390 hardware platforms.
|
||||
|
|
@ -431,7 +431,7 @@ config HW_RANDOM_EXYNOS
|
|||
tristate "Samsung Exynos True Random Number Generator support"
|
||||
depends on ARCH_EXYNOS || COMPILE_TEST
|
||||
default HW_RANDOM
|
||||
---help---
|
||||
help
|
||||
This driver provides support for the True Random Number
|
||||
Generator available in Exynos SoCs.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ menuconfig TCG_TPM
|
|||
imply SECURITYFS
|
||||
select CRYPTO
|
||||
select CRYPTO_HASH_INFO
|
||||
---help---
|
||||
help
|
||||
If you have a TPM security chip in your system, which
|
||||
implements the Trusted Computing Group's specification,
|
||||
say Yes and it will be accessible from within Linux. For
|
||||
|
|
@ -31,7 +31,7 @@ config HW_RANDOM_TPM
|
|||
bool "TPM HW Random Number Generator support"
|
||||
depends on TCG_TPM && HW_RANDOM && !(TCG_TPM=y && HW_RANDOM=m)
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
This setting exposes the TPM's Random Number Generator as a hwrng
|
||||
device. This allows the kernel to collect randomness from the TPM at
|
||||
boot, and provides the TPM randomines in /dev/hwrng.
|
||||
|
|
@ -40,7 +40,7 @@ config HW_RANDOM_TPM
|
|||
|
||||
config TCG_TIS_CORE
|
||||
tristate
|
||||
---help---
|
||||
help
|
||||
TCG TIS TPM core driver. It implements the TPM TCG TIS logic and hooks
|
||||
into the TPM kernel APIs. Physical layers will register against it.
|
||||
|
||||
|
|
@ -48,7 +48,7 @@ config TCG_TIS
|
|||
tristate "TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface"
|
||||
depends on X86 || OF
|
||||
select TCG_TIS_CORE
|
||||
---help---
|
||||
help
|
||||
If you have a TPM security chip that is compliant with the
|
||||
TCG TIS 1.2 TPM specification (TPM1.2) or the TCG PTP FIFO
|
||||
specification (TPM2.0) say Yes and it will be accessible from
|
||||
|
|
@ -59,7 +59,7 @@ config TCG_TIS_SPI
|
|||
tristate "TPM Interface Specification 1.3 Interface / TPM 2.0 FIFO Interface - (SPI)"
|
||||
depends on SPI
|
||||
select TCG_TIS_CORE
|
||||
---help---
|
||||
help
|
||||
If you have a TPM security chip which is connected to a regular,
|
||||
non-tcg SPI master (i.e. most embedded platforms) that is compliant with the
|
||||
TCG TIS 1.3 TPM specification (TPM1.2) or the TCG PTP FIFO
|
||||
|
|
@ -77,7 +77,7 @@ config TCG_TIS_SPI_CR50
|
|||
config TCG_TIS_I2C_ATMEL
|
||||
tristate "TPM Interface Specification 1.2 Interface (I2C - Atmel)"
|
||||
depends on I2C
|
||||
---help---
|
||||
help
|
||||
If you have an Atmel I2C TPM security chip say Yes and it will be
|
||||
accessible from within Linux.
|
||||
To compile this driver as a module, choose M here; the module will
|
||||
|
|
@ -86,7 +86,7 @@ config TCG_TIS_I2C_ATMEL
|
|||
config TCG_TIS_I2C_INFINEON
|
||||
tristate "TPM Interface Specification 1.2 Interface (I2C - Infineon)"
|
||||
depends on I2C
|
||||
---help---
|
||||
help
|
||||
If you have a TPM security chip that is compliant with the
|
||||
TCG TIS 1.2 TPM specification and Infineon's I2C Protocol Stack
|
||||
Specification 0.20 say Yes and it will be accessible from within
|
||||
|
|
@ -97,7 +97,7 @@ config TCG_TIS_I2C_INFINEON
|
|||
config TCG_TIS_I2C_NUVOTON
|
||||
tristate "TPM Interface Specification 1.2 Interface (I2C - Nuvoton)"
|
||||
depends on I2C
|
||||
---help---
|
||||
help
|
||||
If you have a TPM security chip with an I2C interface from
|
||||
Nuvoton Technology Corp. say Yes and it will be accessible
|
||||
from within Linux.
|
||||
|
|
@ -107,7 +107,7 @@ config TCG_TIS_I2C_NUVOTON
|
|||
config TCG_NSC
|
||||
tristate "National Semiconductor TPM Interface"
|
||||
depends on X86
|
||||
---help---
|
||||
help
|
||||
If you have a TPM security chip from National Semiconductor
|
||||
say Yes and it will be accessible from within Linux. To
|
||||
compile this driver as a module, choose M here; the module
|
||||
|
|
@ -116,7 +116,7 @@ config TCG_NSC
|
|||
config TCG_ATMEL
|
||||
tristate "Atmel TPM Interface"
|
||||
depends on PPC64 || HAS_IOPORT_MAP
|
||||
---help---
|
||||
help
|
||||
If you have a TPM security chip from Atmel say Yes and it
|
||||
will be accessible from within Linux. To compile this driver
|
||||
as a module, choose M here; the module will be called tpm_atmel.
|
||||
|
|
@ -124,7 +124,7 @@ config TCG_ATMEL
|
|||
config TCG_INFINEON
|
||||
tristate "Infineon Technologies TPM Interface"
|
||||
depends on PNP
|
||||
---help---
|
||||
help
|
||||
If you have a TPM security chip from Infineon Technologies
|
||||
(either SLD 9630 TT 1.1 or SLB 9635 TT 1.2) say Yes and it
|
||||
will be accessible from within Linux.
|
||||
|
|
@ -136,7 +136,7 @@ config TCG_INFINEON
|
|||
config TCG_IBMVTPM
|
||||
tristate "IBM VTPM Interface"
|
||||
depends on PPC_PSERIES
|
||||
---help---
|
||||
help
|
||||
If you have IBM virtual TPM (VTPM) support say Yes and it
|
||||
will be accessible from within Linux. To compile this driver
|
||||
as a module, choose M here; the module will be called tpm_ibmvtpm.
|
||||
|
|
@ -145,7 +145,7 @@ config TCG_XEN
|
|||
tristate "XEN TPM Interface"
|
||||
depends on TCG_TPM && XEN
|
||||
select XEN_XENBUS_FRONTEND
|
||||
---help---
|
||||
help
|
||||
If you want to make TPM support available to a Xen user domain,
|
||||
say Yes and it will be accessible from within Linux. See
|
||||
the manpages for xl, xl.conf, and docs/misc/vtpm.txt in
|
||||
|
|
@ -156,7 +156,7 @@ config TCG_XEN
|
|||
config TCG_CRB
|
||||
tristate "TPM 2.0 CRB Interface"
|
||||
depends on ACPI
|
||||
---help---
|
||||
help
|
||||
If you have a TPM security chip that is compliant with the
|
||||
TCG CRB 2.0 TPM specification say Yes and it will be accessible
|
||||
from within Linux. To compile this driver as a module, choose
|
||||
|
|
@ -165,7 +165,7 @@ config TCG_CRB
|
|||
config TCG_VTPM_PROXY
|
||||
tristate "VTPM Proxy Interface"
|
||||
depends on TCG_TPM
|
||||
---help---
|
||||
help
|
||||
This driver proxies for an emulated TPM (vTPM) running in userspace.
|
||||
A device /dev/vtpmx is provided that creates a device pair
|
||||
/dev/vtpmX and a server-side file descriptor on which the vTPM
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# SPDX-License-Identifier: GPL-2.0-only
|
||||
config TCG_TIS_ST33ZP24
|
||||
tristate
|
||||
---help---
|
||||
help
|
||||
STMicroelectronics ST33ZP24 core driver. It implements the core
|
||||
TPM1.2 logic and hooks into the TPM kernel APIs. Physical layers will
|
||||
register against it.
|
||||
|
|
@ -13,7 +13,7 @@ config TCG_TIS_ST33ZP24_I2C
|
|||
tristate "STMicroelectronics TPM Interface Specification 1.2 Interface (I2C)"
|
||||
depends on I2C
|
||||
select TCG_TIS_ST33ZP24
|
||||
---help---
|
||||
help
|
||||
This module adds support for the STMicroelectronics TPM security chip
|
||||
ST33ZP24 with i2c interface.
|
||||
To compile this driver as a module, choose M here; the module will be
|
||||
|
|
@ -23,7 +23,7 @@ config TCG_TIS_ST33ZP24_SPI
|
|||
tristate "STMicroelectronics TPM Interface Specification 1.2 Interface (SPI)"
|
||||
depends on SPI
|
||||
select TCG_TIS_ST33ZP24
|
||||
---help---
|
||||
help
|
||||
This module adds support for the STMicroelectronics TPM security chip
|
||||
ST33ZP24 with spi interface.
|
||||
To compile this driver as a module, choose M here; the module will be
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ menuconfig COMMON_CLK
|
|||
select CLKDEV_LOOKUP
|
||||
select SRCU
|
||||
select RATIONAL
|
||||
---help---
|
||||
help
|
||||
The common clock framework is a single definition of struct
|
||||
clk, useful across many platforms, as well as an
|
||||
implementation of the clock API in include/linux/clk.h.
|
||||
|
|
@ -41,7 +41,7 @@ if COMMON_CLK
|
|||
config COMMON_CLK_WM831X
|
||||
tristate "Clock driver for WM831x/2x PMICs"
|
||||
depends on MFD_WM831X
|
||||
---help---
|
||||
help
|
||||
Supports the clocking subsystem of the WM831x/2x series of
|
||||
PMICs from Wolfson Microelectronics.
|
||||
|
||||
|
|
@ -50,14 +50,14 @@ source "drivers/clk/versatile/Kconfig"
|
|||
config CLK_HSDK
|
||||
bool "PLL Driver for HSDK platform"
|
||||
depends on OF || COMPILE_TEST
|
||||
---help---
|
||||
help
|
||||
This driver supports the HSDK core, system, ddr, tunnel and hdmi PLLs
|
||||
control.
|
||||
|
||||
config COMMON_CLK_MAX77686
|
||||
tristate "Clock driver for Maxim 77620/77686/77802 MFD"
|
||||
depends on MFD_MAX77686 || MFD_MAX77620 || COMPILE_TEST
|
||||
---help---
|
||||
help
|
||||
This driver supports Maxim 77620/77686/77802 crystal oscillator
|
||||
clock.
|
||||
|
||||
|
|
@ -70,7 +70,7 @@ config COMMON_CLK_MAX9485
|
|||
config COMMON_CLK_RK808
|
||||
tristate "Clock driver for RK805/RK808/RK809/RK817/RK818"
|
||||
depends on MFD_RK808
|
||||
---help---
|
||||
help
|
||||
This driver supports RK805, RK809 and RK817, RK808 and RK818 crystal oscillator clock.
|
||||
These multi-function devices have two fixed-rate oscillators, clocked at 32KHz each.
|
||||
Clkout1 is always on, Clkout2 can off by control register.
|
||||
|
|
@ -80,7 +80,7 @@ config COMMON_CLK_HI655X
|
|||
depends on (MFD_HI655X_PMIC || COMPILE_TEST)
|
||||
depends on REGMAP
|
||||
default MFD_HI655X_PMIC
|
||||
---help---
|
||||
help
|
||||
This driver supports the hi655x PMIC clock. This
|
||||
multi-function device has one fixed-rate oscillator, clocked
|
||||
at 32KHz.
|
||||
|
|
@ -88,7 +88,7 @@ config COMMON_CLK_HI655X
|
|||
config COMMON_CLK_SCMI
|
||||
tristate "Clock driver controlled via SCMI interface"
|
||||
depends on ARM_SCMI_PROTOCOL || COMPILE_TEST
|
||||
---help---
|
||||
help
|
||||
This driver provides support for clocks that are controlled
|
||||
by firmware that implements the SCMI interface.
|
||||
|
||||
|
|
@ -98,7 +98,7 @@ config COMMON_CLK_SCMI
|
|||
config COMMON_CLK_SCPI
|
||||
tristate "Clock driver controlled via SCPI interface"
|
||||
depends on ARM_SCPI_PROTOCOL || COMPILE_TEST
|
||||
---help---
|
||||
help
|
||||
This driver provides support for clocks that are controlled
|
||||
by firmware that implements the SCPI interface.
|
||||
|
||||
|
|
@ -121,7 +121,7 @@ config COMMON_CLK_SI5351
|
|||
depends on I2C
|
||||
select REGMAP_I2C
|
||||
select RATIONAL
|
||||
---help---
|
||||
help
|
||||
This driver supports Silicon Labs 5351A/B/C programmable clock
|
||||
generators.
|
||||
|
||||
|
|
@ -163,7 +163,7 @@ config COMMON_CLK_CDCE706
|
|||
depends on I2C
|
||||
select REGMAP_I2C
|
||||
select RATIONAL
|
||||
---help---
|
||||
help
|
||||
This driver supports TI CDCE706 programmable 3-PLL clock synthesizer.
|
||||
|
||||
config COMMON_CLK_CDCE925
|
||||
|
|
@ -206,7 +206,7 @@ config COMMON_CLK_GEMINI
|
|||
depends on ARCH_GEMINI || COMPILE_TEST
|
||||
select MFD_SYSCON
|
||||
select RESET_CONTROLLER
|
||||
---help---
|
||||
help
|
||||
This driver supports the SoC clocks on the Cortina Systems Gemini
|
||||
platform, also known as SL3516 or CS3516.
|
||||
|
||||
|
|
@ -216,7 +216,7 @@ config COMMON_CLK_ASPEED
|
|||
default ARCH_ASPEED
|
||||
select MFD_SYSCON
|
||||
select RESET_CONTROLLER
|
||||
---help---
|
||||
help
|
||||
This driver supports the SoC clocks on the Aspeed BMC platforms.
|
||||
|
||||
The G4 and G5 series, including the ast2400 and ast2500, are supported
|
||||
|
|
@ -225,7 +225,7 @@ config COMMON_CLK_ASPEED
|
|||
config COMMON_CLK_S2MPS11
|
||||
tristate "Clock driver for S2MPS1X/S5M8767 MFD"
|
||||
depends on MFD_SEC_CORE || COMPILE_TEST
|
||||
---help---
|
||||
help
|
||||
This driver supports S2MPS11/S2MPS14/S5M8767 crystal oscillator
|
||||
clock. These multi-function devices have two (S2MPS14) or three
|
||||
(S2MPS11, S5M8767) fixed-rate oscillators, clocked at 32KHz each.
|
||||
|
|
@ -233,7 +233,7 @@ config COMMON_CLK_S2MPS11
|
|||
config CLK_TWL6040
|
||||
tristate "External McPDM functional clock from twl6040"
|
||||
depends on TWL6040_CORE
|
||||
---help---
|
||||
help
|
||||
Enable the external functional clock support on OMAP4+ platforms for
|
||||
McPDM. McPDM module is using the external bit clock on the McPDM bus
|
||||
as functional clock.
|
||||
|
|
@ -248,7 +248,7 @@ config COMMON_CLK_AXI_CLKGEN
|
|||
config CLK_QORIQ
|
||||
bool "Clock driver for Freescale QorIQ platforms"
|
||||
depends on (PPC_E500MC || ARM || ARM64 || COMPILE_TEST) && OF
|
||||
---help---
|
||||
help
|
||||
This adds the clock driver support for Freescale QorIQ platforms
|
||||
using common clock framework.
|
||||
|
||||
|
|
@ -266,7 +266,7 @@ config COMMON_CLK_XGENE
|
|||
bool "Clock driver for APM XGene SoC"
|
||||
default ARCH_XGENE
|
||||
depends on ARM64 || COMPILE_TEST
|
||||
---help---
|
||||
help
|
||||
Support for the APM X-Gene SoC reference, PLL, and device clocks.
|
||||
|
||||
config COMMON_CLK_LOCHNAGAR
|
||||
|
|
@ -280,26 +280,26 @@ config COMMON_CLK_NXP
|
|||
def_bool COMMON_CLK && (ARCH_LPC18XX || ARCH_LPC32XX)
|
||||
select REGMAP_MMIO if ARCH_LPC32XX
|
||||
select MFD_SYSCON if ARCH_LPC18XX
|
||||
---help---
|
||||
help
|
||||
Support for clock providers on NXP platforms.
|
||||
|
||||
config COMMON_CLK_PALMAS
|
||||
tristate "Clock driver for TI Palmas devices"
|
||||
depends on MFD_PALMAS
|
||||
---help---
|
||||
help
|
||||
This driver supports TI Palmas devices 32KHz output KG and KG_AUDIO
|
||||
using common clock framework.
|
||||
|
||||
config COMMON_CLK_PWM
|
||||
tristate "Clock driver for PWMs used as clock outputs"
|
||||
depends on PWM
|
||||
---help---
|
||||
help
|
||||
Adapter driver so that any PWM output can be (mis)used as clock signal
|
||||
at 50% duty cycle.
|
||||
|
||||
config COMMON_CLK_PXA
|
||||
def_bool COMMON_CLK && ARCH_PXA
|
||||
---help---
|
||||
help
|
||||
Support for the Marvell PXA SoC.
|
||||
|
||||
config COMMON_CLK_PIC32
|
||||
|
|
@ -309,7 +309,7 @@ config COMMON_CLK_OXNAS
|
|||
bool "Clock driver for the OXNAS SoC Family"
|
||||
depends on ARCH_OXNAS || COMPILE_TEST
|
||||
select MFD_SYSCON
|
||||
---help---
|
||||
help
|
||||
Support for the OXNAS SoC Family clocks.
|
||||
|
||||
config COMMON_CLK_VC5
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ config COMMON_CLK_BOSTON
|
|||
bool "Clock driver for MIPS Boston boards"
|
||||
depends on MIPS || COMPILE_TEST
|
||||
select MFD_SYSCON
|
||||
---help---
|
||||
help
|
||||
Enable this to support the system & CPU clocks on the MIPS Boston
|
||||
development board from Imagination Technologies. These are simple
|
||||
fixed rate clocks whose rate is determined by reading a platform
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
config COMMON_CLK_KEYSTONE
|
||||
tristate "Clock drivers for Keystone based SOCs"
|
||||
depends on (ARCH_KEYSTONE || COMPILE_TEST) && OF
|
||||
---help---
|
||||
help
|
||||
Supports clock drivers for Keystone based SOCs. These SOCs have local
|
||||
a power sleep control module that gate the clock to the IPs and PLLs.
|
||||
|
||||
|
|
@ -11,7 +11,7 @@ config TI_SCI_CLK
|
|||
depends on (ARCH_KEYSTONE || ARCH_K3 || COMPILE_TEST) && OF
|
||||
depends on TI_SCI_PROTOCOL
|
||||
default ARCH_KEYSTONE
|
||||
---help---
|
||||
help
|
||||
This adds the clock driver support over TI System Control Interface.
|
||||
If you wish to use clock resources from the PMMC firmware, say Y.
|
||||
Otherwise, say N.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ menu "Clock driver for MediaTek SoC"
|
|||
config COMMON_CLK_MEDIATEK
|
||||
bool
|
||||
select RESET_CONTROLLER
|
||||
---help---
|
||||
help
|
||||
MediaTek SoCs' clock support.
|
||||
|
||||
config COMMON_CLK_MT2701
|
||||
|
|
@ -16,55 +16,55 @@ config COMMON_CLK_MT2701
|
|||
depends on (ARCH_MEDIATEK && ARM) || COMPILE_TEST
|
||||
select COMMON_CLK_MEDIATEK
|
||||
default ARCH_MEDIATEK && ARM
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2701 basic clocks.
|
||||
|
||||
config COMMON_CLK_MT2701_MMSYS
|
||||
bool "Clock driver for MediaTek MT2701 mmsys"
|
||||
depends on COMMON_CLK_MT2701
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2701 mmsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2701_IMGSYS
|
||||
bool "Clock driver for MediaTek MT2701 imgsys"
|
||||
depends on COMMON_CLK_MT2701
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2701 imgsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2701_VDECSYS
|
||||
bool "Clock driver for MediaTek MT2701 vdecsys"
|
||||
depends on COMMON_CLK_MT2701
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2701 vdecsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2701_HIFSYS
|
||||
bool "Clock driver for MediaTek MT2701 hifsys"
|
||||
depends on COMMON_CLK_MT2701
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2701 hifsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2701_ETHSYS
|
||||
bool "Clock driver for MediaTek MT2701 ethsys"
|
||||
depends on COMMON_CLK_MT2701
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2701 ethsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2701_BDPSYS
|
||||
bool "Clock driver for MediaTek MT2701 bdpsys"
|
||||
depends on COMMON_CLK_MT2701
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2701 bdpsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2701_AUDSYS
|
||||
bool "Clock driver for Mediatek MT2701 audsys"
|
||||
depends on COMMON_CLK_MT2701
|
||||
---help---
|
||||
help
|
||||
This driver supports Mediatek MT2701 audsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2701_G3DSYS
|
||||
bool "Clock driver for MediaTek MT2701 g3dsys"
|
||||
depends on COMMON_CLK_MT2701
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2701 g3dsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2712
|
||||
|
|
@ -72,49 +72,49 @@ config COMMON_CLK_MT2712
|
|||
depends on (ARCH_MEDIATEK && ARM64) || COMPILE_TEST
|
||||
select COMMON_CLK_MEDIATEK
|
||||
default ARCH_MEDIATEK && ARM64
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2712 basic clocks.
|
||||
|
||||
config COMMON_CLK_MT2712_BDPSYS
|
||||
bool "Clock driver for MediaTek MT2712 bdpsys"
|
||||
depends on COMMON_CLK_MT2712
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2712 bdpsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2712_IMGSYS
|
||||
bool "Clock driver for MediaTek MT2712 imgsys"
|
||||
depends on COMMON_CLK_MT2712
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2712 imgsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2712_JPGDECSYS
|
||||
bool "Clock driver for MediaTek MT2712 jpgdecsys"
|
||||
depends on COMMON_CLK_MT2712
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2712 jpgdecsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2712_MFGCFG
|
||||
bool "Clock driver for MediaTek MT2712 mfgcfg"
|
||||
depends on COMMON_CLK_MT2712
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2712 mfgcfg clocks.
|
||||
|
||||
config COMMON_CLK_MT2712_MMSYS
|
||||
bool "Clock driver for MediaTek MT2712 mmsys"
|
||||
depends on COMMON_CLK_MT2712
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2712 mmsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2712_VDECSYS
|
||||
bool "Clock driver for MediaTek MT2712 vdecsys"
|
||||
depends on COMMON_CLK_MT2712
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2712 vdecsys clocks.
|
||||
|
||||
config COMMON_CLK_MT2712_VENCSYS
|
||||
bool "Clock driver for MediaTek MT2712 vencsys"
|
||||
depends on COMMON_CLK_MT2712
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT2712 vencsys clocks.
|
||||
|
||||
config COMMON_CLK_MT6765
|
||||
|
|
@ -264,31 +264,31 @@ config COMMON_CLK_MT6797
|
|||
depends on (ARCH_MEDIATEK && ARM64) || COMPILE_TEST
|
||||
select COMMON_CLK_MEDIATEK
|
||||
default ARCH_MEDIATEK && ARM64
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT6797 basic clocks.
|
||||
|
||||
config COMMON_CLK_MT6797_MMSYS
|
||||
bool "Clock driver for MediaTek MT6797 mmsys"
|
||||
depends on COMMON_CLK_MT6797
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT6797 mmsys clocks.
|
||||
|
||||
config COMMON_CLK_MT6797_IMGSYS
|
||||
bool "Clock driver for MediaTek MT6797 imgsys"
|
||||
depends on COMMON_CLK_MT6797
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT6797 imgsys clocks.
|
||||
|
||||
config COMMON_CLK_MT6797_VDECSYS
|
||||
bool "Clock driver for MediaTek MT6797 vdecsys"
|
||||
depends on COMMON_CLK_MT6797
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT6797 vdecsys clocks.
|
||||
|
||||
config COMMON_CLK_MT6797_VENCSYS
|
||||
bool "Clock driver for MediaTek MT6797 vencsys"
|
||||
depends on COMMON_CLK_MT6797
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT6797 vencsys clocks.
|
||||
|
||||
config COMMON_CLK_MT7622
|
||||
|
|
@ -296,28 +296,28 @@ config COMMON_CLK_MT7622
|
|||
depends on ARCH_MEDIATEK || COMPILE_TEST
|
||||
select COMMON_CLK_MEDIATEK
|
||||
default ARCH_MEDIATEK
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT7622 basic clocks and clocks
|
||||
required for various periperals found on MediaTek.
|
||||
|
||||
config COMMON_CLK_MT7622_ETHSYS
|
||||
bool "Clock driver for MediaTek MT7622 ETHSYS"
|
||||
depends on COMMON_CLK_MT7622
|
||||
---help---
|
||||
help
|
||||
This driver add support for clocks for Ethernet and SGMII
|
||||
required on MediaTek MT7622 SoC.
|
||||
|
||||
config COMMON_CLK_MT7622_HIFSYS
|
||||
bool "Clock driver for MediaTek MT7622 HIFSYS"
|
||||
depends on COMMON_CLK_MT7622
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT7622 HIFSYS clocks providing
|
||||
to PCI-E and USB.
|
||||
|
||||
config COMMON_CLK_MT7622_AUDSYS
|
||||
bool "Clock driver for MediaTek MT7622 AUDSYS"
|
||||
depends on COMMON_CLK_MT7622
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT7622 AUDSYS clocks providing
|
||||
to audio consumers such as I2S and TDM.
|
||||
|
||||
|
|
@ -326,21 +326,21 @@ config COMMON_CLK_MT7629
|
|||
depends on (ARCH_MEDIATEK && ARM) || COMPILE_TEST
|
||||
select COMMON_CLK_MEDIATEK
|
||||
default ARCH_MEDIATEK && ARM
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT7629 basic clocks and clocks
|
||||
required for various periperals found on MediaTek.
|
||||
|
||||
config COMMON_CLK_MT7629_ETHSYS
|
||||
bool "Clock driver for MediaTek MT7629 ETHSYS"
|
||||
depends on COMMON_CLK_MT7629
|
||||
---help---
|
||||
help
|
||||
This driver add support for clocks for Ethernet and SGMII
|
||||
required on MediaTek MT7629 SoC.
|
||||
|
||||
config COMMON_CLK_MT7629_HIFSYS
|
||||
bool "Clock driver for MediaTek MT7629 HIFSYS"
|
||||
depends on COMMON_CLK_MT7629
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT7629 HIFSYS clocks providing
|
||||
to PCI-E and USB.
|
||||
|
||||
|
|
@ -349,7 +349,7 @@ config COMMON_CLK_MT8135
|
|||
depends on (ARCH_MEDIATEK && ARM) || COMPILE_TEST
|
||||
select COMMON_CLK_MEDIATEK
|
||||
default ARCH_MEDIATEK && ARM
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT8135 clocks.
|
||||
|
||||
config COMMON_CLK_MT8173
|
||||
|
|
@ -357,7 +357,7 @@ config COMMON_CLK_MT8173
|
|||
depends on ARCH_MEDIATEK || COMPILE_TEST
|
||||
select COMMON_CLK_MEDIATEK
|
||||
default ARCH_MEDIATEK
|
||||
---help---
|
||||
help
|
||||
This driver supports MediaTek MT8173 clocks.
|
||||
|
||||
config COMMON_CLK_MT8173_MMSYS
|
||||
|
|
|
|||
|
|
@ -3,5 +3,5 @@ config COMMON_CLK_TI_ADPLL
|
|||
tristate "Clock driver for dm814x ADPLL"
|
||||
depends on ARCH_OMAP2PLUS || COMPILE_TEST
|
||||
default y if SOC_TI81XX
|
||||
---help---
|
||||
help
|
||||
ADPLL clock driver for the dm814x SoC using common clock framework.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ menu "Clock driver for ARM Reference designs"
|
|||
config ICST
|
||||
bool "Clock driver for ARM Reference designs ICST"
|
||||
select REGMAP_MMIO
|
||||
---help---
|
||||
help
|
||||
Supports clocking on ARM Reference designs:
|
||||
- Integrator/AP and Integrator/CP
|
||||
- RealView PB1176, EB, PB11MP and PBX
|
||||
|
|
@ -15,7 +15,7 @@ config ICST
|
|||
config CLK_SP810
|
||||
bool "Clock driver for ARM SP810 System Controller"
|
||||
default y if (ARCH_VEXPRESS && ARM)
|
||||
---help---
|
||||
help
|
||||
Supports clock muxing (REFCLK/TIMCLK to TIMERCLKEN0-3) capabilities
|
||||
of the ARM SP810 System Controller cell.
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ config CLK_VEXPRESS_OSC
|
|||
depends on VEXPRESS_CONFIG
|
||||
select REGMAP_MMIO
|
||||
default y if ARCH_VEXPRESS
|
||||
---help---
|
||||
help
|
||||
Simple regmap-based driver driving clock generators on Versatile
|
||||
Express platforms hidden behind its configuration infrastructure,
|
||||
commonly known as OSCs.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
menuconfig CONNECTOR
|
||||
tristate "Connector - unified userspace <-> kernelspace linker"
|
||||
depends on NET
|
||||
---help---
|
||||
help
|
||||
This is unified userspace <-> kernelspace connector working on top
|
||||
of the netlink socket protocol.
|
||||
|
||||
|
|
@ -16,7 +16,7 @@ config PROC_EVENTS
|
|||
bool "Report process events to userspace"
|
||||
depends on CONNECTOR=y
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Provide a connector that reports process events to userspace. Send
|
||||
events such as fork, exec, id change (uid, gid, suid, etc), and exit.
|
||||
|
||||
|
|
|
|||
|
|
@ -75,7 +75,7 @@ config X86_SFI_CPUFREQ
|
|||
config ELAN_CPUFREQ
|
||||
tristate "AMD Elan SC400 and SC410"
|
||||
depends on MELAN
|
||||
---help---
|
||||
help
|
||||
This adds the CPUFreq driver for AMD Elan SC400 and SC410
|
||||
processors.
|
||||
|
||||
|
|
@ -90,7 +90,7 @@ config ELAN_CPUFREQ
|
|||
config SC520_CPUFREQ
|
||||
tristate "AMD Elan SC520"
|
||||
depends on MELAN
|
||||
---help---
|
||||
help
|
||||
This adds the CPUFreq driver for AMD Elan SC520 processor.
|
||||
|
||||
For details, take a look at <file:Documentation/cpu-freq/>.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
menuconfig CRYPTO_HW
|
||||
bool "Hardware crypto devices"
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Say Y here to get to see options for hardware crypto devices and
|
||||
processors. This option alone does not add any kernel code.
|
||||
|
||||
|
|
@ -334,7 +334,7 @@ config HW_RANDOM_PPC4XX
|
|||
bool "PowerPC 4xx generic true random number generator support"
|
||||
depends on CRYPTO_DEV_PPC4XX && HW_RANDOM
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
This option provides the kernel-side support for the TRNG hardware
|
||||
found in the security function of some PowerPC 4xx SoCs.
|
||||
|
||||
|
|
@ -420,7 +420,7 @@ config CRYPTO_DEV_EXYNOS_RNG
|
|||
depends on ARCH_EXYNOS || COMPILE_TEST
|
||||
depends on HAS_IOMEM
|
||||
select CRYPTO_RNG
|
||||
---help---
|
||||
help
|
||||
This driver provides kernel-side support through the
|
||||
cryptographic API for the pseudo random number generator hardware
|
||||
found on Exynos SoCs.
|
||||
|
|
@ -597,7 +597,7 @@ source "drivers/crypto/marvell/Kconfig"
|
|||
config CRYPTO_DEV_CAVIUM_ZIP
|
||||
tristate "Cavium ZIP driver"
|
||||
depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
|
||||
---help---
|
||||
help
|
||||
Select this option if you want to enable compression/decompression
|
||||
acceleration on Cavium's ARM based SoCs
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ config CRYPTO_DEV_CHELSIO
|
|||
select CRYPTO_SHA512
|
||||
select CRYPTO_AUTHENC
|
||||
select CRYPTO_GF128MUL
|
||||
---help---
|
||||
help
|
||||
The Chelsio Crypto Co-processor driver for T6 adapters.
|
||||
|
||||
For general information about Chelsio and our products, visit
|
||||
|
|
@ -29,7 +29,7 @@ config CHELSIO_IPSEC_INLINE
|
|||
depends on XFRM_OFFLOAD
|
||||
depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
Enable support for IPSec Tx Inline.
|
||||
|
||||
config CRYPTO_DEV_CHELSIO_TLS
|
||||
|
|
@ -37,7 +37,7 @@ config CRYPTO_DEV_CHELSIO_TLS
|
|||
depends on CHELSIO_T4
|
||||
depends on TLS_TOE
|
||||
select CRYPTO_DEV_CHELSIO
|
||||
---help---
|
||||
help
|
||||
Support Chelsio Inline TLS with Chelsio crypto accelerator.
|
||||
|
||||
To compile this driver as a module, choose M here: the module
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ config SYNC_FILE
|
|||
bool "Explicit Synchronization Framework"
|
||||
default n
|
||||
select DMA_SHARED_BUFFER
|
||||
---help---
|
||||
help
|
||||
The Sync File Framework adds explicit synchronization via
|
||||
userspace. It enables send/receive 'struct dma_fence' objects to/from
|
||||
userspace via Sync File fds for synchronization between drivers via
|
||||
|
|
@ -22,7 +22,7 @@ config SW_SYNC
|
|||
default n
|
||||
depends on SYNC_FILE
|
||||
depends on DEBUG_FS
|
||||
---help---
|
||||
help
|
||||
A sync object driver that uses a 32bit counter to coordinate
|
||||
synchronization. Useful when there is no hardware primitive backing
|
||||
the synchronization.
|
||||
|
|
|
|||
|
|
@ -198,7 +198,7 @@ config FSL_DMA
|
|||
depends on FSL_SOC
|
||||
select DMA_ENGINE
|
||||
select ASYNC_TX_ENABLE_CHANNEL_SWITCH
|
||||
---help---
|
||||
help
|
||||
Enable support for the Freescale Elo series DMA controllers.
|
||||
The Elo is the DMA controller on some mpc82xx and mpc83xx parts, the
|
||||
EloPlus is on mpc85xx and mpc86xx and Pxxx parts, and the Elo3 is on
|
||||
|
|
@ -233,7 +233,7 @@ config FSL_RAID
|
|||
depends on FSL_SOC && !ASYNC_TX_ENABLE_CHANNEL_SWITCH
|
||||
select DMA_ENGINE
|
||||
select DMA_ENGINE_RAID
|
||||
---help---
|
||||
help
|
||||
Enable support for Freescale RAID Engine. RAID Engine is
|
||||
available on some QorIQ SoCs (like P5020/P5040). It has
|
||||
the capability to offload memcpy, xor and pq computation
|
||||
|
|
@ -414,7 +414,7 @@ config MPC512X_DMA
|
|||
tristate "Freescale MPC512x built-in DMA engine support"
|
||||
depends on PPC_MPC512x || PPC_MPC831x
|
||||
select DMA_ENGINE
|
||||
---help---
|
||||
help
|
||||
Enable support for the Freescale MPC512x built-in DMA engine.
|
||||
|
||||
config MV_XOR
|
||||
|
|
@ -423,7 +423,7 @@ config MV_XOR
|
|||
select DMA_ENGINE
|
||||
select DMA_ENGINE_RAID
|
||||
select ASYNC_TX_ENABLE_CHANNEL_SWITCH
|
||||
---help---
|
||||
help
|
||||
Enable support for the Marvell XOR engine.
|
||||
|
||||
config MV_XOR_V2
|
||||
|
|
@ -433,7 +433,7 @@ config MV_XOR_V2
|
|||
select DMA_ENGINE_RAID
|
||||
select ASYNC_TX_ENABLE_CHANNEL_SWITCH
|
||||
select GENERIC_MSI_IRQ_DOMAIN
|
||||
---help---
|
||||
help
|
||||
Enable support for the Marvell version 2 XOR engine.
|
||||
|
||||
This engine provides acceleration for copy, XOR and RAID6
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ config MTK_HSDMA
|
|||
depends on ARCH_MEDIATEK || COMPILE_TEST
|
||||
select DMA_ENGINE
|
||||
select DMA_VIRTUAL_CHANNELS
|
||||
---help---
|
||||
help
|
||||
Enable support for High-Speed DMA controller on MediaTek
|
||||
SoCs.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ config QCOM_BAM_DMA
|
|||
depends on ARCH_QCOM || (COMPILE_TEST && OF && ARM)
|
||||
select DMA_ENGINE
|
||||
select DMA_VIRTUAL_CHANNELS
|
||||
---help---
|
||||
help
|
||||
Enable support for the QCOM BAM DMA controller. This controller
|
||||
provides DMA capabilities for a variety of on-chip devices.
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ config EDAC_DECODE_MCE
|
|||
tristate "Decode MCEs in human-readable form (only on AMD for now)"
|
||||
depends on CPU_SUP_AMD && X86_MCE_AMD
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Enable this option if you want to decode Machine Check Exceptions
|
||||
occurring on your machine in human-readable form.
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ config HAVE_EISA
|
|||
menuconfig EISA
|
||||
bool "EISA support"
|
||||
depends on HAVE_EISA
|
||||
---help---
|
||||
help
|
||||
The Extended Industry Standard Architecture (EISA) bus was
|
||||
developed as an open alternative to the IBM MicroChannel bus.
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ config EISA_VLB_PRIMING
|
|||
bool "Vesa Local Bus priming"
|
||||
depends on X86 && EISA
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
Activate this option if your system contains a Vesa Local
|
||||
Bus (VLB) card that identify itself as an EISA card (such as
|
||||
the Adaptec AHA-284x).
|
||||
|
|
@ -37,7 +37,7 @@ config EISA_PCI_EISA
|
|||
bool "Generic PCI/EISA bridge"
|
||||
depends on !PARISC && PCI && EISA
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Activate this option if your system contains a PCI to EISA
|
||||
bridge. If your system have both PCI and EISA slots, you
|
||||
certainly need this option.
|
||||
|
|
@ -51,7 +51,7 @@ config EISA_VIRTUAL_ROOT
|
|||
bool "EISA virtual root device"
|
||||
depends on EISA && (ALPHA || X86)
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Activate this option if your system only have EISA bus
|
||||
(no PCI slots). The Alpha Jensen is an example of such
|
||||
a system.
|
||||
|
|
@ -62,7 +62,7 @@ config EISA_NAMES
|
|||
bool "EISA device name database"
|
||||
depends on EISA
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
By default, the kernel contains a database of all known EISA
|
||||
device names to make the information in sysfs comprehensible
|
||||
to the user. This database increases size of the kernel
|
||||
|
|
|
|||
|
|
@ -139,7 +139,7 @@ config EFI_BOOTLOADER_CONTROL
|
|||
tristate "EFI Bootloader Control"
|
||||
depends on EFI_VARS
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
This module installs a reboot hook, such that if reboot() is
|
||||
invoked with a string argument NNN, "NNN" is copied to the
|
||||
"LoaderEntryOneShot" EFI variable, to be read by the
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ menuconfig FSI
|
|||
tristate "FSI support"
|
||||
depends on OF
|
||||
select CRC4
|
||||
---help---
|
||||
help
|
||||
FSI - the FRU Support Interface - is a simple bus for low-level
|
||||
access to POWER-based hardware.
|
||||
|
||||
|
|
@ -16,7 +16,7 @@ if FSI
|
|||
config FSI_NEW_DEV_NODE
|
||||
bool "Create '/dev/fsi' directory for char devices"
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
This option causes char devices created for FSI devices to be
|
||||
located under a common /dev/fsi/ directory. Set to N unless your
|
||||
userspace has been updated to handle the new location.
|
||||
|
|
@ -32,12 +32,12 @@ config FSI_MASTER_GPIO
|
|||
tristate "GPIO-based FSI master"
|
||||
depends on GPIOLIB
|
||||
select CRC4
|
||||
---help---
|
||||
help
|
||||
This option enables a FSI master driver using GPIO lines.
|
||||
|
||||
config FSI_MASTER_HUB
|
||||
tristate "FSI hub master"
|
||||
---help---
|
||||
help
|
||||
This option enables a FSI hub master driver. Hub is a type of FSI
|
||||
master that is connected to the upstream master via a slave. Hubs
|
||||
allow chaining of FSI links to an arbitrary depth. This allows for
|
||||
|
|
@ -48,7 +48,7 @@ config FSI_MASTER_AST_CF
|
|||
depends on GPIOLIB
|
||||
depends on GPIO_ASPEED
|
||||
select GENERIC_ALLOCATOR
|
||||
---help---
|
||||
help
|
||||
This option enables a FSI master using the AST2400 and AST2500 GPIO
|
||||
lines driven by the internal ColdFire coprocessor. This requires
|
||||
the corresponding machine specific ColdFire firmware to be available.
|
||||
|
|
@ -64,13 +64,13 @@ config FSI_MASTER_ASPEED
|
|||
|
||||
config FSI_SCOM
|
||||
tristate "SCOM FSI client device driver"
|
||||
---help---
|
||||
help
|
||||
This option enables an FSI based SCOM device driver.
|
||||
|
||||
config FSI_SBEFIFO
|
||||
tristate "SBEFIFO FSI client device driver"
|
||||
depends on OF_ADDRESS
|
||||
---help---
|
||||
help
|
||||
This option enables an FSI based SBEFIFO device driver. The SBEFIFO is
|
||||
a pipe-like FSI device for communicating with the self boot engine
|
||||
(SBE) on POWER processors.
|
||||
|
|
@ -78,7 +78,7 @@ config FSI_SBEFIFO
|
|||
config FSI_OCC
|
||||
tristate "OCC SBEFIFO client device driver"
|
||||
depends on FSI_SBEFIFO
|
||||
---help---
|
||||
help
|
||||
This option enables an SBEFIFO based On-Chip Controller (OCC) device
|
||||
driver. The OCC is a device embedded on a POWER processor that collects
|
||||
and aggregates sensor data from the processor and system. The OCC can
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@
|
|||
|
||||
menuconfig GNSS
|
||||
tristate "GNSS receiver support"
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a GNSS receiver (e.g. a GPS receiver).
|
||||
|
||||
To compile this driver as a module, choose M here: the module will
|
||||
|
|
@ -32,7 +32,7 @@ config GNSS_MTK_SERIAL
|
|||
config GNSS_SIRF_SERIAL
|
||||
tristate "SiRFstar GNSS receiver support"
|
||||
depends on SERIAL_DEV_BUS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a SiRFstar-based GNSS receiver which uses a
|
||||
serial interface.
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ config GNSS_UBX_SERIAL
|
|||
tristate "u-blox GNSS receiver support"
|
||||
depends on SERIAL_DEV_BUS
|
||||
select GNSS_SERIAL
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a u-blox GNSS receiver which uses a serial
|
||||
interface.
|
||||
|
||||
|
|
|
|||
|
|
@ -1236,7 +1236,7 @@ config GPIO_TC3589X
|
|||
config GPIO_TIMBERDALE
|
||||
bool "Support for timberdale GPIO IP"
|
||||
depends on MFD_TIMBERDALE
|
||||
---help---
|
||||
help
|
||||
Add support for the GPIO IP in the timberdale FPGA.
|
||||
|
||||
config GPIO_TPS65086
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ config DRM_MEGACHIPS_STDPXXXX_GE_B850V3_FW
|
|||
depends on OF
|
||||
select DRM_KMS_HELPER
|
||||
select DRM_PANEL
|
||||
---help---
|
||||
help
|
||||
This is a driver for the display bridges of
|
||||
GE B850v3 that convert dual channel LVDS
|
||||
to DP++. This is used with the i.MX6 imx-ldb
|
||||
|
|
@ -89,7 +89,7 @@ config DRM_NXP_PTN3460
|
|||
depends on OF
|
||||
select DRM_KMS_HELPER
|
||||
select DRM_PANEL
|
||||
---help---
|
||||
help
|
||||
NXP PTN3460 eDP-LVDS bridge chip driver.
|
||||
|
||||
config DRM_PARADE_PS8622
|
||||
|
|
@ -98,7 +98,7 @@ config DRM_PARADE_PS8622
|
|||
select DRM_PANEL
|
||||
select DRM_KMS_HELPER
|
||||
select BACKLIGHT_CLASS_DEVICE
|
||||
---help---
|
||||
help
|
||||
Parade eDP-LVDS bridge chip driver.
|
||||
|
||||
config DRM_PARADE_PS8640
|
||||
|
|
@ -128,13 +128,13 @@ config DRM_SII902X
|
|||
select REGMAP_I2C
|
||||
select I2C_MUX
|
||||
select SND_SOC_HDMI_CODEC if SND_SOC
|
||||
---help---
|
||||
help
|
||||
Silicon Image sii902x bridge chip driver.
|
||||
|
||||
config DRM_SII9234
|
||||
tristate "Silicon Image SII9234 HDMI/MHL bridge"
|
||||
depends on OF
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want support for the MHL interface.
|
||||
It is an I2C driver, that detects connection of MHL bridge
|
||||
and starts encapsulation of HDMI signal.
|
||||
|
|
@ -150,7 +150,7 @@ config DRM_SIMPLE_BRIDGE
|
|||
config DRM_THINE_THC63LVD1024
|
||||
tristate "Thine THC63LVD1024 LVDS decoder bridge"
|
||||
depends on OF
|
||||
---help---
|
||||
help
|
||||
Thine THC63LVD1024 LVDS/parallel converter driver.
|
||||
|
||||
config DRM_TOSHIBA_TC358764
|
||||
|
|
@ -168,7 +168,7 @@ config DRM_TOSHIBA_TC358767
|
|||
select DRM_KMS_HELPER
|
||||
select REGMAP_I2C
|
||||
select DRM_PANEL
|
||||
---help---
|
||||
help
|
||||
Toshiba TC358767 eDP bridge chip driver.
|
||||
|
||||
config DRM_TOSHIBA_TC358768
|
||||
|
|
@ -185,7 +185,7 @@ config DRM_TI_TFP410
|
|||
tristate "TI TFP410 DVI/HDMI bridge"
|
||||
depends on OF
|
||||
select DRM_KMS_HELPER
|
||||
---help---
|
||||
help
|
||||
Texas Instruments TFP410 DVI/HDMI Transmitter driver
|
||||
|
||||
config DRM_TI_SN65DSI86
|
||||
|
|
|
|||
|
|
@ -71,7 +71,7 @@ config OMAP4_DSS_HDMI_CEC
|
|||
depends on OMAP4_DSS_HDMI
|
||||
select CEC_CORE
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
When selected the HDMI transmitter will support the CEC feature.
|
||||
|
||||
config OMAP5_DSS_HDMI
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
menuconfig GREYBUS
|
||||
tristate "Greybus support"
|
||||
depends on SYSFS
|
||||
---help---
|
||||
help
|
||||
This option enables the Greybus driver core. Greybus is a
|
||||
hardware protocol that was designed to provide Unipro with a
|
||||
sane application layer. It was originally designed for the
|
||||
|
|
@ -20,7 +20,7 @@ if GREYBUS
|
|||
config GREYBUS_ES2
|
||||
tristate "Greybus ES3 USB host controller"
|
||||
depends on USB
|
||||
---help---
|
||||
help
|
||||
Select this option if you have a Toshiba ES3 USB device that
|
||||
acts as a Greybus "host controller". This device is a bridge
|
||||
from a USB device to a Unipro network.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ config HID
|
|||
tristate "HID bus support"
|
||||
depends on INPUT
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
A human interface device (HID) is a type of computer device that
|
||||
interacts directly with and takes input from humans. The term "HID"
|
||||
most commonly used to refer to the USB-HID specification, but other
|
||||
|
|
@ -31,7 +31,7 @@ config HID_BATTERY_STRENGTH
|
|||
depends on HID
|
||||
select POWER_SUPPLY
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
This option adds support of reporting battery strength (for HID devices
|
||||
that support this feature) through power_supply class so that userspace
|
||||
tools, such as upower, can display it.
|
||||
|
|
@ -39,7 +39,7 @@ config HID_BATTERY_STRENGTH
|
|||
config HIDRAW
|
||||
bool "/dev/hidraw raw HID device support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to support HID devices (from the USB
|
||||
specification standpoint) that aren't strictly user interface
|
||||
devices, like monitor controls and Uninterruptible Power Supplies.
|
||||
|
|
@ -59,7 +59,7 @@ config UHID
|
|||
tristate "User-space I/O driver support for HID subsystem"
|
||||
depends on HID
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to provide HID I/O Drivers from user-space.
|
||||
This allows to write I/O drivers in user-space and feed the data from
|
||||
the device into the kernel. The kernel parses the HID reports, loads the
|
||||
|
|
@ -80,7 +80,7 @@ config HID_GENERIC
|
|||
tristate "Generic HID driver"
|
||||
depends on HID
|
||||
default HID
|
||||
---help---
|
||||
help
|
||||
Support for generic devices on the HID bus. This includes most
|
||||
keyboards and mice, joysticks, tablets and digitizers.
|
||||
|
||||
|
|
@ -96,13 +96,13 @@ config HID_A4TECH
|
|||
tristate "A4 tech mice"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for A4 tech X5 and WOP-35 / Trust 450L mice.
|
||||
|
||||
config HID_ACCUTOUCH
|
||||
tristate "Accutouch touch device"
|
||||
depends on USB_HID
|
||||
---help---
|
||||
help
|
||||
This selects a driver for the Accutouch 2216 touch controller.
|
||||
|
||||
The driver works around a problem in the reported device capabilities
|
||||
|
|
@ -114,14 +114,14 @@ config HID_ACCUTOUCH
|
|||
config HID_ACRUX
|
||||
tristate "ACRUX game controller support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to enable support for ACRUX game controllers.
|
||||
|
||||
config HID_ACRUX_FF
|
||||
bool "ACRUX force feedback support"
|
||||
depends on HID_ACRUX
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to enable force feedback support for ACRUX
|
||||
game controllers.
|
||||
|
||||
|
|
@ -129,7 +129,7 @@ config HID_APPLE
|
|||
tristate "Apple {i,Power,Mac}Books"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for some Apple devices which less or more break
|
||||
HID specification.
|
||||
|
||||
|
|
@ -139,7 +139,7 @@ config HID_APPLE
|
|||
config HID_APPLEIR
|
||||
tristate "Apple infrared receiver"
|
||||
depends on (USB_HID)
|
||||
---help---
|
||||
help
|
||||
Support for Apple infrared remote control. All the Apple computers from
|
||||
2005 onwards include such a port, except the unibody Macbook (2009),
|
||||
and Mac Pros. This receiver is also used in the Apple TV set-top box
|
||||
|
|
@ -153,7 +153,7 @@ config HID_ASUS
|
|||
depends on LEDS_CLASS
|
||||
depends on ASUS_WMI || ASUS_WMI=n
|
||||
select POWER_SUPPLY
|
||||
---help---
|
||||
help
|
||||
Support for Asus notebook built-in keyboard and touchpad via i2c, and
|
||||
the Asus Republic of Gamers laptop keyboard special keys.
|
||||
|
||||
|
|
@ -166,21 +166,21 @@ config HID_ASUS
|
|||
config HID_AUREAL
|
||||
tristate "Aureal"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Aureal Cy se W-01RN Remote Controller and other Aureal derived remotes.
|
||||
|
||||
config HID_BELKIN
|
||||
tristate "Belkin Flip KVM and Wireless keyboard"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for Belkin Flip KVM and Wireless keyboard.
|
||||
|
||||
config HID_BETOP_FF
|
||||
tristate "Betop Production Inc. force feedback support"
|
||||
depends on USB_HID
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to enable force feedback support for devices by
|
||||
BETOP Production Ltd.
|
||||
Currently the following devices are known to be supported:
|
||||
|
|
@ -202,20 +202,20 @@ config HID_CHERRY
|
|||
tristate "Cherry Cymotion keyboard"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for Cherry Cymotion keyboard.
|
||||
|
||||
config HID_CHICONY
|
||||
tristate "Chicony devices"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for Chicony Tactical pad and special keys on Chicony keyboards.
|
||||
|
||||
config HID_CORSAIR
|
||||
tristate "Corsair devices"
|
||||
depends on HID && USB && LEDS_CLASS
|
||||
---help---
|
||||
help
|
||||
Support for Corsair devices that are not fully compliant with the
|
||||
HID standard.
|
||||
|
||||
|
|
@ -247,7 +247,7 @@ config HID_PRODIKEYS
|
|||
tristate "Prodikeys PC-MIDI Keyboard support"
|
||||
depends on HID && SND
|
||||
select SND_RAWMIDI
|
||||
---help---
|
||||
help
|
||||
Support for Prodikeys PC-MIDI Keyboard device support.
|
||||
Say Y here to enable support for this device.
|
||||
- Prodikeys PC-MIDI keyboard.
|
||||
|
|
@ -261,14 +261,14 @@ config HID_PRODIKEYS
|
|||
config HID_CMEDIA
|
||||
tristate "CMedia CM6533 HID audio jack controls"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for CMedia CM6533 HID audio jack controls.
|
||||
|
||||
config HID_CP2112
|
||||
tristate "Silicon Labs CP2112 HID USB-to-SMBus Bridge support"
|
||||
depends on USB_HID && HIDRAW && I2C && GPIOLIB
|
||||
select GPIOLIB_IRQCHIP
|
||||
---help---
|
||||
help
|
||||
Support for Silicon Labs CP2112 HID USB to SMBus Master Bridge.
|
||||
This is a HID device driver which registers as an i2c adapter
|
||||
and gpiochip to expose these functions of the CP2112. The
|
||||
|
|
@ -287,13 +287,13 @@ config HID_CYPRESS
|
|||
tristate "Cypress mouse and barcode readers"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for cypress mouse and barcode readers.
|
||||
|
||||
config HID_DRAGONRISE
|
||||
tristate "DragonRise Inc. game controller"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have DragonRise Inc. game controllers.
|
||||
These might be branded as:
|
||||
- Tesun USB-703
|
||||
|
|
@ -305,7 +305,7 @@ config DRAGONRISE_FF
|
|||
bool "DragonRise Inc. force feedback"
|
||||
depends on HID_DRAGONRISE
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to enable force feedback support for DragonRise Inc.
|
||||
game controllers.
|
||||
|
||||
|
|
@ -313,7 +313,7 @@ config HID_EMS_FF
|
|||
tristate "EMS Production Inc. force feedback support"
|
||||
depends on HID
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to enable force feedback support for devices by
|
||||
EMS Production Ltd.
|
||||
Currently the following devices are known to be supported:
|
||||
|
|
@ -322,7 +322,7 @@ config HID_EMS_FF
|
|||
config HID_ELAN
|
||||
tristate "ELAN USB Touchpad Support"
|
||||
depends on LEDS_CLASS && USB_HID
|
||||
---help---
|
||||
help
|
||||
Say Y to enable support for the USB ELAN touchpad
|
||||
Currently the following devices are known to be supported:
|
||||
- HP Pavilion X2 10-p0XX.
|
||||
|
|
@ -330,7 +330,7 @@ config HID_ELAN
|
|||
config HID_ELECOM
|
||||
tristate "ELECOM HID devices"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for ELECOM devices:
|
||||
- BM084 Bluetooth Mouse
|
||||
- EX-G Trackballs (M-XT3DRBK, M-XT3URBK)
|
||||
|
|
@ -340,7 +340,7 @@ config HID_ELECOM
|
|||
config HID_ELO
|
||||
tristate "ELO USB 4000/4500 touchscreen"
|
||||
depends on USB_HID
|
||||
---help---
|
||||
help
|
||||
Support for the ELO USB 4000/4500 touchscreens. Note that this is for
|
||||
different devices than those handled by CONFIG_TOUCHSCREEN_USB_ELO.
|
||||
|
||||
|
|
@ -348,19 +348,19 @@ config HID_EZKEY
|
|||
tristate "Ezkey BTC 8193 keyboard"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for Ezkey BTC 8193 keyboard.
|
||||
|
||||
config HID_GEMBIRD
|
||||
tristate "Gembird Joypad"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Gembird JPD-DualForce 2.
|
||||
|
||||
config HID_GFRM
|
||||
tristate "Google Fiber TV Box remote control support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Google Fiber TV Box remote controls
|
||||
|
||||
config HID_GLORIOUS
|
||||
|
|
@ -373,7 +373,7 @@ config HID_GLORIOUS
|
|||
config HID_HOLTEK
|
||||
tristate "Holtek HID devices"
|
||||
depends on USB_HID
|
||||
---help---
|
||||
help
|
||||
Support for Holtek based devices:
|
||||
- Holtek On Line Grip based game controller
|
||||
- Trust GXT 18 Gaming Keyboard
|
||||
|
|
@ -387,20 +387,20 @@ config HOLTEK_FF
|
|||
bool "Holtek On Line Grip force feedback support"
|
||||
depends on HID_HOLTEK
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a Holtek On Line Grip based game controller
|
||||
and want to have force feedback support for it.
|
||||
|
||||
config HID_GOOGLE_HAMMER
|
||||
tristate "Google Hammer Keyboard"
|
||||
depends on USB_HID && LEDS_CLASS && CROS_EC
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a Google Hammer device.
|
||||
|
||||
config HID_GT683R
|
||||
tristate "MSI GT68xR LED support"
|
||||
depends on LEDS_CLASS && USB_HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to enable support for the three MSI GT68xR LEDs
|
||||
|
||||
This driver support following modes:
|
||||
|
|
@ -414,7 +414,7 @@ config HID_GT683R
|
|||
config HID_KEYTOUCH
|
||||
tristate "Keytouch HID devices"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Keytouch HID devices not fully compliant with
|
||||
the specification. Currently supported:
|
||||
- Keytouch IEC 60945
|
||||
|
|
@ -422,7 +422,7 @@ config HID_KEYTOUCH
|
|||
config HID_KYE
|
||||
tristate "KYE/Genius devices"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for KYE/Genius devices not fully compliant with HID standard:
|
||||
- Ergo Mouse
|
||||
- EasyPen i405X tablet
|
||||
|
|
@ -432,13 +432,13 @@ config HID_KYE
|
|||
config HID_UCLOGIC
|
||||
tristate "UC-Logic"
|
||||
depends on USB_HID
|
||||
---help---
|
||||
help
|
||||
Support for UC-Logic and Huion tablets.
|
||||
|
||||
config HID_WALTOP
|
||||
tristate "Waltop"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Waltop tablets.
|
||||
|
||||
config HID_VIEWSONIC
|
||||
|
|
@ -450,13 +450,13 @@ config HID_VIEWSONIC
|
|||
config HID_GYRATION
|
||||
tristate "Gyration remote control"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Gyration remote control.
|
||||
|
||||
config HID_ICADE
|
||||
tristate "ION iCade arcade controller"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for the ION iCade arcade controller to work as a joystick.
|
||||
|
||||
To compile this driver as a module, choose M here: the
|
||||
|
|
@ -466,13 +466,13 @@ config HID_ITE
|
|||
tristate "ITE devices"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for ITE devices not fully compliant with HID standard.
|
||||
|
||||
config HID_JABRA
|
||||
tristate "Jabra USB HID Driver"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Jabra USB HID devices.
|
||||
|
||||
Prevents mapping of vendor defined HID usages to input events. Without
|
||||
|
|
@ -483,27 +483,27 @@ config HID_JABRA
|
|||
config HID_TWINHAN
|
||||
tristate "Twinhan IR remote control"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Twinhan IR remote control.
|
||||
|
||||
config HID_KENSINGTON
|
||||
tristate "Kensington Slimblade Trackball"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for Kensington Slimblade Trackball.
|
||||
|
||||
config HID_LCPOWER
|
||||
tristate "LC-Power"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for LC-Power RC1000MCE RF remote control.
|
||||
|
||||
config HID_LED
|
||||
tristate "Simple RGB LED support"
|
||||
depends on HID
|
||||
depends on LEDS_CLASS
|
||||
---help---
|
||||
help
|
||||
Support for simple RGB LED devices. Currently supported are:
|
||||
- Riso Kagaku Webmail Notifier
|
||||
- Dream Cheeky Webmail Notifier and Friends Alert
|
||||
|
|
@ -519,7 +519,7 @@ config HID_LENOVO
|
|||
depends on HID
|
||||
select NEW_LEDS
|
||||
select LEDS_CLASS
|
||||
---help---
|
||||
help
|
||||
Support for IBM/Lenovo devices that are not fully compliant with HID standard.
|
||||
|
||||
Say Y if you want support for horizontal scrolling of the IBM/Lenovo
|
||||
|
|
@ -535,7 +535,7 @@ config HID_LOGITECH
|
|||
depends on HID
|
||||
depends on LEDS_CLASS
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for Logitech devices that are not fully compliant with HID standard.
|
||||
|
||||
config HID_LOGITECH_DJ
|
||||
|
|
@ -544,7 +544,7 @@ config HID_LOGITECH_DJ
|
|||
depends on HIDRAW
|
||||
depends on HID_LOGITECH
|
||||
select HID_LOGITECH_HIDPP
|
||||
---help---
|
||||
help
|
||||
Say Y if you want support for Logitech receivers and devices.
|
||||
Logitech receivers are capable of pairing multiple Logitech compliant
|
||||
devices to the same receiver. Without this driver it will be handled by
|
||||
|
|
@ -555,7 +555,7 @@ config HID_LOGITECH_HIDPP
|
|||
tristate "Logitech HID++ devices support"
|
||||
depends on HID_LOGITECH
|
||||
select POWER_SUPPLY
|
||||
---help---
|
||||
help
|
||||
Support for Logitech devices relyingon the HID++ Logitech specification
|
||||
|
||||
Say Y if you want support for Logitech devices relying on the HID++
|
||||
|
|
@ -621,7 +621,7 @@ config LOGIWHEELS_FF
|
|||
config HID_MAGICMOUSE
|
||||
tristate "Apple Magic Mouse/Trackpad multi-touch support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for the Apple Magic Mouse/Trackpad multi-touch.
|
||||
|
||||
Say Y here if you want support for the multi-touch features of the
|
||||
|
|
@ -630,7 +630,7 @@ config HID_MAGICMOUSE
|
|||
config HID_MALTRON
|
||||
tristate "Maltron L90 keyboard"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Adds support for the volume up, volume down, mute, and play/pause buttons
|
||||
of the Maltron L90 keyboard.
|
||||
|
||||
|
|
@ -638,7 +638,7 @@ config HID_MAYFLASH
|
|||
tristate "Mayflash game controller adapter force feedback"
|
||||
depends on HID
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have HJZ Mayflash PS3 game controller adapters
|
||||
and want to enable force feedback support.
|
||||
|
||||
|
|
@ -646,7 +646,7 @@ config HID_REDRAGON
|
|||
tristate "Redragon keyboards"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for Redragon keyboards that need fix-ups to work properly.
|
||||
|
||||
config HID_MICROSOFT
|
||||
|
|
@ -654,20 +654,20 @@ config HID_MICROSOFT
|
|||
depends on HID
|
||||
default !EXPERT
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Support for Microsoft devices that are not fully compliant with HID standard.
|
||||
|
||||
config HID_MONTEREY
|
||||
tristate "Monterey Genius KB29E keyboard"
|
||||
depends on HID
|
||||
default !EXPERT
|
||||
---help---
|
||||
help
|
||||
Support for Monterey Genius KB29E.
|
||||
|
||||
config HID_MULTITOUCH
|
||||
tristate "HID Multitouch panels"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Generic support for HID multitouch panels.
|
||||
|
||||
Say Y here if you have one of the following devices:
|
||||
|
|
@ -712,20 +712,20 @@ config HID_MULTITOUCH
|
|||
|
||||
config HID_NTI
|
||||
tristate "NTI keyboard adapters"
|
||||
---help---
|
||||
help
|
||||
Support for the "extra" Sun keyboard keys on keyboards attached
|
||||
through Network Technologies USB-SUN keyboard adapters.
|
||||
|
||||
config HID_NTRIG
|
||||
tristate "N-Trig touch screen"
|
||||
depends on USB_HID
|
||||
---help---
|
||||
help
|
||||
Support for N-Trig touch screen.
|
||||
|
||||
config HID_ORTEK
|
||||
tristate "Ortek PKB-1700/WKB-2000/Skycable wireless keyboard and mouse trackpad"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
There are certain devices which have LogicalMaximum wrong in the keyboard
|
||||
usage page of their report descriptor. The most prevailing ones so far
|
||||
are manufactured by Ortek, thus the name of the driver. Currently
|
||||
|
|
@ -738,7 +738,7 @@ config HID_ORTEK
|
|||
config HID_PANTHERLORD
|
||||
tristate "Pantherlord/GreenAsia game controller"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a PantherLord/GreenAsia based game controller
|
||||
or adapter.
|
||||
|
||||
|
|
@ -746,14 +746,14 @@ config PANTHERLORD_FF
|
|||
bool "Pantherlord force feedback support"
|
||||
depends on HID_PANTHERLORD
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a PantherLord/GreenAsia based game controller
|
||||
or adapter and want to enable force feedback support for it.
|
||||
|
||||
config HID_PENMOUNT
|
||||
tristate "Penmount touch device"
|
||||
depends on USB_HID
|
||||
---help---
|
||||
help
|
||||
This selects a driver for the PenMount 6000 touch controller.
|
||||
|
||||
The driver works around a problem in the report descript allowing
|
||||
|
|
@ -764,13 +764,13 @@ config HID_PENMOUNT
|
|||
config HID_PETALYNX
|
||||
tristate "Petalynx Maxter remote control"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Petalynx Maxter remote control.
|
||||
|
||||
config HID_PICOLCD
|
||||
tristate "PicoLCD (graphic version)"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
This provides support for Minibox PicoLCD devices, currently
|
||||
only the graphical ones are supported.
|
||||
|
||||
|
|
@ -796,7 +796,7 @@ config HID_PICOLCD_FB
|
|||
select FB_SYS_COPYAREA
|
||||
select FB_SYS_IMAGEBLIT
|
||||
select FB_SYS_FOPS
|
||||
---help---
|
||||
help
|
||||
Provide access to PicoLCD's 256x64 monochrome display via a
|
||||
framebuffer device.
|
||||
|
||||
|
|
@ -805,7 +805,7 @@ config HID_PICOLCD_BACKLIGHT
|
|||
default !EXPERT
|
||||
depends on HID_PICOLCD
|
||||
depends on HID_PICOLCD=BACKLIGHT_CLASS_DEVICE || BACKLIGHT_CLASS_DEVICE=y
|
||||
---help---
|
||||
help
|
||||
Provide access to PicoLCD's backlight control via backlight
|
||||
class.
|
||||
|
||||
|
|
@ -814,7 +814,7 @@ config HID_PICOLCD_LCD
|
|||
default !EXPERT
|
||||
depends on HID_PICOLCD
|
||||
depends on HID_PICOLCD=LCD_CLASS_DEVICE || LCD_CLASS_DEVICE=y
|
||||
---help---
|
||||
help
|
||||
Provide access to PicoLCD's LCD contrast via lcd class.
|
||||
|
||||
config HID_PICOLCD_LEDS
|
||||
|
|
@ -822,7 +822,7 @@ config HID_PICOLCD_LEDS
|
|||
default !EXPERT
|
||||
depends on HID_PICOLCD
|
||||
depends on HID_PICOLCD=LEDS_CLASS || LEDS_CLASS=y
|
||||
---help---
|
||||
help
|
||||
Provide access to PicoLCD's GPO pins via leds class.
|
||||
|
||||
config HID_PICOLCD_CIR
|
||||
|
|
@ -830,13 +830,13 @@ config HID_PICOLCD_CIR
|
|||
default !EXPERT
|
||||
depends on HID_PICOLCD
|
||||
depends on HID_PICOLCD=RC_CORE || RC_CORE=y
|
||||
---help---
|
||||
help
|
||||
Provide access to PicoLCD's CIR interface via remote control (LIRC).
|
||||
|
||||
config HID_PLANTRONICS
|
||||
tristate "Plantronics USB HID Driver"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Provides HID support for Plantronics USB audio devices.
|
||||
Correctly maps vendor unique volume up/down HID usages to
|
||||
KEY_VOLUMEUP and KEY_VOLUMEDOWN events and prevents core mapping
|
||||
|
|
@ -847,21 +847,21 @@ config HID_PLANTRONICS
|
|||
config HID_PRIMAX
|
||||
tristate "Primax non-fully HID-compliant devices"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Primax devices that are not fully compliant with the
|
||||
HID standard.
|
||||
|
||||
config HID_RETRODE
|
||||
tristate "Retrode 2 USB adapter for vintage video games"
|
||||
depends on USB_HID
|
||||
---help---
|
||||
help
|
||||
Support for
|
||||
* Retrode 2 cartridge and controller adapter
|
||||
|
||||
config HID_ROCCAT
|
||||
tristate "Roccat device support"
|
||||
depends on USB_HID
|
||||
---help---
|
||||
help
|
||||
Support for Roccat devices.
|
||||
Say Y here if you have a Roccat mouse or keyboard and want
|
||||
support for its special functionalities.
|
||||
|
|
@ -869,7 +869,7 @@ config HID_ROCCAT
|
|||
config HID_SAITEK
|
||||
tristate "Saitek (Mad Catz) non-fully HID-compliant devices"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Saitek devices that are not fully compliant with the
|
||||
HID standard.
|
||||
|
||||
|
|
@ -881,7 +881,7 @@ config HID_SAITEK
|
|||
config HID_SAMSUNG
|
||||
tristate "Samsung InfraRed remote control or keyboards"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Samsung InfraRed remote control or keyboards.
|
||||
|
||||
config HID_SONY
|
||||
|
|
@ -890,7 +890,7 @@ config HID_SONY
|
|||
depends on NEW_LEDS
|
||||
depends on LEDS_CLASS
|
||||
select POWER_SUPPLY
|
||||
---help---
|
||||
help
|
||||
Support for
|
||||
|
||||
* Sony PS3 6-axis controllers
|
||||
|
|
@ -903,21 +903,21 @@ config SONY_FF
|
|||
bool "Sony PS2/3/4 accessories force feedback support"
|
||||
depends on HID_SONY
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a Sony PS2/3/4 accessory and want to enable
|
||||
force feedback support for it.
|
||||
|
||||
config HID_SPEEDLINK
|
||||
tristate "Speedlink VAD Cezanne mouse support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Speedlink Vicious and Divine Cezanne mouse.
|
||||
|
||||
config HID_STEAM
|
||||
tristate "Steam Controller support"
|
||||
depends on HID
|
||||
select POWER_SUPPLY
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a Steam Controller if you want to use it
|
||||
without running the Steam Client. It supports both the wired and
|
||||
the wireless adaptor.
|
||||
|
|
@ -925,13 +925,13 @@ config HID_STEAM
|
|||
config HID_STEELSERIES
|
||||
tristate "Steelseries SRW-S1 steering wheel support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Steelseries SRW-S1 steering wheel
|
||||
|
||||
config HID_SUNPLUS
|
||||
tristate "Sunplus wireless desktop"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Sunplus wireless desktop.
|
||||
|
||||
config HID_RMI
|
||||
|
|
@ -942,7 +942,7 @@ config HID_RMI
|
|||
select RMI4_F11
|
||||
select RMI4_F12
|
||||
select RMI4_F30
|
||||
---help---
|
||||
help
|
||||
Support for Synaptics RMI4 touchpads.
|
||||
Say Y here if you have a Synaptics RMI4 touchpads over i2c-hid or usbhid
|
||||
and want support for its special functionalities.
|
||||
|
|
@ -950,7 +950,7 @@ config HID_RMI
|
|||
config HID_GREENASIA
|
||||
tristate "GreenAsia (Product ID 0x12) game controller support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a GreenAsia (Product ID 0x12) based game
|
||||
controller or adapter.
|
||||
|
||||
|
|
@ -958,7 +958,7 @@ config GREENASIA_FF
|
|||
bool "GreenAsia (Product ID 0x12) force feedback support"
|
||||
depends on HID_GREENASIA
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a GreenAsia (Product ID 0x12) based game controller
|
||||
(like MANTA Warrior MM816 and SpeedLink Strike2 SL-6635) or adapter
|
||||
and want to enable force feedback support for it.
|
||||
|
|
@ -966,13 +966,13 @@ config GREENASIA_FF
|
|||
config HID_HYPERV_MOUSE
|
||||
tristate "Microsoft Hyper-V mouse driver"
|
||||
depends on HYPERV
|
||||
---help---
|
||||
help
|
||||
Select this option to enable the Hyper-V mouse driver.
|
||||
|
||||
config HID_SMARTJOYPLUS
|
||||
tristate "SmartJoy PLUS PS2/USB adapter support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for SmartJoy PLUS PS2/USB adapter, Super Dual Box,
|
||||
Super Joy Box 3 Pro, Super Dual Box Pro, and Super Joy Box 5 Pro.
|
||||
|
||||
|
|
@ -983,20 +983,20 @@ config SMARTJOYPLUS_FF
|
|||
bool "SmartJoy PLUS PS2/USB adapter force feedback support"
|
||||
depends on HID_SMARTJOYPLUS
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a SmartJoy PLUS PS2/USB adapter and want to
|
||||
enable force feedback support for it.
|
||||
|
||||
config HID_TIVO
|
||||
tristate "TiVo Slide Bluetooth remote control support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y if you have a TiVo Slide Bluetooth remote control.
|
||||
|
||||
config HID_TOPSEED
|
||||
tristate "TopSeed Cyberlink, BTC Emprex, Conceptronic remote control support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y if you have a TopSeed Cyberlink or BTC Emprex or Conceptronic
|
||||
CLLRCMCE remote control.
|
||||
|
||||
|
|
@ -1005,7 +1005,7 @@ config HID_THINGM
|
|||
depends on HID
|
||||
depends on LEDS_CLASS
|
||||
select HID_LED
|
||||
---help---
|
||||
help
|
||||
Support for the ThingM blink(1) USB RGB LED. This driver has been
|
||||
merged into the generic hid led driver. Config symbol HID_THINGM
|
||||
just selects HID_LED and will be removed soon.
|
||||
|
|
@ -1013,7 +1013,7 @@ config HID_THINGM
|
|||
config HID_THRUSTMASTER
|
||||
tristate "ThrustMaster devices support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
|
||||
a THRUSTMASTER Ferrari GT Rumble Wheel.
|
||||
|
||||
|
|
@ -1021,7 +1021,7 @@ config THRUSTMASTER_FF
|
|||
bool "ThrustMaster devices force feedback support"
|
||||
depends on HID_THRUSTMASTER
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or 3,
|
||||
a THRUSTMASTER Dual Trigger 3-in-1 or a THRUSTMASTER Ferrari GT
|
||||
Rumble Force or Force Feedback Wheel.
|
||||
|
|
@ -1029,7 +1029,7 @@ config THRUSTMASTER_FF
|
|||
config HID_UDRAW_PS3
|
||||
tristate "THQ PS3 uDraw tablet"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to use the THQ uDraw gaming tablet for
|
||||
the PS3.
|
||||
|
||||
|
|
@ -1069,7 +1069,7 @@ config HID_WIIMOTE
|
|||
depends on LEDS_CLASS
|
||||
select POWER_SUPPLY
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Support for Nintendo Wii and Wii U Bluetooth peripherals. Supported
|
||||
devices are the Wii Remote and its extension devices, but also devices
|
||||
based on the Wii Remote like the Wii U Pro Controller or the
|
||||
|
|
@ -1091,7 +1091,7 @@ config HID_WIIMOTE
|
|||
config HID_XINMO
|
||||
tristate "Xin-Mo non-fully compliant devices"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Xin-Mo devices that are not fully compliant with the HID
|
||||
standard. Currently only supports the Xin-Mo Dual Arcade. Say Y here
|
||||
if you have a Xin-Mo Dual Arcade controller.
|
||||
|
|
@ -1099,21 +1099,21 @@ config HID_XINMO
|
|||
config HID_ZEROPLUS
|
||||
tristate "Zeroplus based game controller support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a Zeroplus based game controller.
|
||||
|
||||
config ZEROPLUS_FF
|
||||
bool "Zeroplus based game controller force feedback support"
|
||||
depends on HID_ZEROPLUS
|
||||
select INPUT_FF_MEMLESS
|
||||
---help---
|
||||
help
|
||||
Say Y here if you have a Zeroplus based game controller and want
|
||||
to have force feedback support for it.
|
||||
|
||||
config HID_ZYDACRON
|
||||
tristate "Zydacron remote control support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Zydacron remote control.
|
||||
|
||||
config HID_SENSOR_HUB
|
||||
|
|
@ -1121,7 +1121,7 @@ config HID_SENSOR_HUB
|
|||
depends on HID && HAS_IOMEM
|
||||
select MFD_CORE
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
Support for HID Sensor framework. This creates a MFD instance
|
||||
for a sensor hub and identifies all the sensors connected to it.
|
||||
Each sensor is registered as a MFD cell, so that sensor specific
|
||||
|
|
@ -1134,7 +1134,7 @@ config HID_SENSOR_CUSTOM_SENSOR
|
|||
tristate "HID Sensors hub custom sensor support"
|
||||
depends on HID_SENSOR_HUB
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
HID Sensor hub specification allows definition of some custom and
|
||||
generic sensors. Unlike other HID sensors, they can't be exported
|
||||
via Linux IIO because of custom fields. This is up to the manufacturer
|
||||
|
|
@ -1148,7 +1148,7 @@ config HID_SENSOR_CUSTOM_SENSOR
|
|||
config HID_ALPS
|
||||
tristate "Alps HID device support"
|
||||
depends on HID
|
||||
---help---
|
||||
help
|
||||
Support for Alps I2C HID touchpads and StickPointer.
|
||||
Say Y here if you have a Alps touchpads over i2c-hid or usbhid
|
||||
and want support for its special functionalities.
|
||||
|
|
@ -1157,7 +1157,7 @@ config HID_MCP2221
|
|||
tristate "Microchip MCP2221 HID USB-to-I2C/SMbus host support"
|
||||
depends on USB_HID && I2C
|
||||
depends on GPIOLIB
|
||||
---help---
|
||||
help
|
||||
Provides I2C and SMBUS host adapter functionality over USB-HID
|
||||
through MCP2221 device.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ config I2C_HID
|
|||
default n
|
||||
depends on I2C && INPUT
|
||||
select HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you use a keyboard, a touchpad, a touchscreen, or any
|
||||
other HID based devices which is connected to your computer via I2C.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ config USB_HID
|
|||
default y
|
||||
depends on USB && INPUT
|
||||
select HID
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to connect USB keyboards,
|
||||
mice, joysticks, graphic tablets, or any other HID based devices
|
||||
to your computer via USB, as well as Uninterruptible Power Supply
|
||||
|
|
@ -51,7 +51,7 @@ menu "USB HID Boot Protocol drivers"
|
|||
config USB_KBD
|
||||
tristate "USB HIDBP Keyboard (simple Boot) support"
|
||||
depends on USB && INPUT
|
||||
---help---
|
||||
help
|
||||
Say Y here only if you are absolutely sure that you don't want
|
||||
to use the generic HID driver for your USB keyboard and prefer
|
||||
to use the keyboard in its limited Boot Protocol mode instead.
|
||||
|
|
@ -67,7 +67,7 @@ config USB_KBD
|
|||
config USB_MOUSE
|
||||
tristate "USB HIDBP Mouse (simple Boot) support"
|
||||
depends on USB && INPUT
|
||||
---help---
|
||||
help
|
||||
Say Y here only if you are absolutely sure that you don't want
|
||||
to use the generic HID driver for your USB mouse and prefer
|
||||
to use the mouse in its limited Boot Protocol mode instead.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
#
|
||||
menuconfig HSI
|
||||
tristate "HSI support"
|
||||
---help---
|
||||
help
|
||||
The "High speed synchronous Serial Interface" is
|
||||
synchronous serial interface used mainly to connect
|
||||
application engines and cellular modems.
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ config SSI_PROTOCOL
|
|||
config HSI_CHAR
|
||||
tristate "HSI/SSI character driver"
|
||||
depends on HSI
|
||||
---help---
|
||||
help
|
||||
If you say Y here, you will enable the HSI/SSI character driver.
|
||||
This driver provides a simple character device interface for
|
||||
serial communication with the cellular modem over HSI/SSI bus.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ config OMAP_SSI
|
|||
tristate "OMAP SSI hardware driver"
|
||||
depends on HSI && OF && ARM && COMMON_CLK
|
||||
depends on ARCH_OMAP3 || COMPILE_TEST
|
||||
---help---
|
||||
help
|
||||
SSI is a legacy version of HSI. It is usually used to connect
|
||||
an application engine with a cellular modem.
|
||||
If you say Y here, you will enable the OMAP SSI hardware driver.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ config I2C
|
|||
tristate "I2C support"
|
||||
select RT_MUTEXES
|
||||
select IRQ_DOMAIN
|
||||
---help---
|
||||
help
|
||||
I2C (pronounce: I-squared-C) is a slow serial bus protocol used in
|
||||
many micro controller applications and developed by Philips. SMBus,
|
||||
or System Management Bus is a subset of the I2C protocol. More
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ menuconfig IDE
|
|||
depends on HAVE_IDE
|
||||
depends on BLOCK
|
||||
select BLK_SCSI_REQUEST
|
||||
---help---
|
||||
help
|
||||
If you say Y here, your kernel will be able to manage ATA/(E)IDE and
|
||||
ATAPI units. The most common cases are IDE hard drives and ATAPI
|
||||
CD-ROM drives.
|
||||
|
|
@ -49,7 +49,7 @@ config IDE_LEGACY
|
|||
config BLK_DEV_IDE_SATA
|
||||
bool "Support for SATA (deprecated; conflicts with libata SATA driver)"
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
There are two drivers for Serial ATA controllers.
|
||||
|
||||
The main driver, "libata", uses the SCSI subsystem
|
||||
|
|
@ -121,7 +121,7 @@ config BLK_DEV_IDECD
|
|||
depends on BLK_DEV
|
||||
select IDE_ATAPI
|
||||
select CDROM
|
||||
---help---
|
||||
help
|
||||
If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
|
||||
a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
|
||||
SCSI protocol. Most new CD-ROM drives use ATAPI, including the
|
||||
|
|
@ -172,7 +172,7 @@ config BLK_DEV_IDETAPE
|
|||
config BLK_DEV_IDEACPI
|
||||
bool "IDE ACPI support"
|
||||
depends on ACPI
|
||||
---help---
|
||||
help
|
||||
Implement ACPI support for generic IDE devices. On modern
|
||||
machines ACPI support is required to properly handle ACPI S3 states.
|
||||
|
||||
|
|
@ -232,7 +232,7 @@ config BLK_DEV_CMD640
|
|||
tristate "CMD640 chipset bugfix/support"
|
||||
depends on X86
|
||||
select IDE_TIMINGS
|
||||
---help---
|
||||
help
|
||||
The CMD-Technologies CMD640 IDE chip is used on many common 486 and
|
||||
Pentium motherboards, usually in combination with a "Neptune" or
|
||||
"SiS" chipset. Unfortunately, it has a number of rather nasty
|
||||
|
|
|
|||
|
|
@ -325,7 +325,7 @@ config MAX5821
|
|||
config MCP4725
|
||||
tristate "MCP4725/6 DAC driver"
|
||||
depends on I2C
|
||||
---help---
|
||||
help
|
||||
Say Y here if you want to build a driver for the Microchip
|
||||
MCP 4725/6 12-bit digital-to-analog converter (DAC) with I2C
|
||||
interface.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ menuconfig INFINIBAND
|
|||
depends on !ALPHA
|
||||
select IRQ_POLL
|
||||
select DIMLIB
|
||||
---help---
|
||||
help
|
||||
Core support for InfiniBand (IB). Make sure to also select
|
||||
any protocols you wish to use as well as drivers for your
|
||||
InfiniBand hardware.
|
||||
|
|
@ -18,7 +18,7 @@ if INFINIBAND
|
|||
config INFINIBAND_USER_MAD
|
||||
tristate "InfiniBand userspace MAD support"
|
||||
depends on INFINIBAND
|
||||
---help---
|
||||
help
|
||||
Userspace InfiniBand Management Datagram (MAD) support. This
|
||||
is the kernel side of the userspace MAD support, which allows
|
||||
userspace processes to send and receive MADs. You will also
|
||||
|
|
@ -28,7 +28,7 @@ config INFINIBAND_USER_MAD
|
|||
config INFINIBAND_USER_ACCESS
|
||||
tristate "InfiniBand userspace access (verbs and CM)"
|
||||
depends on MMU
|
||||
---help---
|
||||
help
|
||||
Userspace InfiniBand access support. This enables the
|
||||
kernel side of userspace verbs and the userspace
|
||||
communication manager (CM). This allows userspace processes
|
||||
|
|
@ -40,7 +40,7 @@ config INFINIBAND_USER_ACCESS
|
|||
config INFINIBAND_EXP_LEGACY_VERBS_NEW_UAPI
|
||||
bool "Allow experimental legacy verbs in new ioctl uAPI (EXPERIMENTAL)"
|
||||
depends on INFINIBAND_USER_ACCESS
|
||||
---help---
|
||||
help
|
||||
IOCTL based uAPI support for Infiniband is enabled by default for
|
||||
new verbs only. This allows userspace to invoke the IOCTL based uAPI
|
||||
for current legacy verbs too.
|
||||
|
|
@ -57,7 +57,7 @@ config INFINIBAND_ON_DEMAND_PAGING
|
|||
select MMU_NOTIFIER
|
||||
select INTERVAL_TREE
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
On demand paging support for the InfiniBand subsystem.
|
||||
Together with driver support this allows registration of
|
||||
memory regions without pinning their pages, fetching the
|
||||
|
|
@ -67,7 +67,7 @@ config INFINIBAND_ADDR_TRANS
|
|||
bool "RDMA/CM"
|
||||
depends on INFINIBAND
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Support for RDMA communication manager (CM).
|
||||
This allows for a generic connection abstraction over RDMA.
|
||||
|
||||
|
|
@ -75,7 +75,7 @@ config INFINIBAND_ADDR_TRANS_CONFIGFS
|
|||
bool
|
||||
depends on INFINIBAND_ADDR_TRANS && CONFIGFS_FS && !(INFINIBAND=y && CONFIGFS_FS=m)
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
ConfigFS support for RDMA communication manager (CM).
|
||||
This allows the user to config the default GID type that the CM
|
||||
uses for each device, when initiaing new connections.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ config INFINIBAND_BNXT_RE
|
|||
depends on ETHERNET && NETDEVICES && PCI && INET && DCB
|
||||
select NET_VENDOR_BROADCOM
|
||||
select BNXT
|
||||
---help---
|
||||
help
|
||||
This driver supports Broadcom NetXtreme-E 10/25/40/50 gigabit
|
||||
RoCE HCAs. To compile this driver as a module, choose M here:
|
||||
the module will be called bnxt_re.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ config INFINIBAND_CXGB4
|
|||
depends on INFINIBAND_ADDR_TRANS
|
||||
select CHELSIO_LIB
|
||||
select GENERIC_ALLOCATOR
|
||||
---help---
|
||||
help
|
||||
This is an iWARP/RDMA driver for the Chelsio T4 and T5
|
||||
1GbE, 10GbE adapters and T5 40GbE adapter.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,19 +5,19 @@ config INFINIBAND_HFI1
|
|||
select MMU_NOTIFIER
|
||||
select CRC32
|
||||
select I2C_ALGOBIT
|
||||
---help---
|
||||
help
|
||||
This is a low-level driver for Intel OPA Gen1 adapter.
|
||||
config HFI1_DEBUG_SDMA_ORDER
|
||||
bool "HFI1 SDMA Order debug"
|
||||
depends on INFINIBAND_HFI1
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
This is a debug flag to test for out of order
|
||||
sdma completions for unit testing
|
||||
config SDMA_VERBOSITY
|
||||
bool "Config SDMA Verbosity"
|
||||
depends on INFINIBAND_HFI1
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
This is a configuration flag to enable verbose
|
||||
SDMA debug
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ config INFINIBAND_HNS
|
|||
depends on NET_VENDOR_HISILICON
|
||||
depends on ARM64 || (COMPILE_TEST && 64BIT)
|
||||
depends on (HNS_DSAF && HNS_ENET) || HNS3
|
||||
---help---
|
||||
help
|
||||
This is a RoCE/RDMA driver for the Hisilicon RoCE engine. The engine
|
||||
is used in Hisilicon Hip06 and more further ICT SoC based on
|
||||
platform device.
|
||||
|
|
@ -15,7 +15,7 @@ config INFINIBAND_HNS_HIP06
|
|||
bool "Hisilicon Hip06 Family RoCE support"
|
||||
depends on INFINIBAND_HNS && HNS && HNS_DSAF && HNS_ENET
|
||||
depends on INFINIBAND_HNS=m || (HNS_DSAF=y && HNS_ENET=y)
|
||||
---help---
|
||||
help
|
||||
RoCE driver support for Hisilicon RoCE engine in Hisilicon Hip06 and
|
||||
Hip07 SoC. These RoCE engines are platform devices.
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ config INFINIBAND_HNS_HIP08
|
|||
bool "Hisilicon Hip08 Family RoCE support"
|
||||
depends on INFINIBAND_HNS && PCI && HNS3
|
||||
depends on INFINIBAND_HNS=m || HNS3=y
|
||||
---help---
|
||||
help
|
||||
RoCE driver support for Hisilicon RoCE engine in Hisilicon Hip08 SoC.
|
||||
The RoCE engine is a PCI device.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,5 +5,5 @@ config INFINIBAND_I40IW
|
|||
depends on IPV6 || !IPV6
|
||||
depends on PCI
|
||||
select GENERIC_ALLOCATOR
|
||||
---help---
|
||||
help
|
||||
Intel(R) Ethernet X722 iWARP Driver
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ config MLX4_INFINIBAND
|
|||
depends on NETDEVICES && ETHERNET && PCI && INET
|
||||
select NET_VENDOR_MELLANOX
|
||||
select MLX4_CORE
|
||||
---help---
|
||||
help
|
||||
This driver provides low-level InfiniBand support for
|
||||
Mellanox ConnectX PCI Express host channel adapters (HCAs).
|
||||
This is required to use InfiniBand protocols such as
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
config MLX5_INFINIBAND
|
||||
tristate "Mellanox 5th generation network adapters (ConnectX series) support"
|
||||
depends on NETDEVICES && ETHERNET && PCI && MLX5_CORE
|
||||
---help---
|
||||
help
|
||||
This driver provides low-level InfiniBand support for
|
||||
Mellanox Connect-IB PCI Express host channel adapters (HCAs).
|
||||
This is required to use InfiniBand protocols such as
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
config INFINIBAND_MTHCA
|
||||
tristate "Mellanox HCA support"
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This is a low-level driver for Mellanox InfiniHost host
|
||||
channel adapters (HCAs), including the MT23108 PCI-X HCA
|
||||
("Tavor") and the MT25208 PCI Express HCA ("Arbel").
|
||||
|
|
@ -11,7 +11,7 @@ config INFINIBAND_MTHCA_DEBUG
|
|||
bool "Verbose debugging output" if EXPERT
|
||||
depends on INFINIBAND_MTHCA
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
This option causes debugging code to be compiled into the
|
||||
mthca driver. The output can be turned on via the
|
||||
debug_level module parameter (which can also be set after
|
||||
|
|
|
|||
|
|
@ -4,6 +4,6 @@ config INFINIBAND_OCRDMA
|
|||
depends on ETHERNET && NETDEVICES && PCI && INET && (IPV6 || IPV6=n)
|
||||
select NET_VENDOR_EMULEX
|
||||
select BE2NET
|
||||
---help---
|
||||
help
|
||||
This driver provides low-level InfiniBand over Ethernet
|
||||
support for Emulex One Connect host channel adapters (HCAs).
|
||||
|
|
|
|||
|
|
@ -6,6 +6,6 @@ config INFINIBAND_QEDR
|
|||
select QED_LL2
|
||||
select QED_OOO
|
||||
select QED_RDMA
|
||||
---help---
|
||||
help
|
||||
This driver provides low-level InfiniBand over Ethernet
|
||||
support for QLogic QED host channel adapters (HCAs).
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ config INFINIBAND_QIB
|
|||
tristate "Intel PCIe HCA support"
|
||||
depends on 64BIT && INFINIBAND_RDMAVT
|
||||
depends on PCI
|
||||
---help---
|
||||
help
|
||||
This is a low-level driver for Intel PCIe QLE InfiniBand host
|
||||
channel adapters. This driver does not support the Intel
|
||||
HyperTransport card (model QHT7140).
|
||||
|
|
@ -12,6 +12,6 @@ config INFINIBAND_QIB_DCA
|
|||
bool "QIB DCA support"
|
||||
depends on INFINIBAND_QIB && DCA && SMP && !(INFINIBAND_QIB=y && DCA=m)
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
Setting this enables DCA support on some Intel chip sets
|
||||
with the iba7322 HCA.
|
||||
|
|
|
|||
|
|
@ -6,6 +6,6 @@ config INFINIBAND_USNIC
|
|||
select ENIC
|
||||
select NET_VENDOR_CISCO
|
||||
select PCI_IOV
|
||||
---help---
|
||||
help
|
||||
This is a low-level driver for Cisco's Virtual Interface
|
||||
Cards (VICs), including the VIC 1240 and 1280 cards.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
config INFINIBAND_VMWARE_PVRDMA
|
||||
tristate "VMware Paravirtualized RDMA Driver"
|
||||
depends on NETDEVICES && ETHERNET && PCI && INET && VMXNET3
|
||||
---help---
|
||||
help
|
||||
This driver provides low-level support for VMware Paravirtual
|
||||
RDMA adapter. It interacts with the VMXNet3 driver to provide
|
||||
Ethernet capabilities.
|
||||
|
|
|
|||
|
|
@ -4,5 +4,5 @@ config INFINIBAND_RDMAVT
|
|||
depends on X86_64 && ARCH_DMA_ADDR_T_64BIT
|
||||
depends on PCI
|
||||
select DMA_VIRT_OPS
|
||||
---help---
|
||||
help
|
||||
This is a common software verbs provider for RDMA networks.
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ config RDMA_RXE
|
|||
select NET_UDP_TUNNEL
|
||||
select CRYPTO_CRC32
|
||||
select DMA_VIRT_OPS
|
||||
---help---
|
||||
help
|
||||
This driver implements the InfiniBand RDMA transport over
|
||||
the Linux network stack. It enables a system with a
|
||||
standard Ethernet adapter to interoperate with a RoCE
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
config INFINIBAND_IPOIB
|
||||
tristate "IP-over-InfiniBand"
|
||||
depends on NETDEVICES && INET && (IPV6 || IPV6=n)
|
||||
---help---
|
||||
help
|
||||
Support for the IP-over-InfiniBand protocol (IPoIB). This
|
||||
transports IP packets over InfiniBand so you can use your IB
|
||||
device as a fancy NIC.
|
||||
|
|
@ -13,7 +13,7 @@ config INFINIBAND_IPOIB_CM
|
|||
bool "IP-over-InfiniBand Connected Mode support"
|
||||
depends on INFINIBAND_IPOIB
|
||||
default n
|
||||
---help---
|
||||
help
|
||||
This option enables support for IPoIB connected mode. After
|
||||
enabling this option, you need to switch to connected mode
|
||||
through /sys/class/net/ibXXX/mode to actually create
|
||||
|
|
@ -28,7 +28,7 @@ config INFINIBAND_IPOIB_DEBUG
|
|||
bool "IP-over-InfiniBand debugging" if EXPERT
|
||||
depends on INFINIBAND_IPOIB
|
||||
default y
|
||||
---help---
|
||||
help
|
||||
This option causes debugging code to be compiled into the
|
||||
IPoIB driver. The output can be turned on via the
|
||||
debug_level and mcast_debug_level module parameters (which
|
||||
|
|
@ -42,7 +42,7 @@ config INFINIBAND_IPOIB_DEBUG
|
|||
config INFINIBAND_IPOIB_DEBUG_DATA
|
||||
bool "IP-over-InfiniBand data path debugging"
|
||||
depends on INFINIBAND_IPOIB_DEBUG
|
||||
---help---
|
||||
help
|
||||
This option compiles debugging code into the data path
|
||||
of the IPoIB driver. The output can be turned on via the
|
||||
data_debug_level module parameter; however, even with output
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ config INFINIBAND_ISER
|
|||
tristate "iSCSI Extensions for RDMA (iSER)"
|
||||
depends on SCSI && INET && INFINIBAND_ADDR_TRANS
|
||||
select SCSI_ISCSI_ATTRS
|
||||
---help---
|
||||
help
|
||||
Support for the iSCSI Extensions for RDMA (iSER) Protocol
|
||||
over InfiniBand. This allows you to access storage devices
|
||||
that speak iSCSI over iSER over InfiniBand.
|
||||
|
|
|
|||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче