| /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/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/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/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/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/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/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/lib/vdso/ |
| H A D | Kconfig | 10 This is a generic implementation of gettimeofday vdso.
12 provide the fallback implementation.
|
| /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/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/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/nfc/hci/ |
| H A D | Kconfig | 4 tristate "NFC HCI implementation"
8 implementation. This is mostly needed for devices that only process
|
| /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/crypto/ |
| 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/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/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…
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-reload.rst | 43 implementation might require to perform another action alongside with
51 By default reload actions are not limited and driver implementation may
55 implementation to specific constraints.
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | nfs41-server.rst | 21 The NFSv4 minorversion 1 (NFSv4.1) implementation in nfsd is based
24 From the many new features in NFSv4.1 the current implementation
33 are not supported yet by the linux server implementation.
41 The following abbreviations indicate the linux server implementation status.
242 implementation ids are ignored
|
| /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
106 to be requeued to a PI-aware futex. The implementation is the
|
| /linux/Documentation/virt/kvm/devices/ |
| H A D | arm-vgic.rst | 64 GICD_IIDR.Revision is updated when the KVM implementation of an emulated
67 confirm its expected behavior is aligned with the KVM implementation.
95 The Active Priorities Registers APRn are implementation defined, so we set a
96 fixed format for our implementation that fits with the model of a "GICv2
97 implementation without the security extensions" which we present to the
|
| /linux/Documentation/driver-api/iio/ |
| H A 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/drivers/firmware/qcom/ |
| H A D | Kconfig | 14 backends plugged in whether it's an SCM implementation or a proper
15 TEE bus based PAS service implementation.
25 by the firmware TEE implementation as the backend.
|