| /linux/Documentation/devicetree/bindings/iio/proximity/ |
| H A D | awinic,aw96103.yaml | 19 phone approaches the human body, it will actively reduce the transmit
|
| /linux/drivers/remoteproc/ |
| H A D | omap_remoteproc.h | 24 * as we progress and experiment with those two different approaches.
|
| /linux/Documentation/gpu/ |
| H A D | drm-compute.rst | 37 only approaches possible. So even with those, you want a separate way of
|
| /linux/tools/memory-model/Documentation/ |
| H A D | README | 102 And also a reminder of the simpler approaches to concurrency!
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | gpio-get-linehandle-ioctl.rst | 86 hardware and driver, the kernel applies one of these approaches:
|
| H A D | gpio-v2-get-line-ioctl.rst | 103 hardware and driver, the kernel applies one of these approaches:
|
| /linux/Documentation/locking/ |
| H A D | pi-futex.rst | 113 Note that under this approach, contrary to previous PI-futex approaches,
|
| /linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 41 All three approaches need to modify the existing code at runtime. Therefore
94 Livepatch uses several complementary approaches to determine when it's
|
| H A D | reliable-stacktrace.rst | 19 functions with live state, and best-effort approaches which can be helpful for
|
| /linux/arch/microblaze/kernel/ |
| H A D | ftrace.c | 105 /* There are two approaches howto solve ftrace_make nop function - look below */
|
| /linux/tools/testing/selftests/bpf/benchs/ |
| H A D | bench_local_storage_rcu_tasks_trace.c | 250 * This benchmark uses both approaches, attaching to rcu_tasks_trace_pregp_step
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | SafeSetID.rst | 48 Other Approaches Considered
|
| /linux/arch/x86/math-emu/ |
| H A D | README | 360 argument approaches pi/2. The table does not show those cases when the
362 often for fsin and fptan when the argument approaches pi/2. This poor
|
| /linux/Documentation/mm/ |
| H A D | highmem.rst | 12 High memory (highmem) is used when the size of physical memory approaches or
|
| H A D | multigen_lru.rst | 115 increments ``max_seq`` when ``max_seq-min_seq+1`` approaches
|
| /linux/arch/arm64/include/asm/ |
| H A D | io.h | 139 * approaches have a very low chance to generate write combining.
|
| /linux/drivers/md/dm-vdo/ |
| H A D | memory-alloc.c | 204 * been made elsewhere. It can wait for other tasks to attempt high level approaches to in vdo_allocate_memory()
|
| /linux/Documentation/networking/ |
| H A D | openvswitch.rst | 120 two possible approaches: reactively install flows as they miss the kernel
|
| /linux/Documentation/admin-guide/nfs/ |
| H A D | nfsroot.rst | 248 To get the kernel into memory different approaches can be used.
|
| /linux/include/linux/ |
| H A D | gfp_types.h | 231 * tasks to attempt high-level approaches to freeing memory such as
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | gpio-properties.rst | 308 There are two main approaches to get GPIO resource from ACPI::
|
| /linux/Documentation/driver-api/media/ |
| H A D | dtv-frontend.rst | 339 can be done using two approaches:
|
| /linux/drivers/pwm/ |
| H A D | pwm-microchip-core.c | 234 * especially as tmp approaches integer multiples of in mchp_core_pwm_calc_period()
|
| /linux/Documentation/filesystems/ |
| H A D | erofs.rst | 18 amplification and memory-resident overhead compared to similar approaches.
|
| /linux/arch/sparc/mm/ |
| H A D | tsb.c | 392 * The idea here is to grow the TSB when the RSS of the process approaches
|