Searched full:implementations (Results 1 – 25 of 686) sorted by relevance
12345678910>>...28
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | dm-log.rst | 15 implementations use to perform logging operations (see
17 logging implementations are available and provide different
43 so log implementations can be done there. This is done by forwarding most
53 There are currently two userspace log implementations that leverage this
54 framework - "clustered-disk" and "clustered-core". These implementations
56 can be used in a shared-storage environment when the cluster log implementations
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 38 For implementations complying to PSCI versions prior to 0.2.
42 For implementations complying to PSCI 0.2.
46 For implementations complying to PSCI 0.2.
56 For implementations complying to PSCI 1.0.
60 For implementations complying to PSCI 1.0.
|
| /Linux-v5.4/mm/ |
| D | zpool.c | 7 * This is a common frontend for memory storage pool implementations.
149 * Implementations must guarantee this to be thread-safe.
207 * Implementations must guarantee this to be thread-safe,
232 * Implementations must guarantee this to be thread-safe.
248 * Implementations must guarantee this to be thread-safe.
269 * Implementations must guarantee this to be thread-safe.
288 * Implementations must guarantee this to be thread-safe,
311 * Implementations must guarantee this to be thread-safe.
|
| /Linux-v5.4/Documentation/crypto/ |
| D | architecture.rst | 23 The kernel crypto API provides implementations of single block ciphers
101 The kernel crypto API may provide multiple implementations of a template
103 the following implementations: AES-NI, assembler implementation, or
109 implementations providing an implementation with that name and selects
247 existing cipher implementations. The first section addresses the most
262 generic C implementations (gcm.c, aes-generic.c, ctr.c, ghash-generic.c,
266 It is possible that some streamlined cipher implementations (like
267 AES-NI) provide implementations merging aspects which in the view of the
378 Keyed message digest implementations again follow the same concept as
|
| D | intro.rst | 27 - data transformation implementations (typically ciphers) that can be
33 implementations (i.e. implementations of ciphers and other
|
| /Linux-v5.4/drivers/net/ethernet/ibm/emac/ |
| D | emac.h | 28 /* Common registers across all EMAC implementations. */
42 /* Registers unique to EMAC4 implementations */
53 /* Registers unique to EMAC4SYNC implementations */
62 /* Common registers across all EMAC implementations. */
72 /* Registers unique to EMAC4 implementations */
76 /* Registers unique to EMAC4SYNC implementations */
|
| /Linux-v5.4/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 117 not appear as the DOI identifier in any CIPSO option. Implementations
150 identifier field in the CIPSO header, implementations should assume that
160 types, implementations will require the DOI identifier as well as the tag
163 interoperability with other networks will not be an issue. Implementations
237 speed many implementations including router implementations.
334 speed many implementations including router implementations.
386 speed many implementations including router implementations.
447 parameters are required for CIPSO implementations:
543 CIPSO implementations that support only one label are not required to
544 support the parameters described above. These limited implementations are
|
| /Linux-v5.4/Documentation/core-api/ |
| D | genericirq.rst | 67 Analysing a couple of architecture's IRQ subsystem implementations
75 which is normally one of the generic implementations. (This high-level
86 of existing implementations, the :c:func:`__do_IRQ` super-handler is still
175 Default flow implementations
182 default flow implementations. The following helper functions are
217 Default flow handler implementations
347 implementations.
390 To avoid copies of identical implementations of IRQ chips the core
|
| /Linux-v5.4/Documentation/devicetree/bindings/mfd/ |
| D | cros-ec.txt | 24 - google,cros-ec-spi-pre-delay: Some implementations of the EC need a little
28 - google,cros-ec-spi-msg-delay: Some implementations of the EC require some
41 - google,has-vbc-nvram: Some implementations of the EC include a small
|
| /Linux-v5.4/drivers/crypto/caam/ |
| D | Kconfig | 95 bool "Register algorithm implementations with the Crypto API"
124 bool "Register hash algorithm implementations with Crypto API"
133 bool "Register public key cryptography implementations with Crypto API"
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | index.rst | 32 filesystem implementations.
44 Documentation for filesystem implementations.
|
| /Linux-v5.4/drivers/net/wireless/intel/iwlwifi/ |
| D | iwl-drv.h | 92 * This component is also in charge of managing the several implementations of
94 * different implementations will differ in the way they implement mac80211's
118 * specific system flows implementations. For example, the bus specific probe
130 * implementations. For example, the bus specific remove function should first
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | ufs.rst | 13 The problem are differences among implementations. Features of
14 some implementations are undocumented, so its hard to recognize
|
| /Linux-v5.4/arch/openrisc/include/asm/ |
| D | cmpxchg.h | 2 * 1,2 and 4 byte cmpxchg and xchg implementations for OpenRISC.
12 * The portable implementations of 1 and 2 byte xchg and cmpxchg using a 4
13 * byte cmpxchg is sourced heavily from the sh and mips implementations.
|
| /Linux-v5.4/arch/arm/include/debug/ |
| D | samsung.S | 10 /* The S5PV210/S5PC110 implementations are as belows. */
24 /* The S3C2440 implementations are used by default as they are the
|
| /Linux-v5.4/lib/raid6/ |
| D | neon.c | 20 * from the actual implementations in neonN.c (generated from neon.uc by
22 * - the actual implementations use NEON intrinsics, and the GCC support header
|
| /Linux-v5.4/Documentation/watchdog/ |
| D | mlx-wdt.rst | 13 There are 2 types of HW watchdog implementations.
45 This mlx-wdt driver supports both HW watchdog implementations.
|
| /Linux-v5.4/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu.txt | 44 For SMMUv2 implementations, there must be exactly one
68 implementations that always use secure access to
92 - unspecified for other implementations.
|
| /Linux-v5.4/drivers/pci/hotplug/ |
| D | TODO | 5 * There are no implementations of the ->hardware_test, ->get_power and
21 * Implementations of hotplug_slot_ops callbacks such as get_adapter_present()
|
| /Linux-v5.4/Documentation/sound/designs/ |
| D | tracepoints.rst | 93 it. Else, zero. But this behaviour depends on implementations in driver
99 it. Else, zero. But this behaviour depends on implementations in driver
106 on implementations in driver side.
|
| /Linux-v5.4/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 36 signals the command was ignored. Some Master implementations allow for a
39 solution. Alternatively some implementations might directly issue a bus
|
| /Linux-v5.4/Documentation/devicetree/bindings/misc/ |
| D | xlnx,sd-fec.txt | 4 which provides high-throughput LDPC and Turbo Code implementations.
8 power and area savings versus implementations done in the FPGA fabric.
|
| /Linux-v5.4/arch/arm/include/asm/ |
| D | outercache.h | 75 * It is intended that this function is only used by implementations
77 * (Some implementations perform this as a clean followed by an invalidate.)
|
| /Linux-v5.4/lib/ |
| D | dump_stack.c | 42 * Arch-specific dump_stack() implementations can use this function to
66 * show_regs() implementations can use this function to print out generic
|
| /Linux-v5.4/arch/powerpc/mm/book3s32/ |
| D | mmu_context.c | 4 * PowerPC implementations where the MMU substantially follows the
6 * and 8260 implementations but excludes the 8xx and 4xx.
|
12345678910>>...28
