| /Linux-v6.1/lib/crypto/ |
| D | Kconfig | 18 accelerated implementation of the Blake2s library interface,
27 implementation is enabled, this implementation serves the users
34 accelerated implementation of the ChaCha library interface,
44 implementation is enabled, this implementation serves the users
53 by either the generic implementation or an arch-specific one, if one
60 accelerated implementation of the Curve25519 library interface,
69 implementation is enabled, this implementation serves the users
79 fulfilled by either the generic implementation or an arch-specific
96 accelerated implementation of the Poly1305 library interface,
105 implementation is enabled, this implementation serves the users
[all …]
|
| D | curve25519-generic.c | 5 * This is an implementation of the Curve25519 ECDH algorithm, using either
6 * a 32-bit implementation or a 64-bit implementation with 128-bit integers,
|
| D | curve25519.c | 5 * This is an implementation of the Curve25519 ECDH algorithm, using either
6 * a 32-bit implementation or a 64-bit implementation with 128-bit integers,
|
| /Linux-v6.1/Documentation/crypto/ |
| D | architecture.rst | 103 the following implementations: AES-NI, assembler implementation, or
105 which cipher implementation is used? The answer to that question is the
106 priority number assigned to each cipher implementation by the kernel
109 implementations providing an implementation with that name and selects
110 the implementation with the highest priority.
113 implementation and thus does not want to rely on the priority-based
115 the cipher implementation to register a unique name in addition to
117 sure to refer to the intended cipher implementation.
133 - module: the kernel module providing the cipher implementation (or
136 - priority: the priority value of the cipher implementation
[all …]
|
| D | intro.rst | 43 The transformation implementation is an actual code or interface to
48 implementation. There can be multiple transformation objects associated
49 with a single transformation implementation. Each of those
52 consumer requests a transformation implementation. The consumer is then
|
| /Linux-v6.1/drivers/mailbox/ |
| D | Kconfig | 42 Mailbox implementation for i.MX Messaging Unit (MU).
58 An implementation of the ARM PL320 Interprocessor Communication
69 Mailbox implementation for communication with the the firmware
78 Mailbox implementation for OMAP family chips with hardware for
117 An implementation of the Altera Mailbox soft core. It is used
125 An implementation of the BCM2385 Mailbox. It is used to invoke
133 Mailbox implementation for STMicroelectonics family chips with
140 An implementation of Message Manager slave driver for Keystone
153 An implementation of the hi3660 mailbox. It is used to send message
163 An implementation of the hi6220 mailbox. It is used to send message
[all …]
|
| /Linux-v6.1/Documentation/arm/samsung/ |
| D | gpio.rst | 2 Samsung GPIO implementation
8 This outlines the Samsung GPIO implementation and the architecture
16 about these devices. Their implementation has been brought into line
17 with the core samsung implementation described in this document.
23 The gpio implementation uses gpiolib as much as possible, only providing
35 implementation to configure pins as necessary.
|
| /Linux-v6.1/arch/openrisc/ |
| D | Kconfig | 83 Select this if your implementation features write through data caches.
100 Select this if your implementation has the Class II instruction l.ff1
106 Select this if your implementation has the Class II instruction l.fl1
112 Select this if your implementation has a hardware multiply instruction
118 Select this if your implementation has a hardware divide instruction
128 Select this if your implementation has support for the Class II
141 Select this if your implementation has support for the Class II
154 Select this if your implementation has support for the Class II
167 Select this if your implementation has support for the Class II
|
| /Linux-v6.1/Documentation/core-api/ |
| D | genericirq.rst | 28 The original implementation of interrupt handling in Linux uses the
33 a quite universal set for the ARM interrupt handler implementation in
42 During the implementation we identified another type:
51 This split implementation of high-level IRQ handlers allows us to
56 The original general IRQ implementation used hw_interrupt_type
76 flow handler implementation also makes it simple to provide
82 IRQ-flow implementation for 'level type' interrupts and add a
83 (sub)architecture specific 'edge type' implementation.
225 handle_level_irq provides a generic implementation for level-triggered
238 handle_fasteoi_irq provides a generic implementation for interrupts,
[all …]
|
| /Linux-v6.1/arch/arm/crypto/ |
| D | Kconfig | 30 Use an implementation of GHASH (used by the GCM AEAD chaining mode)
64 BLAKE2b, but slower than the NEON implementation of BLAKE2b.
65 There is no NEON implementation of BLAKE2s, since NEON doesn't
80 Crypto Extensions, typically this BLAKE2b implementation is
156 fastest AES implementation for single blocks. For multiple
157 blocks, the NEON bit-sliced implementation is usually faster.
159 This implementation may be vulnerable to cache timing attacks,
184 This implementation does not rely on any lookup tables so it is
|
| /Linux-v6.1/drivers/char/xilinx_hwicap/ |
| D | buffer_icap.h | 13 * OR INFORMATION AS ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE,
15 * THAT THIS IMPLEMENTATION IS FREE FROM ANY CLAIMS OF INFRINGEMENT,
17 * FOR YOUR IMPLEMENTATION. XILINX EXPRESSLY DISCLAIMS ANY
19 * IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
20 * REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF
|
| D | fifo_icap.h | 13 * OR INFORMATION AS ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE,
15 * THAT THIS IMPLEMENTATION IS FREE FROM ANY CLAIMS OF INFRINGEMENT,
17 * FOR YOUR IMPLEMENTATION. XILINX EXPRESSLY DISCLAIMS ANY
19 * IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
20 * REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF
|
| /Linux-v6.1/tools/testing/selftests/powerpc/tm/ |
| D | tm.h | 38 * Transactional Memory was removed in ISA 3.1. A synthetic TM implementation
40 * synthetic implementation immediately fails after tbegin. This failure sets
41 * Bit 7 (Failure Persistent) and Bit 15 (Implementation-specific).
49 * times in case we got an Implementation-specific failure on a non ISA in htm_is_synthetic()
50 * v3.1 system. On these systems the Implementation-specific failure in htm_is_synthetic()
|
| /Linux-v6.1/Documentation/networking/caif/ |
| D | linux_caif.rst | 29 The implementation of CAIF is divided into:
32 * CAIF Core Protocol Implementation
59 Implementation chapter
75 The Core CAIF implementation contains:
77 - Simple implementation of CAIF.
92 Implementation. The support functions include:
94 - CFPKT CAIF Packet. Implementation of CAIF Protocol Packet. The
98 The CAIF Protocol implementation contains:
|
| /Linux-v6.1/security/selinux/ |
| D | xfrm.c | 150 * LSM hook implementation that authorizes that a flow can use a xfrm policy
173 * LSM hook implementation that authorizes that a state matches
259 * LSM hook implementation that checks and/or returns the xfrm sid for the
283 * LSM hook implementation that allocs and transfers uctx spec to xfrm_policy.
293 * LSM hook implementation that copies security data structure from old to new
315 * LSM hook implementation that frees xfrm_sec_ctx security information.
323 * LSM hook implementation that authorizes deletion of labeled policies.
331 * LSM hook implementation that allocates a xfrm_sec_state, populates it using
341 * LSM hook implementation that allocates a xfrm_sec_state and populates based
383 * LSM hook implementation that frees xfrm_state security information.
[all …]
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | men-chameleon-bus.rst | 9 1.2 Limitations of the current implementation
27 This document describes the architecture and implementation of the MEN
34 implementation and does by no means describe the complete possibilities of MCB
37 Limitations of the current implementation
40 The current implementation is limited to PCI and PCIe based carrier devices
69 not handled by the MCB implementation.
98 The current implementation assigns exactly one memory and one IRQ resource
|
| /Linux-v6.1/Documentation/locking/ |
| D | futex-requeue-pi.rst | 16 Without requeue_pi, the glibc implementation of
20 implementation would wake the highest-priority waiter, and leave the
56 user space already holding the PI futex. The glibc implementation
81 The actual glibc implementation will likely test for PI and make the
86 Implementation section in Futex Requeue PI
106 to be requeued to a PI-aware futex. The implementation is the
|
| /Linux-v6.1/drivers/net/ethernet/mellanox/mlxsw/ |
| D | Kconfig | 34 tristate "PCI bus implementation for Mellanox Technologies Switch ASICs"
38 This is PCI bus implementation for Mellanox Technologies Switch ASICs.
44 tristate "I2C bus implementation for Mellanox Technologies Switch ASICs"
48 This is I2C bus implementation for Mellanox Technologies Switch ASICs.
|
| /Linux-v6.1/Documentation/networking/ |
| D | x25.rst | 8 write an X.25 implementation for Linux. My aim is to provide a complete X.25
15 I therefore decided to write the implementation such that as far as the
18 implementation of LAPB. Therefore the LAPB modules would be called by
22 To confuse matters a little, an 802.2 LLC implementation is also possible
|
| /Linux-v6.1/tools/perf/include/bpf/linux/ |
| D | socket.h | 8 #define _K_SS_MAXSIZE 128 /* Implementation specific max size */
10 /* Implementation specific desired alignment */
16 /* Following field(s) are implementation specific */
|
| /Linux-v6.1/net/ipv4/ |
| D | tcp_lp.c | 11 * the original TCP-LP implementation:
27 * Original implementation for 2.4.19:
74 * We get the idea from original TCP-LP implementation where only left those we
95 * Clone the handling from Vegas module implementation.
117 * Implementation of cong_avoid.
135 * implementation only guest it for once and use forever.
220 * Implementation or rtt_sample.
225 * Most ideas come from the original TCP-LP implementation.
265 * Implementation of pkts_acked.
|
| /Linux-v6.1/include/uapi/linux/ |
| D | socket.h | 8 #define _K_SS_MAXSIZE 128 /* Implementation specific max size */
20 /* Following field(s) are implementation specific */
25 void *__align; /* implementation specific desired alignment */
|
| /Linux-v6.1/include/crypto/internal/ |
| D | kpp.h | 18 * @alg: The &struct kpp_alg implementation provided by the instance.
106 * kpp_instance_ctx() - Get a pointer to a &struct kpp_instance's implementation
110 * A KPP template implementation may allocate extra memory beyond the
114 * Return: A pointer to the implementation specific context data.
127 * Function registers an implementation of a key-agreement protocol primitive
140 * Function unregisters an implementation of a key-agreement protocol primitive
|
| /Linux-v6.1/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_dma_buf.c | 46 * amdgpu_dma_buf_attach - &dma_buf_ops.attach implementation
76 * amdgpu_dma_buf_detach - &dma_buf_ops.detach implementation
95 * amdgpu_dma_buf_pin - &dma_buf_ops.pin implementation
111 * amdgpu_dma_buf_unpin - &dma_buf_ops.unpin implementation
126 * amdgpu_dma_buf_map - &dma_buf_ops.map_dma_buf implementation
201 * amdgpu_dma_buf_unmap - &dma_buf_ops.unmap_dma_buf implementation
223 * amdgpu_dma_buf_begin_cpu_access - &dma_buf_ops.begin_cpu_access implementation
278 * amdgpu_gem_prime_export - &drm_driver.gem_prime_export implementation
353 * amdgpu_dma_buf_move_notify - &attach.move_notify implementation
421 * amdgpu_gem_prime_import - &drm_driver.gem_prime_import implementation
|
| /Linux-v6.1/mm/ |
| D | zpool.c | 33 * zpool_register_driver() - register a zpool implementation.
46 * zpool_unregister_driver() - unregister a zpool implementation.
142 * used when allocating memory, if the implementation supports it. If the
256 * implementation supports it. The provided @handle will be
319 * param indicates to the implementation how the memory will be
321 * implementation does not support it, the memory will be treated
328 * as soon as possible. As the implementation may use per-cpu
346 * actions that the implementation took in zpool_map_handle()
376 * in its implementation of zpool_driver.shrink. It could do internal
|
