| /kernel/linux/linux-5.10/lib/crypto/ |
| D | Kconfig | 15 accelerated implementation of the Blake2s library interface,
24 implementation is enabled, this implementation serves the users
33 by either the generic implementation or an arch-specific one, if one
40 accelerated implementation of the ChaCha library interface,
50 implementation is enabled, this implementation serves the users
59 by either the generic implementation or an arch-specific one, if one
66 accelerated implementation of the Curve25519 library interface,
75 implementation is enabled, this implementation serves the users
84 fulfilled by either the generic implementation or an arch-specific
101 accelerated implementation of the Poly1305 library interface,
[all …]
|
| /kernel/liteos_m/ |
| D | arch_spec.md | 6 │ │ │ └── gcc --- Implementation of the GCC toolc…
8 │ │ │ └── keil --- Implementation of the keil tool…
10 │ │ │ │── gcc --- Implementation of the GCC toolc…
13 │ │ │ └── iar --- Implementation of the IAR toolc…
17 │ │ │ │── gcc --- Implementation of the GCC toolc…
18 │ │ │ └── iar --- Implementation of the IAR toolc…
20 │ │ │── gcc --- Implementation of the GCC toolc…
21 │ │ └── iar --- Implementation of the IAR toolc…
24 │ │ └── gcc --- Implementation of the GCC toolc…
27 │ │ └── gcc --- Implementation of the GCC toolc…
[all …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/drivers/mailbox/ |
| D | Kconfig | 23 Mailbox implementation for i.MX Messaging Unit (MU).
39 An implementation of the ARM PL320 Interprocessor Communication
50 Mailbox implementation for communication with the the firmware
59 Mailbox implementation for OMAP family chips with hardware for
98 An implementation of the Altera Mailbox soft core. It is used
106 An implementation of the BCM2385 Mailbox. It is used to invoke
114 Mailbox implementation for STMicroelectonics family chips with
121 An implementation of Message Manager slave driver for Keystone
134 An implementation of the hi3660 mailbox. It is used to send message
144 An implementation of the hi6220 mailbox. It is used to send message
[all …]
|
| /kernel/linux/linux-4.19/drivers/mailbox/ |
| D | Kconfig | 22 Mailbox implementation for i.MX Messaging Unit (MU).
38 An implementation of the ARM PL320 Interprocessor Communication
48 Mailbox implementation for OMAP family chips with hardware for
87 An implementation of the Altera Mailbox soft core. It is used
95 An implementation of the BCM2385 Mailbox. It is used to invoke
103 Mailbox implementation for STMicroelectonics family chips with
110 An implementation of Message Manager slave driver for Keystone
123 An implementation of the hi3660 mailbox. It is used to send message
133 An implementation of the hi6220 mailbox. It is used to send message
166 An implementation of the APM X-Gene Interprocessor Communication
[all …]
|
| /kernel/linux/linux-4.19/Documentation/arm/Samsung/ |
| D | GPIO.txt | 1 Samsung GPIO implementation
7 This outlines the Samsung GPIO implementation and the architecture
15 about these devices. Their implementation has been brought into line
16 with the core samsung implementation described in this document.
22 The gpio implementation uses gpiolib as much as possible, only providing
34 implementation to configure pins as necessary.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/arch/arm/crypto/ |
| D | Kconfig | 73 fastest AES implementation for single blocks. For multiple
74 blocks, the NEON bit-sliced implementation is usually faster.
76 This implementation may be vulnerable to cache timing attacks,
88 Use a faster and more secure NEON based implementation of AES in CBC,
94 This implementation does not rely on any lookup tables so it is
104 Use an implementation of AES in CBC, CTR and XTS modes that uses
114 Use an implementation of GHASH (used by the GCM AEAD chaining mode)
|
| /kernel/linux/linux-4.19/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.
223 handle_level_irq provides a generic implementation for level-triggered
236 handle_fasteoi_irq provides a generic implementation for interrupts,
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | x25.txt | 4 write an X.25 implementation for Linux. My aim is to provide a complete X.25
11 I therefore decided to write the implementation such that as far as the
14 implementation of LAPB. Therefore the LAPB modules would be called by
18 To confuse matters a little, an 802.2 LLC implementation for Linux is being
23 implementation is being done as part of another protocol project (SNA) and
|
| /kernel/linux/linux-4.19/Documentation/cgroup-v1/ |
| D | 00-INDEX | 4 - Description for Block IO Controller, implementation and usage details.
6 - Control Groups definition, implementation details, examples and API.
16 - HugeTLB Controller implementation and usage details.
18 - Memory Resource Controller; implementation details.
|
| /kernel/linux/linux-5.10/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 for Linux is being
27 implementation is being done as part of another protocol project (SNA) and
|
| /kernel/linux/linux-4.19/include/net/sctp/ |
| D | checksum.h | 1 /* SCTP kernel reference Implementation
5 * This file is part of the SCTP kernel reference Implementation
9 * The SCTP reference implementation is free software;
15 * The SCTP reference implementation is distributed in the hope that it
48 /* This uses the crypto implementation of crc32c, which is either in sctp_csum_update()
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/liteos_a/bsd/dev/usb/ |
| D | BUILD.gn | 36 "implementation/bsd_busspace.c",
37 "implementation/bsd_kernel.c",
38 "implementation/usb_btree.c",
39 "implementation/usb_busdma_loader.c",
40 "implementation/usb_init.c",
41 "implementation/usb_version.c",
|
| /kernel/linux/linux-5.10/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:
|
| /kernel/linux/linux-5.10/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
258 * LSM hook implementation that checks and/or returns the xfrm sid for the
282 * LSM hook implementation that allocs and transfers uctx spec to xfrm_policy.
292 * LSM hook implementation that copies security data structure from old to new
314 * LSM hook implementation that frees xfrm_sec_ctx security information.
322 * LSM hook implementation that authorizes deletion of labeled policies.
330 * LSM hook implementation that allocates a xfrm_sec_state, populates it using
340 * LSM hook implementation that allocates a xfrm_sec_state and populates based
382 * LSM hook implementation that frees xfrm_state security information.
[all …]
|
| /kernel/linux/linux-4.19/security/selinux/ |
| D | xfrm.c | 153 * LSM hook implementation that authorizes that a flow can use a xfrm policy
176 * LSM hook implementation that authorizes that a state matches
261 * LSM hook implementation that checks and/or returns the xfrm sid for the
285 * LSM hook implementation that allocs and transfers uctx spec to xfrm_policy.
295 * LSM hook implementation that copies security data structure from old to new
317 * LSM hook implementation that frees xfrm_sec_ctx security information.
325 * LSM hook implementation that authorizes deletion of labeled policies.
333 * LSM hook implementation that allocates a xfrm_sec_state, populates it using
343 * LSM hook implementation that allocates a xfrm_sec_state and populates based
385 * LSM hook implementation that frees xfrm_state security information.
[all …]
|
| /kernel/linux/linux-4.19/crypto/ |
| D | Kconfig | 123 Generic implementation of the RSA public key algorithm.
130 Generic implementation of the Diffie-Hellman algorithm.
137 Generic implementation of the ECDH algorithm
174 Efficient table driven implementation of multiplications in the
314 tristate "AEGIS-128 AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
319 AESNI+SSE2 implementation of the AEGSI-128 dedicated AEAD algorithm.
322 tristate "AEGIS-128L AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
327 AESNI+SSE2 implementation of the AEGSI-128L dedicated AEAD algorithm.
330 tristate "AEGIS-256 AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
335 AESNI+SSE2 implementation of the AEGSI-256 dedicated AEAD algorithm.
[all …]
|
| /kernel/linux/linux-4.19/arch/openrisc/ |
| D | Kconfig | 91 Select this if your implementation features write through data caches.
108 Select this if your implementation has the Class II instruction l.ff1
114 Select this if your implementation has the Class II instruction l.fl1
120 Select this if your implementation has a hardware multiply instruction
126 Select this if your implementation has a hardware divide instruction
|