| /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/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()
320 (implementation == 0x0340) || (par->Architecture >= NV_ARCH_40); in NVCommonSetup()
323 (implementation != 0x0100); in NVCommonSetup()
[all …]
|
| /linux/drivers/mailbox/ |
| H A D | Kconfig | 43 Mailbox driver implementation for ASPEED AST27XX SoCs. This driver
52 Mailbox driver implementation for Sophgo CV18XX SoCs. This driver
73 Mailbox implementation for i.MX Messaging Unit (MU).
89 An implementation of the ARM PL320 Interprocessor Communication
100 Mailbox implementation for communication with the the firmware
109 Mailbox implementation for OMAP family chips with hardware for
139 An implementation of the Altera Mailbox soft core. It is used
147 An implementation of the BCM2385 Mailbox. It is used to invoke
155 Mailbox implementation for STMicroelectonics family chips with
163 An implementation of Message Manager slave driver for Keystone
[all …]
|
| /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/drivers/dpll/zl3073x/ |
| H A D | Kconfig | 18 tristate "I2C bus implementation for Microchip Azurite devices"
23 This is I2C bus implementation for Microchip Azurite DPLL/PTP/SyncE
30 tristate "SPI bus implementation for Microchip Azurite devices"
35 This is SPI bus implementation for Microchip Azurite DPLL/PTP/SyncE
|
| /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 …]
|
| 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/drivers/iommu/generic_pt/ |
| H A D | Kconfig | 29 IOMMU_PT provides an implementation of the page table operations
31 implementation of the page table operations that can be shared by
39 iommu_domain implementation for the AMD v1 page table. AMDv1 is the
49 iommu_domain implementation for the Intel VT-d's 64 bit 3/4/5
59 iommu_domain implementation for the x86 64-bit 4/5 level page table.
|
| /linux/arch/openrisc/ |
| H A D | Kconfig | 93 Select this if your implementation features write through data caches.
110 Select this if your implementation has the Class II instruction l.ff1
116 Select this if your implementation has the Class II instruction l.fl1
122 Select this if your implementation has a hardware multiply instruction
128 Select this if your implementation has a hardware divide instruction
138 Select this if your implementation has support for the Class II
151 Select this if your implementation has support for the Class II
164 Select this if your implementation has support for the Class II
177 Select this if your implementation has support for the Class II
|
| /linux/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/drivers/gpu/drm/display/ |
| H A D | Kconfig | 23 DRM connector implementation terminating DRM bridge chains.
84 implementation).
89 DRM display helpers for HDMI CEC implementation.
94 DRM display helpers for HDMI CEC notifiers implementation.
|
| /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
|
| 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/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/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
|
| H A D | generic_pt.rst | 27 format headers and the generic code for the implementation. For instance in an
28 implementation compilation unit the headers would normally be included as
39 #include "../iommu_pt.h" /* The IOMMU implementation */
46 IOMMU implementation uses multi-compilation to generate per-format ops structs
60 The implementation will further wrap struct pt_common in its own top-level
91 where a uniquely named per-format inline function provides the implementation
|
| /linux/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/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/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/lib/vdso/ |
| H A D | Kconfig | 11 This is a generic implementation of gettimeofday vdso.
13 provide the fallback implementation.
|
| /linux/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/net/nfc/hci/ |
| H A D | Kconfig | 4 tristate "NFC HCI implementation"
8 implementation. This is mostly needed for devices that only process
|
| /linux/Documentation/ABI/testing/ |
| H A D | configfs-tsm-report | 16 options The format of the report is implementation specific
17 where the implementation is conveyed via the @provider
97 (WO) Attribute is visible if a TSM implementation provider
117 (WO) Attribute is visible if a TSM implementation provider
134 (WO) Attribute is visible if a TSM implementation provider
152 (WO) Attribute is visible if a TSM implementation provider
|
| /linux/Documentation/devicetree/bindings/nios2/ |
| H A D | nios2.txt | 35 - altr,implementation: Nios II core implementation, this should be "fast";
50 altr,implementation = "fast";
|