| /Linux-v5.4/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-v5.4/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-v5.4/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 …]
|
| /Linux-v5.4/drivers/video/fbdev/nvidia/ |
| D | nv_setup.c | 233 u32 implementation = par->Chipset & 0x0ff0; in nv10GetConfig() local
264 if (par->twoHeads && (implementation != 0x0110)) { in nv10GetConfig()
278 u16 implementation = par->Chipset & 0x0ff0; in NVCommonSetup() local
315 (implementation != 0x0100) && in NVCommonSetup()
316 (implementation != 0x0150) && in NVCommonSetup()
317 (implementation != 0x01A0) && (implementation != 0x0200); in NVCommonSetup()
320 (implementation != 0x0110)); in NVCommonSetup()
322 par->twoStagePLL = (implementation == 0x0310) || in NVCommonSetup()
323 (implementation == 0x0340) || (par->Architecture >= NV_ARCH_40); in NVCommonSetup()
326 (implementation != 0x0100); in NVCommonSetup()
[all …]
|
| /Linux-v5.4/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)
|
| /Linux-v5.4/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
|
| D | sctp.txt | 4 implementation.
17 The initial project goal is to create an Linux kernel reference implementation
28 implementation and testing lksctp on IPv4.
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/net/nsh/ |
| D | Kconfig | 6 Network Service Header is an implementation of Service Function
7 Chaining (RFC 7665). The current implementation in Linux supports
|
| /Linux-v5.4/lib/vdso/ |
| D | Kconfig | 11 This is a generic implementation of gettimeofday vdso.
13 provide the fallback implementation.
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | men-chameleon-bus.rst | 9 1.2 Limitations of the current implementation
26 This document describes the architecture and implementation of the MEN
33 implementation and does by no means describe the complete possibilities of MCB
36 Limitations of the current implementation
39 The current implementation is limited to PCI and PCIe based carrier devices
68 not handled by the MCB implementation.
97 The current implementation assigns exactly one memory and one IRQ resource
|
| /Linux-v5.4/net/nfc/hci/ |
| D | Kconfig | 4 tristate "NFC HCI implementation"
8 implementation. This is mostly needed for devices that only process
|
| /Linux-v5.4/arch/openrisc/ |
| D | Kconfig | 84 Select this if your implementation features write through data caches.
101 Select this if your implementation has the Class II instruction l.ff1
107 Select this if your implementation has the Class II instruction l.fl1
113 Select this if your implementation has a hardware multiply instruction
119 Select this if your implementation has a hardware divide instruction
|
| /Linux-v5.4/drivers/net/ethernet/mellanox/mlxsw/ |
| D | Kconfig | 32 tristate "PCI bus implementation for Mellanox Technologies Switch ASICs"
36 This is PCI bus implementation for Mellanox Technologies Switch ASICs.
42 tristate "I2C bus implementation for Mellanox Technologies Switch ASICs"
46 This is I2C bus implementation for Mellanox Technologies Switch ASICs.
|
| /Linux-v5.4/drivers/staging/iio/Documentation/ |
| D | ring.txt | 5 specific information on a given buffer implementation, see the
7 implementation to be selected at compile time via Kconfig options.
9 A given buffer implementation typically embeds a struct
|
| /Linux-v5.4/Documentation/devicetree/bindings/nios2/ |
| D | nios2.txt | 35 - altr,implementation: Nios II core implementation, this should be "fast";
50 altr,implementation = "fast";
|
| /Linux-v5.4/Documentation/virt/kvm/devices/ |
| D | arm-vgic.txt | 53 GICD_IIDR.Revision is updated when the KVM implementation of an emulated
56 confirm its expected behavior is aligned with the KVM implementation.
78 The Active Priorities Registers APRn are implementation defined, so we set a
79 fixed format for our implementation that fits with the model of a "GICv2
80 implementation without the security extensions" which we present to the
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | nfs41-server.txt | 19 The NFSv4 minorversion 1 (NFSv4.1) implementation in nfsd is based
22 From the many new features in NFSv4.1 the current implementation
31 are not supported yet by the linux server implementation.
38 The following abbreviations indicate the linux server implementation status.
159 * implementation ids are ignored
|
| /Linux-v5.4/Documentation/ |
| D | futex-requeue-pi.txt | 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
106 to be requeued to a PI-aware futex. The implementation is the
|
| /Linux-v5.4/Documentation/driver-api/iio/ |
| D | hw-consumer.rst | 7 software buffer for data. The implementation can be found under
21 As standard IIO device the implementation is based on IIO provider/consumer.
|
| /Linux-v5.4/Documentation/devicetree/bindings/interrupt-controller/ |
| D | sifive,plic-1.0.0.txt | 4 SiFive SOCs include an implementation of the Platform-Level Interrupt Controller
26 "sifive,plic-1.0.0" device is a concrete implementation of the PLIC that
32 detailed implementation in case that specific bugs need to be worked around.
|
| /Linux-v5.4/Documentation/media/uapi/dvb/ |
| D | legacy_dvb_apis.rst | 29 code implementation, as this section of the document was written
31 implementation.
|
| /Linux-v5.4/Documentation/arm/ |
| 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-v5.4/drivers/staging/media/omap4iss/ |
| D | TODO | 2 * Replace dummy resizer code with a real implementation
|
