| /linux/lib/crypto/ |
| H A D | Kconfig | 32 accelerated implementation of the Blake2s library interface,
41 implementation is enabled, this implementation serves the users
48 accelerated implementation of the ChaCha library interface,
58 implementation is enabled, this implementation serves the users
67 by either the generic implementation or an arch-specific one, if one
74 accelerated implementation of the Curve25519 library interface,
83 implementation is enabled, this implementation serves the users
93 fulfilled by either the generic implementation or an arch-specific
110 accelerated implementation of the Poly1305 library interface,
119 implementation is enabled, this implementation serves the users
[all …]
|
| H A 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,
|
| H A 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/Documentation/crypto/ |
| H A 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 …]
|
| H A 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/drivers/mailbox/ |
| H A 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
108 An implementation of the Altera Mailbox soft core. It is used
116 An implementation of the BCM2385 Mailbox. It is used to invoke
124 Mailbox implementation for STMicroelectonics family chips with
132 An implementation of Message Manager slave driver for Keystone
145 An implementation of the hi3660 mailbox. It is used to send message
155 An implementation of the hi6220 mailbox. It is used to send message
[all …]
|
| /linux/arch/openrisc/ |
| H A D | Kconfig | 85 Select this if your implementation features write through data caches.
102 Select this if your implementation has the Class II instruction l.ff1
108 Select this if your implementation has the Class II instruction l.fl1
114 Select this if your implementation has a hardware multiply instruction
120 Select this if your implementation has a hardware divide instruction
130 Select this if your implementation has support for the Class II
143 Select this if your implementation has support for the Class II
156 Select this if your implementation has support for the Class II
169 Select this if your implementation has support for the Class II
|
| /linux/Documentation/core-api/ |
| H A 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/security/selinux/ |
| H A D | xfrm.c | 145 * LSM hook implementation that authorizes that a flow can use a xfrm policy
167 * LSM hook implementation that authorizes that a state matches
253 * LSM hook implementation that checks and/or returns the xfrm sid for the
277 * LSM hook implementation that allocs and transfers uctx spec to xfrm_policy.
287 * LSM hook implementation that copies security data structure from old to new
309 * LSM hook implementation that frees xfrm_sec_ctx security information.
317 * LSM hook implementation that authorizes deletion of labeled policies.
325 * LSM hook implementation that allocates a xfrm_sec_state, populates it using
335 * LSM hook implementation that allocates a xfrm_sec_state and populates based
377 * LSM hook implementation that frees xfrm_state security information.
[all …]
|
| /linux/Documentation/networking/caif/ |
| H A 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/drivers/char/xilinx_hwicap/ |
| H A 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
|
| H A 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
|
| /linux/tools/testing/selftests/powerpc/tm/ |
| H A 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/arch/arm/crypto/ |
| H A D | Kconfig | 32 Use an implementation of GHASH (used by the GCM AEAD chaining mode)
66 BLAKE2b, but slower than the NEON implementation of BLAKE2b.
67 There is no NEON implementation of BLAKE2s, since NEON doesn't
82 Crypto Extensions, typically this BLAKE2b implementation is
158 fastest AES implementation for single blocks. For multiple
159 blocks, the NEON bit-sliced implementation is usually faster.
161 This implementation may be vulnerable to cache timing attacks,
|
| /linux/Documentation/arch/arm/samsung/ |
| H A D | gpio.rst | 2 Samsung GPIO implementation
8 This outlines the Samsung GPIO implementation and the architecture
15 The gpio implementation uses gpiolib as much as possible, only providing
27 implementation to configure pins as necessary.
|
| /linux/Documentation/driver-api/ |
| H A 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/Documentation/locking/ |
| H A 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 chapter
106 to be requeued to a PI-aware futex. The implementation is the
|
| /linux/Documentation/i2c/ |
| H A D | summary.rst | 42 Linux kernel implementation it is also called an "adapter" or "bus". Controller
48 own implementation.
51 controller. In the Linux kernel implementation it is also called a "client".
68 As mentioned above, the Linux I2C implementation historically uses the terms
70 have these synonyms in their name. So, when discussing implementation details,
|
| /linux/Documentation/ABI/testing/ |
| H A D | configfs-tsm | 16 options The format of the report is implementation specific
17 where the implementation is conveyed via the @provider
81 (WO) Attribute is visible if a TSM implementation provider
101 (WO) Attribute is visible if a TSM implementation provider
118 (WO) Attribute is visible if a TSM implementation provider
136 (WO) Attribute is visible if a TSM implementation provider
|
| /linux/Documentation/networking/ |
| H A 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/drivers/net/ethernet/mellanox/mlxsw/ |
| H A D | Kconfig | 34 tristate "PCI bus implementation for Mellanox Technologies Switch ASICs"
39 This is PCI bus implementation for Mellanox Technologies Switch ASICs.
45 tristate "I2C bus implementation for Mellanox Technologies Switch ASICs"
49 This is I2C bus implementation for Mellanox Technologies Switch ASICs.
|
| /linux/net/ipv4/ |
| H A 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/include/uapi/linux/ |
| H A 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/Documentation/arch/arm/ |
| H A D | vlocks.rst | 119 ARM implementation
122 The current ARM implementation [2] contains some optimisations beyond
130 In the ARM implementation, this means that we can use a single load
159 implementation uses a simple loop of word-sized loads for this
166 implementation.
171 implementation removes many of the barriers which would be required
|
| /linux/include/crypto/internal/ |
| H A D | kpp.h | 18 * @alg: The &struct kpp_alg implementation provided by the instance.
134 * kpp_instance_ctx() - Get a pointer to a &struct kpp_instance's implementation
138 * A KPP template implementation may allocate extra memory beyond the
142 * Return: A pointer to the implementation specific context data.
155 * Function registers an implementation of a key-agreement protocol primitive
168 * Function unregisters an implementation of a key-agreement protocol primitive
|