| /drivers/android/ |
| D | Kconfig | 63 bool "Android Debug Kernel Information Support"
66 This supports kernel information backup for bootloader usage.
77 This option enables the padding that the Android GKI kernel adds
78 to many different kernel structures to support an in-kernel stable ABI
79 over the lifespan of support for the kernel.
82 kernel drivers, but is NOT an Android GKI kernel image. If disabled
83 it has the possibility to make the kernel static and runtime image
85 kernel team.
93 This option enables the padding that the Android GKI kernel adds
94 to many different kernel structures to support an in-kernel stable ABI
[all …]
|
| /drivers/pps/ |
| D | kc.c | 3 * PPS kernel consumer API
10 #include <linux/kernel.h>
23 /* state variables to bind kernel consumer */
25 /* PPS API (RFC 2783): current source and mode for kernel consumer */
27 static int pps_kc_hardpps_mode; /* mode bits for kernel consumer */
29 /* pps_kc_bind - control PPS kernel consumer binding
31 * @bind_args: kernel consumer bind parameters
33 * This function is used to bind or unbind PPS kernel consumer according to
46 dev_info(&pps->dev, "unbound kernel" in pps_kc_bind()
50 dev_err(&pps->dev, "selected kernel consumer" in pps_kc_bind()
[all …]
|
| /drivers/char/hw_random/ |
| D | Kconfig | 18 kernel's random number generator entropy pool.
28 This driver provides kernel-side support for a generic Random
43 This driver provides kernel-side support for the Random Number
57 This driver provides kernel-side support for the Random Number
70 This driver provides kernel-side support for the Random Number
82 This driver provides kernel-side support for the Random Number
94 This driver provides kernel-side support for the Random Number
107 This driver provides kernel-side support for the RNG200
121 This driver provides kernel-side support for the Random Number
134 This driver provides kernel-side support for the Random Number
[all …]
|
| /drivers/base/firmware_loader/ |
| D | Kconfig | 10 This enables the firmware loading facility in the kernel. The kernel
14 o firmware_class path module parameter or kernel boot param
20 Enabling this feature only increases your kernel image by about
37 SHA256 checksums to the kernel log for each firmware file that is
56 string "Build named firmware blobs into the kernel binary"
59 having the kernel load firmware from the various supported
61 kernel firmware files. Built-in firmware searches are preceded
76 the usb8388.bin file into /lib/firmware, and build the kernel. Then
78 inside the kernel without ever looking at your filesystem at runtime.
81 kernel image that are not available under the terms of the GPL,
[all …]
|
| /drivers/android/binder/ |
| D | rust_binder_main.rs | 8 use kernel::{
46 use kernel::bindings::{dentry, inode};
49 pub fn init_rust_binderfs() -> kernel::ffi::c_int; in init_rust_binderfs()
54 pid: kernel::ffi::c_int, in rust_binderfs_create_proc_file()
60 pub type rust_binder_context = *mut kernel::ffi::c_void;
64 pub minor: kernel::ffi::c_int,
86 use kernel::bindings::rust_binder_layout;
173 kernel::list::impl_has_list_links_self_ptr! {
176 kernel::list::impl_list_arc_safe! {
181 kernel::list::impl_list_item! {
[all …]
|
| /drivers/gpu/drm/ci/xfails/ |
| D | msm-sdm845-flakes.txt | 2 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
9 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
16 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
23 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
30 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
37 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
44 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
51 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
58 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
65 # Bug Report: https://lore.kernel.org/linux-arm-msm/661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.…
[all …]
|
| D | vkms-none-flakes.txt | 2 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
9 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
16 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
23 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
30 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
37 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
44 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
51 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
58 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
65 # Bug Report: https://lore.kernel.org/dri-devel/61ed26af-062c-443c-9df2-d1ee319f3fb0@collabora.com/…
[all …]
|
| D | i915-amly-flakes.txt | 2 # Bug Report: https://lore.kernel.org/intel-gfx/af4ca4df-a3ef-4943-bdbf-4c3af2c333af@collabora.com/…
9 # Bug Report: https://lore.kernel.org/intel-gfx/af4ca4df-a3ef-4943-bdbf-4c3af2c333af@collabora.com/…
16 # Bug Report: https://lore.kernel.org/intel-gfx/af4ca4df-a3ef-4943-bdbf-4c3af2c333af@collabora.com/…
23 # Bug Report: https://lore.kernel.org/intel-gfx/af4ca4df-a3ef-4943-bdbf-4c3af2c333af@collabora.com/…
30 # Bug Report: https://lore.kernel.org/intel-gfx/af4ca4df-a3ef-4943-bdbf-4c3af2c333af@collabora.com/…
37 # Bug Report: https://lore.kernel.org/intel-gfx/af4ca4df-a3ef-4943-bdbf-4c3af2c333af@collabora.com/…
44 # Bug Report: https://lore.kernel.org/intel-gfx/af4ca4df-a3ef-4943-bdbf-4c3af2c333af@collabora.com/…
|
| D | rockchip-rk3399-flakes.txt | 2 # Bug Report: https://lore.kernel.org/linux-rockchip/3e267d0c-fde4-4533-b001-6ab7d7c03546@collabora…
9 # Bug Report: https://lore.kernel.org/linux-rockchip/3e267d0c-fde4-4533-b001-6ab7d7c03546@collabora…
16 # Bug Report: https://lore.kernel.org/linux-rockchip/3e267d0c-fde4-4533-b001-6ab7d7c03546@collabora…
23 # Bug Report: https://lore.kernel.org/linux-rockchip/3e267d0c-fde4-4533-b001-6ab7d7c03546@collabora…
30 # Bug Report: https://lore.kernel.org/linux-rockchip/3e267d0c-fde4-4533-b001-6ab7d7c03546@collabora…
37 # Bug Report: https://lore.kernel.org/linux-rockchip/3e267d0c-fde4-4533-b001-6ab7d7c03546@collabora…
44 # Bug Report: https://lore.kernel.org/linux-rockchip/3e267d0c-fde4-4533-b001-6ab7d7c03546@collabora…
|
| /drivers/base/ |
| D | Kconfig | 10 The uevent helper program is forked by the kernel for
13 used to hook hotplug scripts into kernel device events. It
28 via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper
35 In this filesystem, the kernel driver core maintains device
51 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
54 This will instruct the kernel to automatically mount the
55 devtmpfs filesystem at /dev, directly after the kernel has
69 This instructs the kernel to include the MS_NOEXEC and MS_NOSUID mount
90 driver firmware at kernel build time. These drivers do not use the
91 kernel firmware API to load firmware (CONFIG_FW_LOADER), instead they
[all …]
|
| /drivers/accessibility/speakup/ |
| D | Kconfig | 10 kernel, it can speak everything on the text console from
55 synthesizer. You can say y to build it into the kernel,
64 synthesizer. You can say y to build it into the kernel,
72 synthesizer. You can say y to build it into the kernel,
80 You can say y to build it into the kernel, or m to
88 synthesizer. You can say y to build it into the kernel,
97 synthesizer. You can say y to build it into the kernel,
107 kernel, or m to build it as a module. See the
141 kernel, or m to build it as a module. See the
152 kernel, or m to build it as a module. See the
[all …]
|
| /drivers/bluetooth/ |
| D | Kconfig | 36 kernel or say M to compile it as module (btusb).
46 on the kernel commandline.
102 kernel or say M to compile it as module (btsdio).
118 kernel or say M to compile it as module (hci_uart).
299 kernel or say M to compile it as module (bcm203x).
311 kernel or say M to compile it as module (hci_bcm4377).
322 kernel or say M to compile it as module (bpa10x).
335 kernel or say M to compile it as module (bfusb).
348 kernel or say M to compile it as module (dtl1_cs).
362 kernel or say M to compile it as module (bt3c_cs).
[all …]
|
| /drivers/tty/serial/ |
| D | Kconfig | 38 console (the system console is the device which receives all kernel
43 you can alter that using a kernel command line option such as
46 kernel at boot time.)
66 console (the system console is the device which receives all kernel
71 you can alter that using a kernel command line option such as
74 kernel at boot time.)
85 This is enabled with "earlycon=smh" on the kernel command line.
97 with "earlycon=sbi" on the kernel command line. The console is
123 kernel messages and warnings and which allows logins in single user
147 console is the device which receives all kernel messages and
[all …]
|
| /drivers/firmware/efi/libstub/ |
| D | kaslr.c | 11 * efi_kaslr_get_phys_seed() - Get random seed for physical kernel KASLR
15 * that will be used to move the kernel physical mapping.
28 efi_info("KASLR disabled on kernel command line\n"); in efi_kaslr_get_phys_seed()
89 * efi_kaslr_relocate_kernel() - Relocate the kernel (random if KASLR enabled)
90 * @image_addr: Pointer to the current kernel location
91 * @reserve_addr: Pointer to the relocated kernel location
92 * @reserve_size: Size of the relocated kernel
98 * If KASLR is not enabled, this function relocates the kernel to a fixed
100 * kernel physical location is randomized using the seed in parameter.
118 * locate the kernel at a randomized offset in physical memory. in efi_kaslr_relocate_kernel()
[all …]
|
| /drivers/staging/iio/Documentation/ |
| D | sysfs-bus-iio-dds | 4 Contact: linux-iio@vger.kernel.org
15 Contact: linux-iio@vger.kernel.org
24 Contact: linux-iio@vger.kernel.org
34 Contact: linux-iio@vger.kernel.org
45 Contact: linux-iio@vger.kernel.org
54 Contact: linux-iio@vger.kernel.org
65 Contact: linux-iio@vger.kernel.org
77 Contact: linux-iio@vger.kernel.org
85 Contact: linux-iio@vger.kernel.org
94 Contact: linux-iio@vger.kernel.org
|
| /drivers/gpu/drm/xe/ |
| D | xe_bo_doc.h | 24 * Kernel BOs
27 * A kernel BO is created as part of driver load (e.g. uC firmware images, GuC
29 * a kernel BO (e.g. engine state, memory for page tables, etc...). These BOs
30 * are typically mapped in the GGTT (any kernel BOs aside memory for page tables
35 * More details of why kernel BOs are pinned and contiguous below.
137 * with kernel BOs.
139 * Some kernel BOs are used by the GT migration engine to do moves, thus we
141 * TTM memcpy (CPU) to move any kernel (pinned) BO on either suspend or resume.
143 * Some kernel BOs need to be restored to the exact same physical location. TTM
145 * for simplity, we enforce that all kernel (pinned) BOs are contiguous and
[all …]
|
| /drivers/vhost/ |
| D | Kconfig | 35 tristate "Host kernel accelerator for virtio net"
39 This kernel module can be loaded in host kernel to accelerate
41 module itself which needs to be loaded in guest kernel.
62 This kernel module can be loaded in the host kernel to provide AF_VSOCK
76 This kernel module can be loaded in host kernel to accelerate
|
| /drivers/hwtracing/stm/ |
| D | Kconfig | 52 tristate "Kernel console over STM devices"
54 This is a kernel space trace source that sends kernel log
57 If you want to send kernel console messages over STM devices,
63 This is a kernel space trace source that sends periodic
72 tristate "Copy the output from kernel Ftrace to STM engine"
75 This option can be used to copy the output from kernel Ftrace
79 If you want to send kernel Ftrace messages over STM devices,
|
| /drivers/firmware/efi/ |
| D | Kconfig | 41 arrange for the kernel to reserve it as a "Soft Reserved"
45 device-dax kmem facility. Say N to have the kernel treat this
56 accessible for both write and execute as the kernel expects
60 ranges used by the kernel are writable and executable.
82 actual kernel image in compressed form, and decompresses it into
146 kernel subsystem, just for testing the UEFI runtime service
204 kernel. System firmware may configure the IOMMU to prevent malicious
214 kernel reenables busmastering after configuring the IOMMU.
217 and should not be enabled without testing. The kernel commandline
233 by a kernel command line option.
[all …]
|
| /drivers/media/platform/mediatek/vpu/ |
| D | mtk_vpu.h | 27 * @IPI_VPU_INIT: The interrupt from vpu is to notfiy kernel
34 * @IPI_VDEC_H264: The interrupt from vpu is to notify kernel to
38 * @IPI_VDEC_VP8: The interrupt from is to notify kernel to
42 * @IPI_VDEC_VP9: The interrupt from vpu is to notify kernel to
46 * @IPI_VENC_H264: The interrupt from vpu is to notify kernel to
48 * @IPI_VENC_VP8: The interrupt fro vpu is to notify kernel to
50 * @IPI_MDP: The interrupt from vpu is to notify kernel to
174 * vpu_mapping_dm_addr - Mapping DTCM/DMEM to kernel virtual address
181 * kernel virtual address.
184 * otherwise the mapped kernel virtual address
|
| /drivers/gpu/drm/amd/amdkfd/ |
| D | kfd_doorbell.c | 31 * This extension supports a kernel level doorbells management for the
32 * kernel queues using the first doorbell page reserved for the kernel.
68 * Todo: KFD kernel level operations need only one doorbell for in kfd_doorbell_init()
70 * kernel, reserve and consume a doorbell from existing KGD kernel in kfd_doorbell_init()
74 /* Bitmap to dynamically allocate doorbells from kernel page */ in kfd_doorbell_init()
77 DRM_ERROR("Failed to allocate kernel doorbell bitmap\n"); in kfd_doorbell_init()
81 /* Alloc a doorbell page for KFD kernel usages */ in kfd_doorbell_init()
90 pr_err("failed to allocate kernel doorbells\n"); in kfd_doorbell_init()
95 pr_debug("Doorbell kernel address == %p\n", kfd->doorbell_kernel_ptr); in kfd_doorbell_init()
149 /* get kernel iomem pointer for a doorbell */
[all …]
|
| /drivers/gpu/drm/ |
| D | Kconfig | 24 Kernel-level support for the Direct Rendering Infrastructure (DRI)
93 distributions or general kernels, but only for kernel
113 bool "Display a user-friendly message when a kernel panic occurs"
119 when a kernel panic occurs. It's useful when using a user-space
139 Add dri/[device]/drm_panic_plane_x in the kernel debugfs, to force the
149 This option enable to choose what will be displayed when a kernel
153 This can also be overridden by drm.panic_screen=xxxx kernel parameter
164 information. This should be easier for the user to report a kernel
172 This option sets the base URL to report the kernel panic. If it's set
199 kernel log once a port or branch device's topology refcount reaches 0.
[all …]
|
| /drivers/net/wireless/intel/iwlwifi/ |
| D | Kconfig | 30 This driver uses the kernel's mac80211 subsystem.
35 <https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi>.
43 inserted in and removed from the running kernel whenever you want),
72 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
82 https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
100 This will result in the kernel module being ~100k larger. You can
101 control which debug output is sent to the kernel log by setting the
155 Enables the iwlmei kernel module.
162 This kernel module allows to communicate with the Intel Management
|
| /drivers/misc/sgi-gru/ |
| D | grukservices.c | 5 * KERNEL SERVICES THAT USE THE GRU
10 #include <linux/kernel.h>
32 * Kernel GRU Usage
34 * The following is an interim algorithm for management of kernel GRU
36 * kernel/user requirements.
38 * Blade percpu resources reserved for kernel use. These resources are
39 * reserved whenever the kernel context for the blade is loaded. Note
40 * that the kernel context is not guaranteed to be always available. It is
42 * kernel demand. The kernel can always reload the kernel context but
47 * Each blade has one "kernel context" that owns GRU kernel resources
[all …]
|
| /drivers/eisa/ |
| D | Kconfig | 21 Say Y here if you are building a kernel for an EISA-based machine.
65 By default, the kernel contains a database of all known EISA
67 to the user. This database increases size of the kernel
69 boots up, so it doesn't take up kernel memory. Anyway, if
70 you are building an installation floppy or kernel for an
71 embedded system where kernel image size really matters, you
|