Searched refs:mechanism (Results 1 – 25 of 402) sorted by relevance
12345678910>>...17
| /Linux-v5.4/Documentation/driver-api/firmware/ |
| D | fallback-mechanisms.rst | 5 A fallback mechanism is supported to allow to overcome failures to do a direct
8 configuration options related to supporting the firmware fallback mechanism are:
11 mechanism. Most distributions enable this option today. If enabled but
13 mechanism is available and for the request_firmware_nowait() call.
15 enable the kobject uevent fallback mechanism on all firmware API calls
18 fallback mechanism: if this kconfig option is enabled and your second
20 informing the kernel that you have a custom fallback mechanism and it will
28 the kobject uevent fallback mechanism will never take effect even
31 Justifying the firmware fallback mechanism
36 fallback mechanism:
[all …]
|
| D | firmware_cache.rst | 32 userspace for the firmware request through the sysfs fallback mechanism
43 * The timeout for the fallback mechanism is temporarily reduced to 10 seconds
50 cache mechanism but must not use the firmware API on suspend.
|
| D | lookup-order.rst | 15 * If no firmware has been found and the fallback mechanism was enabled
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | rpc-server-gss.txt | 22 Authentication for NFS. Although GSSAPI is itself completely mechanism
23 agnostic, in many cases only the KRB5 mechanism is supported by NFS
26 The Linux kernel, at the moment, supports only the KRB5 mechanism, and
46 The classic upcall mechanism uses a custom text based upcall mechanism
50 This upcall mechanism has 2 limitations:
67 The newer upcall mechanism uses RPC over a unix socket to a daemon
74 This upcall mechanism uses the kernel rpc client and connects to the gssproxy
82 legacy mechanism. To switch to the new mechanism, gss-proxy must bind
87 Once the upcall mechanism is chosen, it cannot be changed. To prevent
|
| /Linux-v5.4/drivers/base/firmware_loader/ |
| D | Kconfig | 72 bool "Enable the firmware sysfs fallback mechanism"
76 loading to the kernel through userspace as a fallback mechanism
81 built-in. For details on how to work with the sysfs fallback mechanism
90 this is known as the driver using the custom fallback mechanism.
91 If the custom fallback mechanism is used userspace must always
93 mechanism is disabled, and failed requests will linger forever.
98 can no longer be relied upon as a fallback mechanism. Linux no longer
99 relies on or uses a fallback mechanism in userspace. If you need to
106 mechanism can never be removed from the kernel.
109 require a fallback mechanism and have a userspace mechanism ready to
[all …]
|
| /Linux-v5.4/drivers/hwspinlock/ |
| D | Kconfig | 26 provides a synchronisation mechanism for the various processors on
37 provides a synchronisation mechanism for the various processors
67 provides a synchronisation mechanism for the various processor on the
|
| /Linux-v5.4/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 8 mechanism (sync loss after two errors) and short CRCs used for the Bulk
13 1. Bus clash or parity errors: This mechanism relies on low-level detectors
25 indication of a bus allocation issue. The interrupt mechanism can also help
60 Note that SoundWire does not provide a mechanism to detect illegal values
63 implementation does not provide a recovery mechanism for such errors, Slave
|
| /Linux-v5.4/net/sunrpc/ |
| D | Kconfig | 20 tristate "Secure RPC: Kerberos V mechanism"
29 GSS-API mechanism (RFC 1964).
44 with the Kerberos version 5 GSS-API mechanism (RFC 1964). The
|
| /Linux-v5.4/Documentation/ |
| D | robust-futex-ABI.txt | 8 Robust_futexes provide a mechanism that is used in addition to normal
23 mechanism, which handles uncontested locking without needing a system
80 lock variable used by the futex mechanism, in conjunction with
83 mechanism to register the address of that 'lock word' with the kernel.
91 that lock using the futex mechanism.
104 robust_futex mechanism doesn't care what else is in that structure, so
118 existing futex mechanism to wait for, and wakeup, locks. The kernels
164 used to the futex mechanism to wait on that address, and
|
| /Linux-v5.4/Documentation/core-api/ |
| D | tracepoint.rst | 13 a callback mechanism. The 'probes' are strictly typed functions that are
16 From this simple callback mechanism, 'probes' can be used to profile,
|
| /Linux-v5.4/Documentation/devicetree/bindings/thermal/ |
| D | stm32-thermal.txt | 8 DTS provides interrupt notification mechanism by threshold. This mechanism
|
| /Linux-v5.4/Documentation/driver-api/i3c/ |
| D | protocol.rst | 61 The I3C protocol defines a mechanism to automatically discover devices present
65 The discovery mechanism is called DAA (Dynamic Address Assignment), because it
75 Provisional ID collision, otherwise the discovery mechanism may fail.
83 This mechanism is called IBI for In Band Interrupts, and as stated in the name,
98 The Hot-Join mechanism is similar to USB hotplug. This mechanism allows
106 This mechanism is relying on slave events to inform the master that a new
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | thermal-notification | 1 What: A notification mechanism for thermal related events
|
| /Linux-v5.4/Documentation/netlabel/ |
| D | introduction.rst | 12 NetLabel is a mechanism which can be used by kernel security modules to attach
36 protocol built on top of the Generic NETLINK transport mechanism. The exact
|
| D | cipso_ipv4.rst | 44 The CIPSO/IPv4 protocol engine contains a mechanism to translate CIPSO security
56 CIPSO/IPv4 protocol engine supports this caching mechanism.
|
| D | lsm_interface.rst | 12 NetLabel is a mechanism which can set and retrieve security attributes from
45 NetLabel label mapping cache is a caching mechanism which can be used to
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | dell_rbu.rst | 54 The driver supports two types of update mechanism; monolithic and packetized.
55 These update mechanism depends upon the BIOS currently running on the system.
59 In case of packet mechanism the single memory can be broken in smaller chunks
73 In the packet update mechanism, the user needs to create a new file having
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | initrd.rst | 32 mechanism" section below.
180 with an older mechanism, the following boot command line parameters
325 Obsolete root change mechanism
328 The following mechanism was used before the introduction of pivot_root.
338 In order to use this mechanism, you do not have to specify the boot
348 Note that the mechanism is incompatible with NFS and similar file
351 This old, deprecated mechanism is commonly called ``change_root``, while
352 the new, supported mechanism is called ``pivot_root``.
355 Mixed change_root and pivot_root mechanism
359 mechanism, you may create both ``/linuxrc`` and ``/sbin/init`` in your initrd
|
| /Linux-v5.4/Documentation/ABI/removed/ |
| D | ip_queue | 6 more advanced queueing mechanism to user-space. The ip_queue
|
| /Linux-v5.4/fs/verity/ |
| D | Kconfig | 11 mechanism implemented at the file level. On supported
49 This is meant as a relatively simple mechanism that can be
|
| /Linux-v5.4/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | reboot.txt | 4 software reset mechanism may be overridden. Here the possible values of
|
| /Linux-v5.4/net/batman-adv/ |
| D | Kconfig | 41 This option enables BLA (Bridge Loop Avoidance), a mechanism
53 mechanism that increases ARP reliability on sparse wireless
61 This option enables network coding, a mechanism that aims to
|
| /Linux-v5.4/kernel/irq/ |
| D | Kconfig | 13 # Enable the generic irq autoprobe mechanism
42 # Alpha specific irq affinity mechanism
|
| /Linux-v5.4/drivers/base/ |
| D | Kconfig | 78 use their own custom loading mechanism. The required firmware is
96 device coredump mechanism.
102 This option controls if the device coredump mechanism is available or
103 not; if disabled, the mechanism will be omitted even if drivers that
|
| /Linux-v5.4/Documentation/devicetree/bindings/powerpc/ |
| D | ibm,vas.txt | 3 VAS is a hardware mechanism that allows kernel subsystems and user processes
|
12345678910>>...17
