| /linux-6.15/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
71 by either the generic implementation or an arch-specific one, if one
78 accelerated implementation of the Curve25519 library interface,
88 implementation is enabled, this implementation serves the users
101 fulfilled by either the generic implementation or an arch-specific
118 accelerated implementation of the Poly1305 library interface,
127 implementation is enabled, this implementation serves the users
[all …]
|
| /linux-6.15/Documentation/crypto/ |
| H A D | architecture.rst | 110 the implementation with the highest priority.
117 sure to refer to the intended cipher implementation.
136 - priority: the priority value of the cipher implementation
161 an ECDH or DH implementation
203 an ECDH or DH implementation
265 the AES-NI implementation, the CTR mode, the GHASH implementation and
275 crypto API for the cipher implementation type.
354 5. The GCM AEAD implementation also invokes the GHASH cipher
355 implementation via the AHASH API.
379 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-6.15/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-6.15/drivers/video/fbdev/nvidia/ |
| H A D | nv_setup.c | 230 u32 implementation = par->Chipset & 0x0ff0; in nv10GetConfig() local
261 if (par->twoHeads && (implementation != 0x0110)) { in nv10GetConfig()
275 u16 implementation = par->Chipset & 0x0ff0; in NVCommonSetup() local
312 (implementation != 0x0100) && in NVCommonSetup()
313 (implementation != 0x0150) && in NVCommonSetup()
314 (implementation != 0x01A0) && (implementation != 0x0200); in NVCommonSetup()
317 (implementation != 0x0110)); in NVCommonSetup()
319 par->twoStagePLL = (implementation == 0x0310) || in NVCommonSetup()
323 (implementation != 0x0100); in NVCommonSetup()
440 if (implementation != 0x0110) { in NVCommonSetup()
[all …]
|
| /linux-6.15/drivers/mailbox/ |
| H A D | Kconfig | 54 Mailbox implementation for i.MX Messaging Unit (MU).
70 An implementation of the ARM PL320 Interprocessor Communication
81 Mailbox implementation for communication with the the firmware
90 Mailbox implementation for OMAP family chips with hardware for
120 An implementation of the Altera Mailbox soft core. It is used
128 An implementation of the BCM2385 Mailbox. It is used to invoke
136 Mailbox implementation for STMicroelectonics family chips with
144 An implementation of Message Manager slave driver for Keystone
197 Mailbox implementation for Microchip devices with an
247 Mailbox implementation of the Broadcom FlexRM ring manager,
[all …]
|
| /linux-6.15/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.
274 handle_simple_irq provides a generic implementation for simple
289 handle_percpu_irq provides a generic implementation for per CPU
[all …]
|
| H A D | union_find.rst | 43 This document covers use of the Linux union-find implementation. For more
44 information on the nature and implementation of union-find, see:
49 Linux implementation of union-find
52 Linux's union-find implementation resides in the file "lib/union_find.c".
|
| /linux-6.15/Documentation/virt/kvm/arm/ |
| H A D | hypercalls.rst | 148 Request the target CPU implementation version information and the number of target
178 Request the target CPU implementation information for the Guest VM. The Guest kernel
188 | Arguments: | (uint64) | R1 | selected implementation index |
198 | | (uint64) | R1 | MIDR_EL1 of the selected implementation |
200 | | (uint64) | R2 | REVIDR_EL1 of the selected implementation |
202 | | (uint64) | R3 | AIDR_EL1 of the selected implementation |
|
| /linux-6.15/arch/openrisc/ |
| H A 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
136 Select this if your implementation has support for the Class II
149 Select this if your implementation has support for the Class II
162 Select this if your implementation has support for the Class II
175 Select this if your implementation has support for the Class II
|
| /linux-6.15/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
|
| H A D | sctp.rst | 8 implementation.
21 The initial project goal is to create an Linux kernel reference implementation
33 implementation and testing lksctp on IPv4.
|
| /linux-6.15/net/nsh/ |
| H A D | Kconfig | 6 Network Service Header is an implementation of Service Function
7 Chaining (RFC 7665). The current implementation in Linux supports
|
| /linux-6.15/Documentation/filesystems/bcachefs/ |
| H A D | index.rst | 20 Filesystem implementation
23 Documentation for filesystem features and their implementation details.
|
| /linux-6.15/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-6.15/arch/arm/crypto/ |
| H A D | Kconfig | 34 Use an implementation of GHASH (used by the GCM AEAD chaining mode)
69 BLAKE2b, but slower than the NEON implementation of BLAKE2b.
70 There is no NEON implementation of BLAKE2s, since NEON doesn't
85 Crypto Extensions, typically this BLAKE2b implementation is
161 fastest AES implementation for single blocks. For multiple
162 blocks, the NEON bit-sliced implementation is usually faster.
164 This implementation may be vulnerable to cache timing attacks,
|
| /linux-6.15/Documentation/driver-api/media/drivers/ |
| H A D | rkisp1.rst | 31 - V12 supports a new CSI-host implementation but can still
32 also use the same implementation from V10
43 - V13 does not support the old CSI-host implementation anymore
|
| /linux-6.15/Documentation/userspace-api/media/dvb/ |
| H A D | legacy_dvb_apis.rst | 17 code implementation, as this section of the document was written
19 implementation.
|
| /linux-6.15/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-6.15/net/nfc/hci/ |
| H A D | Kconfig | 4 tristate "NFC HCI implementation"
8 implementation. This is mostly needed for devices that only process
|
| /linux-6.15/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-6.15/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-6.15/lib/vdso/ |
| H A D | Kconfig | 11 This is a generic implementation of gettimeofday vdso.
13 provide the fallback implementation.
|
| /linux-6.15/Documentation/devicetree/bindings/nios2/ |
| H A D | nios2.txt | 35 - altr,implementation: Nios II core implementation, this should be "fast";
50 altr,implementation = "fast";
|
| /linux-6.15/Documentation/bpf/ |
| H A D | clang-notes.rst | 5 Clang implementation notes
8 This document provides more details specific to the Clang/LLVM implementation of the eBPF instructi…
|