| /linux-4.4.14/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.
|
| D | Overview.txt | 26 on the implementation details and specific support.
|
| /linux-4.4.14/Documentation/cgroups/ |
| 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.
|
| D | devices.txt | 108 4.1 Hierarchy (internal implementation)
113 implementation. Removal or addition of exceptions that will reduce the access
|
| /linux-4.4.14/drivers/video/fbdev/nvidia/ |
| D | nv_setup.c | 257 u32 implementation = par->Chipset & 0x0ff0; in nv10GetConfig() local
287 if (par->twoHeads && (implementation != 0x0110)) { in nv10GetConfig()
301 u16 implementation = par->Chipset & 0x0ff0; in NVCommonSetup() local
338 (implementation != 0x0100) && in NVCommonSetup()
339 (implementation != 0x0150) && in NVCommonSetup()
340 (implementation != 0x01A0) && (implementation != 0x0200); in NVCommonSetup()
343 (implementation != 0x0110)); in NVCommonSetup()
345 par->twoStagePLL = (implementation == 0x0310) || in NVCommonSetup()
346 (implementation == 0x0340) || (par->Architecture >= NV_ARCH_40); in NVCommonSetup()
349 (implementation != 0x0100); in NVCommonSetup()
[all …]
|
| /linux-4.4.14/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.
|
| D | ieee802154.txt | 2 Linux IEEE 802.15.4 implementation
13 The linux-wpan project goal is to provide a complete implementation
114 6LoWPAN Linux implementation
130 used in this Linux implementation.
|
| D | ipsec.txt | 25 is implementation dependent.
27 Current IPComp implementation is indeed by the book, while as in practice
|
| D | vxlan.txt | 11 device, there is also a separate implementation of VXLAN for
30 the IANA-assigned value of 4789. The Linux implementation of VXLAN
|
| D | dccp.txt | 24 implementation, this is the TCP-like CCID2 (RFC 4341). Additional CCIDs, such as
37 The Linux DCCP implementation does not currently support all the features that are
43 For more up-to-date versions of the DCCP implementation, please consider using
|
| D | altera_tse.txt | 100 o altera_msgdma.h: MSGDMA implementation function definitions
101 o altera_sgdma.h: SGDMA implementation function definitions
102 o altera_msgdma.c: MSGDMA implementation
103 o altera_sgdma.c: SGDMA implementation
|
| D | i40e.txt | 50 The driver supports the in-kernel software implementation of GRO. GRO has
|
| D | 00-INDEX | 104 - Linux IEEE 802.15.4 implementation, API and drivers
192 - Notes on the Linux kernel implementation of the SCTP protocol.
|
| D | PLIP.txt | 60 The Linux PLIP driver is an implementation of the original Crynwr protocol,
131 bits with standard status register implementation.
|
| /linux-4.4.14/drivers/mailbox/ |
| D | Kconfig | 22 An implementation of the ARM PL320 Interprocessor Communication
32 Mailbox implementation for OMAP family chips with hardware for
62 An implementation of the Altera Mailbox soft core. It is used
70 An implementation of the BCM2385 Mailbox. It is used to invoke
78 Mailbox implementation for STMicroelectonics family chips with
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | 00-INDEX | 4 - CPU Scheduler implementation hints for architecture specific code.
8 - goals, design and implementation of the Completely Fair Scheduler.
|
| D | sched-arch.txt | 1 CPU Scheduler implementation hints for architecture specific code
18 penalty to the core scheduler implementation in the CONFIG_SMP case.
|
| /linux-4.4.14/net/nfc/hci/ |
| D | Kconfig | 3 tristate "NFC HCI implementation"
7 implementation. This is mostly needed for devices that only process
|
| /linux-4.4.14/Documentation/ |
| D | men-chameleon-bus.txt | 8 1.2 Limitations of the current implementation
24 This document describes the architecture and implementation of the MEN
30 implementation and does by no means describe the complete possibilities of MCB
33 1.2 Limitations of the current implementation
35 The current implementation is limited to PCI and PCIe based carrier devices
60 not handled by the MCB implementation.
86 The current implementation assigns exactly one memory and one IRQ resource
|
| D | futex-requeue-pi.txt | 15 Without requeue_pi, the glibc implementation of
19 implementation would wake the highest-priority waiter, and leave the
55 user space already holding the PI futex. The glibc implementation
80 The actual glibc implementation will likely test for PI and make the
105 to be requeued to a PI-aware futex. The implementation is the
|
| D | clk.txt | 20 is a common implementation of the clk.h api, defined in
22 are invoked by the clk api implementation.
29 implementation of that code. Likewise, references to struct clk_foo
30 serve as a convenient shorthand for the implementation of the
96 vice versa. To illustrate consider the simple gateable clk implementation in
264 framework functions from within its implementation of clock operations. This
|
| D | vgaarbiter.txt | 27 I.3 xf86VGAArbiter (X server implementation)
82 types in the future, even if the current kernel implementation doesn't.
87 supports stacking, like the kernel one. This complexifies the implementation
167 I.3 xf86VGAArbiter (X server implementation)
182 implementation of the user space side [3]. Now (2009) Tiago Vignatti and Dave
|
| D | smsc_ece1099.txt | 40 The ECE1099 device SMBus implementation is a subset of the
42 The implementation in the device is a subset of SMBus since it
|
| D | sysfs-rules.txt | 3 The kernel-exported sysfs exports internal kernel implementation details
23 implementation details in its own API. Therefore it is not better than
41 kernel implementation details which should not be expected by
84 Everything else is just a kernel driver-core implementation detail
167 the error handling implementation within the kernel.
|
| D | rbtree.txt | 32 This document covers use of the Linux rbtree implementation. For more
33 information on the nature and implementation of Red Black Trees, see:
41 Linux implementation of red-black trees
44 Linux's rbtree implementation lives in the file "lib/rbtree.c". To use it,
47 The Linux rbtree implementation is optimized for speed, and thus has one
211 such implementation details.
|
| D | pi-futex.txt | 13 - the in-kernel PI implementation is streamlined around the mutex
14 abstraction, with strict rules that keep the implementation
54 implementation to user-space.
|
| D | adding-syscalls.txt | 173 - The core implementation of the system call, together with prototypes,
174 generic numbering, Kconfig changes and fallback stub implementation.
215 The file kernel/sys_ni.c provides a fallback stub implementation of each system
262 For most system calls the same 64-bit implementation can be invoked even when
291 SYSCALL_DEFINEn. This version of the implementation runs as part of a 64-bit
295 them call a common inner implementation function.)
390 To allow for this, the kernel implementation of the system call may need to
414 implementation is not common with the x86_64 version, then its syscall
420 doesn't include arch/x86/entry/entry_64.S implementation (because UML
489 implementation paths in detail for v3.14:
|
| D | atomic_ops.txt | 213 If the atomic instructions used in an implementation provide explicit
310 implementation could legally allow the atomic counter update visible
314 atomic_t implementation above can have disastrous results. Here is
476 The implementation of test_and_set_bit() must guarantee that
527 expensive non-atomic operations may be used in the implementation.
552 1) When acquiring a lock, the implementation must make it globally
555 2) When releasing a lock, the implementation must make it such that
|
| D | hwspinlock.txt | 242 - to be called from the underlying platform-specific implementation, in
249 - to be called from the underlying vendor-specific implementation, in order
260 implementation using the hwspin_lock_register() API.
316 spinning on a lock, and can be used by the underlying implementation to force
|
| D | remoteproc.txt | 116 This is called by the platform-specific rproc implementation, whenever
129 implementation decides to remove the rproc device. it should
141 platform specific rproc implementation. This should not be called from a
162 Every remoteproc implementation should at least provide the ->start and ->stop
|
| D | irqflags-tracing.txt | 45 implementation in an architecture: lockdep will detect that and will
|
| D | init.txt | 46 - try to make the implementation itself more helpful in general,
|
| D | phy.txt | 28 the PHY, the framework provides its own implementation of of_xlate in
30 should provide its own implementation of of_xlate. of_xlate is used only for
|
| D | lzo.txt | 62 in this implementation. This number of immediate literals to be copied is
74 an implementation design choice independant on the algorithm or encoding.
|
| D | memory-hotplug.txt | 31 Note(1): x86_64's has special implementation for memory hotplug.
238 not called (in current implementation). You'll have to online memory by
300 In the current implementation, Linux's memory offline uses method (2), freeing
355 Need more implementation yet....
|
| D | io-mapping.txt | 65 The initial implementation of these functions uses existing mapping
|
| D | mailbox.txt | 16 Some of the choices made during implementation are the result of this
|
| /linux-4.4.14/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-4.4.14/arch/openrisc/ |
| D | Kconfig | 82 Select this if your implementation has the Class II instruction l.ff1
88 Select this if your implementation has the Class II instruction l.fl1
94 Select this if your implementation has a hardware multiply instruction
100 Select this if your implementation has a hardware divide instruction
|
| /linux-4.4.14/Documentation/devicetree/bindings/nios2/ |
| D | nios2.txt | 35 - altr,implementation: Nios II core implementation, this should be "fast";
50 altr,implementation = "fast";
|
| /linux-4.4.14/Documentation/thermal/ |
| D | cpu-cooling-api.txt | 85 For a given processor implementation the primary factors are:
107 implementation specific processor support and characterisation
108 factors. Therefore, in initial implementation that contribution is
127 given circuit implementation the primary factors are:
148 Circuit implementation specific factors include the chosen silicon
164 However, since both implementation specific and complex relationships
193 dynamic power is highly dependent on implementation. Given the
194 potential complexity in implementation, the importance and accuracy of
|
| D | exynos_thermal | 73 thresholds. It invokes core thermal implementation with the call
|
| /linux-4.4.14/drivers/net/ethernet/mellanox/mlxsw/ |
| D | Kconfig | 14 tristate "PCI bus implementation for Mellanox Technologies Switch ASICs"
18 This is PCI bus implementation for Mellanox Technologies Switch ASICs.
|
| /linux-4.4.14/arch/arm/crypto/ |
| D | Kconfig | 95 Use a faster and more secure NEON based implementation of AES in CBC,
101 This implementation does not rely on any lookup tables so it is
110 Use an implementation of AES in CBC, CTR and XTS modes that uses
119 Use an implementation of GHASH (used by the GCM AEAD chaining mode)
|
| /linux-4.4.14/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
|
| D | Exporting | 18 The mechanism discussed here allows each filesystem implementation to
104 A file system implementation declares that instances of the filesystem
112 implementation creates a filehandle fragment that encodes a 32bit inode
137 supplied, a default implementation is provided which uses vfs_readdir
|
| D | 00-INDEX | 12 - info on the Linux server implementation of NFSv4 minor version 1.
|
| /linux-4.4.14/Documentation/arm/ |
| D | vlocks.txt | 118 ARM implementation
121 The current ARM implementation [2] contains some optimisations beyond
129 In the ARM implementation, this means that we can use a single load
158 implementation uses a simple loop of word-sized loads for this
165 implementation.
170 implementation removes many of the barriers which would be required
|
| D | uefi.txt | 22 The implementation depends on receiving information about the UEFI environment
|
| D | kernel_user_helpers.txt | 17 implementation, however a VDSO would prevent some assembly tricks with
25 the implementation of a library call) when optimizing for a recent enough
|
| /linux-4.4.14/Documentation/power/ |
| D | 00-INDEX | 40 - Goals, implementation, and usage of software suspend (ACPI S3)
44 - Experimental implementation of software suspend in userspace
|
| D | opp.txt | 68 OPP library facilitates this concept in it's implementation. The following
100 The SoC implementation calls dev_pm_opp_add function iteratively to add OPPs per
179 Example 2: A simplified implementation of a SoC cpufreq_driver->target:
208 implementation might choose to do something as follows:
223 exceeds a threshold value. The SoC framework implementation might
340 nature of the device and it's implementation is left to the user of
|
| D | apm-acpi.txt | 12 enabled by default). If a working ACPI implementation is found, the
|
| /linux-4.4.14/drivers/staging/media/omap4iss/ |
| D | TODO | 2 * Replace dummy resizer code with a real implementation
|
| /linux-4.4.14/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 21 The implementation of CAIF is divided into:
63 The Core CAIF implementation contains:
64 - Simple implementation of CAIF.
84 The CAIF Protocol implementation contains:
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei-client-bus.txt | 23 A driver implementation for an MEI Client is very similar to existing bus
53 will trigger an event handler call and the driver implementation is supposed
120 The handler implementation will typically call some I/O routine depending on
|
| /linux-4.4.14/Documentation/timers/ |
| D | hrtimers.txt | 36 - the implementation of the current posix-timer subsystem on top of
78 hrtimer subsystem implementation details
106 implementation needed to keep an extra list of all armed absolute
112 scaling code from the posix-timer implementation - the clock can simply
152 the hrtimer implementation details in praxis, and we also ran the posix
175 hrtimers-based high-resolution clock implementation, so the hrtimers
|
| D | timekeeping.txt | 113 may not provide an implementation of sched_clock() on its own. If a local
114 implementation is not provided, the system jiffy counter will be used as
132 If an architecture does not provide its own implementation of this function,
|
| D | highres.txt | 33 the base implementation are covered in Documentation/timers/hrtimers.txt. See
188 and calls update_process_times and profiling. The implementation of the hrtimer
237 The implementation leaves room for further development like full tickless
|
| /linux-4.4.14/scripts/ |
| D | spelling.txt | 490 impelentation||implementation
492 implemantation||implementation
493 implemenation||implementation
494 implementaiton||implementation
496 implemention||implementation
497 implemetation||implementation
498 implemntation||implementation
499 implentation||implementation
500 implmentation||implementation
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu.txt | 3 ARM SoCs may contain an implementation of the ARM System Memory
20 depending on the particular implementation and/or the
|
| D | renesas,ipmmu-vmsa.txt | 3 The IPMMU is an IOMMU implementation compatible with the ARM VMSA page tables.
|
| D | arm,smmu-v3.txt | 13 implementation. This entry should be last in the
|
| /linux-4.4.14/kernel/irq/ |
| D | Kconfig | 16 # Use the generic /proc/interrupts implementation
53 # Generic configurable interrupt chip implementation
|
| /linux-4.4.14/Documentation/virtual/kvm/devices/ |
| D | arm-vgic.txt | 77 The Active Priorities Registers APRn are implementation defined, so we set a
78 fixed format for our implementation that fits with the model of a "GICv2
79 implementation without the security extensions" which we present to the
|
| /linux-4.4.14/tools/power/cpupower/ |
| D | ToDo | 4 (current implementation has issues on AMD)
|
| D | README | 17 allows for code reduction in userspace tools, a clean implementation of
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | CPUfreq.txt | 14 how the clocks are arranged. The first implementation used as single
16 and muxes and this is the implementation that is documented here. A
|
| D | USB-Host.txt | 53 descriptions of the platform device data. An implementation
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.pvrusb2 | 29 1a. Low level wire-protocol implementation with the device.
31 1b. I2C adaptor implementation and corresponding I2C client drivers
34 1c. High level hardware driver implementation which coordinates all
53 implementation and interface isolated from each other. Thus while
115 implementation had to be completely different.
155 pvrusb2-i2c-core.[ch] - This module provides an implementation of a
|
| D | videobuf | 14 a consistent implementation of the V4L2 user-space API.
136 videobuf calls into the implementation of the other driver callbacks. The
197 typical driver read() implementation will start the capture engine, call
199 smarter implementation might leave the engine running for a little while in
213 V4L2 drivers, the often-complex mmap() implementation simplifies to a
304 The final part of a videobuf implementation has no direct callback - it's
|
| /linux-4.4.14/Documentation/devicetree/bindings/timer/ |
| D | renesas,tpu.txt | 5 This implementation support only cascade mode.
|
| /linux-4.4.14/drivers/cpuidle/ |
| D | Kconfig.mips | 17 also using the CONFIG_MIPS_CPS SMP implementation.
|
| /linux-4.4.14/Documentation/locking/ |
| D | 00-INDEX | 10 - description of the RealTime mutex implementation design.
|
| D | locktorture.txt | 41 o "lock_busted": Simulates a buggy lock implementation.
128 implementation. Otherwise a lock should never fail (i.e., spin_lock()).
|
| /linux-4.4.14/drivers/staging/wilc1000/ |
| D | TODO | 14 - use wext-core handling instead of private SIOCSIWPRIV implementation
|
| /linux-4.4.14/net/mac802154/ |
| D | Kconfig | 15 Note: this implementation is neither certified, nor feature
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | st-spear-miphy.txt | 15 present on a implementation.
|
| /linux-4.4.14/arch/h8300/lib/ |
| D | mulsi3.S | 2 ; mulsi3 for H8/300H - based on Renesas SH implementation
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | mmc-card.txt | 14 implementation, and that hpi should not be used
|
| D | samsung-sdhci.txt | 6 Samsung implementation of the SDHCI controller.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | global_timer.txt | 10 timers or any compatible implementation. Note: driver
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-log.txt | 27 This log implementation commits the log state to disk. This way, the
32 This log implementation keeps the log state in memory. The log state
|
| D | thin-provisioning.txt | 7 The main highlight of this implementation, compared to the previous
8 implementation of snapshots, is that it allows many virtual devices to
14 previous implementation of snapshots did this by chaining together
16 implementation uses a single data structure to avoid this degradation
|
| D | persistent-data.txt | 8 - Mikulas Patocka's multisnap implementation
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | 00-INDEX | 14 - info on a TCP implementation of a network block device.
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/can/ |
| D | fsl-flexcan.txt | 7 An implementation should also claim any of the following compatibles
|
| /linux-4.4.14/Documentation/blockdev/drbd/ |
| D | README.txt | 10 The here included files are intended to help understand the implementation
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | iskeleton.S | 161 | Entry point for the selected cas emulation code implementation.
162 | If the implementation provided by the 68060ISP is sufficient,
172 | Entry point for the selected cas2 emulation code implementation.
173 | If the implementation provided by the 68060ISP is sufficient,
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 8 with the non-spec compliant or1200 type implementation.
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
| D | l3-noc.txt | 3 This version is an implementation of the generic NoC IP
|
| /linux-4.4.14/drivers/net/can/mscan/ |
| D | Kconfig | 7 implementation of the Motorola Scalable CAN concept targeted for
|
| /linux-4.4.14/fs/efs/ |
| D | Kconfig | 9 This implementation only offers read-only access. If you don't know
|
| /linux-4.4.14/drivers/hwtracing/coresight/ |
| D | Kconfig | 30 complies with the generic implementation of the component without
49 that complies with the generic implementation of the component without
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | autofs4-mount-control.txt | 31 because autofs direct mounts and the implementation of "on demand mount
100 somewhat more detail to the implementation but it isn't needed for the
105 The current autofs implementation uses an ioctl file descriptor opened
134 ENOENT so the re-implementation allows user space to send an actual
143 ioctl mechanism in favor of systems such as Netlink. An implementation
150 message bus implementation rather than specifically an ioctl replacement.
162 mount at a time. A Generic Netlink implementation would exclude this
224 An example of an implementation which uses this interface can be seen
236 implementation. It requires an initialized struct autofs_dev_ioctl as an
266 completeness and to provide for a consistent user space implementation.
|
| D | befs.txt | 8 implementation is neither complete nor well-tested.
36 implementation.
|
| D | 00-INDEX | 8 - 9p (v9fs) is an implementation of the Plan 9 remote fs protocol.
95 - info on the Linux implementation of Sys V mandatory file locking.
|
| D | relay.txt | 273 The create_buf_file() implementation can also be defined in such a way
281 implementation should set the value of the is_global outparam to a
311 'no-overwrite'. The mode is entirely determined by the implementation
341 an implementation of the subbuf_start() callback something like the
372 The implementation of the subbuf_start() callback for 'overwrite' mode
394 The default subbuf_start() implementation, used if the client doesn't
405 subbuf_start() implementation; the padding value for the previous
|
| D | 9p.txt | 7 v9fs is a Unix implementation of the Plan 9 9p remote filesystem protocol.
15 The best detailed explanation of the Linux implementation and applications of
|
| D | bfs.txt | 55 implementation please contact the author:
|
| D | sysfs.txt | 46 With the current sysfs implementation the kobject reference count is
233 A very simple (and naive) implementation of a device attribute is:
252 (Note that the real implementation doesn't allow userspace to set the
|
| D | cramfs.txt | 76 See fs/cramfs/README for filesystem layout and implementation notes.
|
| D | ext2.txt | 183 The current implementation of ext2 uses a singly-linked list to store
187 The current implementation never removes empty directory blocks once they
285 It is frequently claimed that the ext2 implementation of writing
304 limits are imposed by the current implementation of the kernel code.
329 with the current linear linked-list directory implementation. This limit
|
| D | mandatory-locking.txt | 11 The Linux implementation is prey to a number of difficult-to-fix race
92 O_TRUNC flag set should be rejected. The Linux implementation follows the SVID
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-error-recovery.txt | 51 The biggest reason for choosing a kernel-based implementation rather
52 than a user-space implementation was the need to deal with bus
67 Design and implementation details below, based on a chain of
74 arch/powerpc implementation will simulate a PCI hotplug remove/add.
164 >>> The current powerpc implementation assumes that a device driver will
166 >>> implementation uses one kernel thread to notify all devices;
169 >>> recovery implementation (e.g. waiting for all notification threads
173 >>> The current powerpc implementation doesn't much care if the device
253 >>> The current powerpc implementation does not implement this callback.
336 >>> The current powerpc implementation does not try a power-cycle
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ux500/ |
| D | power_domain.txt | 6 The implementation of PM domains for UX500 are based upon the generic PM domain
|
| /linux-4.4.14/Documentation/laptops/ |
| D | disk-shock-protection.txt | 80 There is a technical detail of this implementation that may cause some
131 of pointers at different projects aiming at an implementation of shock
145 This implementation of disk head parking has been inspired by a patch
147 to develop an implementation of this feature that is fit to be merged
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-omap.txt | 17 Note: Current implementation will fetch base address, irq and dma
|
| D | i2c-opal.txt | 22 and depend on the specific hardware implementation. The example below depicts
|
| /linux-4.4.14/net/ax25/ |
| D | TODO | 13 the race caused by the static variable in it's previous implementation.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | nand.txt | 19 The interpretation of these parameters is implementation-defined, so not all
|
| D | gpmi-nand.txt | 26 the software may chooses an implementation-defined
|
| /linux-4.4.14/Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 12 driver implementation may support the following properties:
|
| /linux-4.4.14/drivers/staging/nvec/ |
| D | README | 3 This is an implementation of the NVEC protocol used to communicate with an
|
| /linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
| D | qcom-spmi-temp-alarm.txt | 4 that utilize the Qualcomm SPMI implementation. These peripherals provide an
|
| /linux-4.4.14/fs/autofs4/ |
| D | Kconfig | 5 on demand. This implementation is partially kernel-based to reduce
|
| /linux-4.4.14/scripts/coccinelle/api/ |
| D | memdup_user.cocci | 1 /// Use memdup_user rather than duplicating its implementation
|
| D | memdup.cocci | 1 /// Use kmemdup rather than duplicating its implementation
|
| D | kstrdup.cocci | 1 /// Use kstrdup rather than duplicating its implementation
|
| /linux-4.4.14/Documentation/devicetree/bindings/usb/ |
| D | ci-hdrc-usb2.txt | 42 default of the hardware implementation will be used.
48 default of the hardware implementation will be used.
|
| /linux-4.4.14/drivers/crypto/ |
| D | Kconfig | 84 This is the s390 hardware accelerated implementation of the
94 This is the s390 hardware accelerated implementation of the
104 This is the s390 hardware accelerated implementation of the
116 This is the s390 hardware accelerated implementation of the
128 This is the s390 hardware accelerated implementation of the
157 This is the s390 hardware accelerated implementation of the
|
| /linux-4.4.14/crypto/ |
| D | Kconfig | 111 Generic implementation of the RSA public key algorithm.
147 Efficient table driven implementation of multiplications in the
348 key size 256, 384 or 512 bits. This implementation currently
417 support CRC32C implementation using hardware accelerated CRC32
420 gain performance compared with software implementation.
448 CRC32 PCLMULQDQ implementation using hardware accelerated PCLMULQDQ
451 and gain better performance as compared with the table implementation.
470 crct10dif checksum as compared with the generic table implementation.
485 in IETF protocols. This is the portable C implementation of Poly1305.
496 in IETF protocols. This is the x86_64 assembler implementation using SIMD
[all …]
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | dynamic-resolution-notes.txt | 4 This document describes the implementation of the in-kernel
|
| D | overlay-notes.txt | 4 This document describes the implementation of the in-kernel
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.fax | 16 NOTE: This implementation does *not* support fax with passive
|
| D | 00-INDEX | 2 - this file (info on ISDN implementation for Linux)
|
| D | README.x25 | 16 other side first. Be prepared that bugs in the protocol implementation
19 - This implementation has never wiped out my whole hard disk yet. But as
174 alpha-test implementation ("eftp4linux") of the EUROfile transfer
|
| D | CREDITS | 12 For X.25 implementation.
|
| D | README.syncppp | 42 You must disable BSD-compression, this implementation can't
|
| D | README.concap | 58 In order to support Linux' x25 PLP implementation on top of
70 synchronous ppp implementation used by the isdn driver and the
71 asynchronous ppp implementation used by the ppp driver have a lot of
|
| /linux-4.4.14/drivers/w1/slaves/ |
| D | Kconfig | 8 tristate "Thermal family implementation"
14 tristate "Simple 64bit memory family implementation"
|
| /linux-4.4.14/fs/nfs/ |
| D | Kconfig | 18 implementation is available via the nfs(5) man page.
141 This option defines the domain portion of the implementation ID that
156 The NFSv4.1 pieces of the Linux NFSv4 migration implementation are
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | ccf.txt | 6 that enables the implementation of coherent, multicore systems.
|
| D | cpus.txt | 22 the category is supported by the implementation.
|
| D | mpic-msgr.txt | 35 required, though. However, a particular implementation of this binding
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | nested-vmx.txt | 18 its implementation and its performance characteristics, in the OSDI 2010 paper
64 implementation for the a guest hypervisor to use. As such, the official
71 As a VMX implementation, nested VMX presents a VMCS structure to L1.
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | ipoib.txt | 3 The ib_ipoib driver is an implementation of the IP over InfiniBand
5 working group. It is a "native" implementation in the sense of
|
| D | core_locking.txt | 10 With the following exceptions, a low-level driver implementation of
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | TODO | 23 There are a couple of ways to approach the implementation of these. One
59 implementations: it is there to control the hardware in an implementation-
|
| D | README | 23 John Hauser. SoftFloat is a software implementation of floating-point
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | lm77 | 27 This implementation detail implies the following:
|
| D | emc1403 | 48 This implementation detail implies the following:
|
| D | smsc47m1 | 55 already have disappeared! Note that in the current implementation, all
|
| D | lm80 | 57 already have disappeared! Note that in the current implementation, all
|
| D | vt1211 | 82 implementation :-) You will have to find documentation for your own
116 temp1 and temp3-temp7, scaling depends on the board implementation and needs
|
| D | gl518sm | 68 implementation, all hardware registers are read whenever any data is read
|
| D | lm87 | 52 already have disappeared! Note that in the current implementation, all
|
| D | lm78 | 62 already have disappeared! Note that in the current implementation, all
|
| D | via686a | 60 already have disappeared! Note that in the current implementation, all
|
| /linux-4.4.14/drivers/acpi/acpica/ |
| D | psxface.c | 192 info->obj_desc->method.dispatch.implementation(walk_state); in acpi_ps_execute_method()
|
| D | acobject.h | 182 acpi_internal_method implementation; member
|
| D | nsaccess.c | 169 obj_desc->method.dispatch.implementation = in acpi_ns_root_initialize()
|
| /linux-4.4.14/Documentation/vm/ |
| D | userfaultfd.txt | 5 Userfaults allow the implementation of on-demand paging from userland
9 For example userfaults allows a proper and more optimal implementation
104 The implementation of postcopy live migration currently uses one
|
| D | remap_file_pages.txt | 16 It's only known that one enterprise RDBMS implementation uses the syscall
|
| D | cleancache.txt | 61 cleancache implementation can simply disable shared_init by always
94 A backend implementation may provide additional metrics.
155 initial implementation of cleancache didn't provide this hook.
175 The one-page-at-a-time copy semantics simplifies the implementation
194 The invalidate is done by the cleancache backend implementation.
|
| D | page_owner.txt | 51 There is one notice that is caused by implementation detail. page owner
|
| /linux-4.4.14/Documentation/scsi/ |
| D | osd.txt | 33 There are no current plans for an OSD target implementation in kernel. For all
51 osd_initiator.c OSD-Initiator library implementation
61 osd_initiator is a low level implementation of an osd initiator encoder.
|
| /linux-4.4.14/Documentation/gpio/ |
| D | driver.txt | 66 (like PM runtime) in its gpio_chip implementation (.get/.set and direction
82 (like PM runtime) as part of its irq_chip implementation on -RT.
233 - ensure spinlock_t is not used as part irq_chip implementation;
234 - ensure that sleepable APIs are not used as part irq_chip implementation.
244 GPIO IRQ chip implementation;
|
| /linux-4.4.14/arch/arm/plat-omap/ |
| D | Kconfig | 49 Say Y to enable Class 3 implementation of Smartreflex
51 Class 3 implementation of Smartreflex employs continuous hardware
|
| /linux-4.4.14/Documentation/i2c/ |
| D | ten-bit-addresses | 18 code (or it's there but not working properly.) Software implementation
|
| D | old-module-parameters | 13 longer needed, and that a centralized implementation was possible. The new,
|
| D | summary | 35 driver, or includes its own implementation.
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | amd-powernow.txt | 4 implementation changes in new generations of the processors,
|
| /linux-4.4.14/Documentation/RCU/ |
| D | RTFP.txt | 12 implementation. This works well in environments that have garbage
31 (In contrast, implementation of RCU is permitted only in software licensed
37 RCU implementation in DYNIX/ptx. In 1988, Barbara Liskov published
137 Later that year saw a paper describing an RCU implementation
139 Hugh Dickins [Dickins02a] and an implementation by Mingming Cao
157 sections proved elusive. An RCU implementation permitting general
183 2010 produced a simpler preemptible-RCU implementation
252 Describes concurrent AVL tree implementation. Uses a
285 Describes concurrent AVL tree implementation. Uses a
1063 implementation that make it friendly to realtime applications.
[all …]
|
| D | whatisRCU.txt | 36 understand the RCU implementation should focus on Section 5, then dive
187 readers are done, its implementation is key to RCU. For RCU
547 production-quality implementation, and see:
551 for papers describing the Linux kernel RCU implementation. The OLS'01
553 more details on the current implementation as of early 2004.
558 This section presents a "toy" RCU implementation that is based on
564 However, it is probably the easiest implementation to relate to, so is
626 This section presents a "toy" RCU implementation that is based on
650 The implementation of synchronize_rcu() simply schedules itself on each
653 "toy" implementation would restore the affinity upon completion rather
[all …]
|
| D | torture.txt | 65 synchronous RCU implementation (one for which a member of
143 RCU implementation supports priority boosting. Specifying
147 implementation does not support RCU priority boosting,
293 Different implementations of RCU can provide implementation-specific
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-firmware-gsmi | 22 underlying implementation as /sys/firmware/efi/vars.
|
| /linux-4.4.14/drivers/acpi/apei/ |
| D | Kconfig | 64 and firmware implementation.
|
| /linux-4.4.14/Documentation/devicetree/bindings/serial/ |
| D | atmel-usart.txt | 30 - at91sam9260: generic USART implementation for SAM9 SoCs
|
| /linux-4.4.14/arch/c6x/lib/ |
| D | divi.S | 27 ;; In our implementation, divu and remu are leaf functions,
|
| D | remi.S | 27 ;; In our implementation, divu and remu are leaf functions,
|
| D | remu.S | 27 ;; In our implementation, divu and remu are leaf functions,
|
| D | divu.S | 27 ;; In our implementation, divu and remu are leaf functions,
|
| /linux-4.4.14/drivers/gpu/drm/i915/ |
| D | Kconfig | 37 different implementation.
|
| /linux-4.4.14/arch/powerpc/platforms/ps3/ |
| D | Kconfig | 57 current implementation should be considered experimental.
168 This driver uses a trivial implementation and is independent
|
| /linux-4.4.14/Documentation/arm/OMAP/ |
| D | omap_pm | 16 implementation, whether it is the TI SRF or Linux PM QoS or Linux
117 implementation needs:
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | intel-bts.txt | 10 consequence the present implementation is limited to per-thread recording.
|
| /linux-4.4.14/Documentation/trace/ |
| D | coresight.txt | 25 implementation, either storing the compressed stream in a memory buffer or
87 manage coresight devices on a platform. This first implementation centers on
129 Framework and implementation
|
| /linux-4.4.14/Documentation/x86/ |
| D | pat.txt | 125 implementation defined, yet this strategy can be used as last resort on devices
143 (*) denotes implementation defined and is discouraged
|
| /linux-4.4.14/tools/testing/selftests/futex/ |
| D | README | 10 Futextest will also provide example implementation of mutual exclusion
|
| /linux-4.4.14/drivers/staging/iio/ |
| D | TODO | 56 buffer implementation as different users will have
|
| /linux-4.4.14/arch/mips/cavium-octeon/ |
| D | Kconfig | 76 Lock the kernel's implementation of memcpy() into L2.
|
| /linux-4.4.14/drivers/atm/ |
| D | nicstarmac.copyright | 37 * See nicstar_free_rx_skb and linearize_buffer for implementation
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 422 A CIPSO implementation MUST be capable of generating at least tag type 1 in
423 the non-optimized form. In addition, a CIPSO implementation MUST be able
440 An implementation of CIPSO on a host MUST have the capability to reject a
612 The default condition for any CIPSO implementation is that an
614 handled as described in section 4.1. A CIPSO implementation MAY allow
669 to use. A CIPSO implementation need only support one level of DOI
675 A CIPSO implementation MUST support at least one DOI and SHOULD support
|
| /linux-4.4.14/arch/nios2/boot/dts/ |
| D | 3c120_devboard.dts | 43 altr,implementation = "fast";
|
| D | 10m50_devboard.dts | 41 altr,implementation = "fast";
|
| /linux-4.4.14/arch/mips/kernel/ |
| D | r2300_fpu.S | 68 cfc1 t0,$0 # implementation/version
|
| /linux-4.4.14/tools/perf/tests/attr/ |
| D | README | 16 This is the sys_perf_event_open hook implementation. The hook
|
| /linux-4.4.14/drivers/firewire/ |
| D | Kconfig | 12 a.k.a. Juju, a new implementation designed for robustness and
|
| /linux-4.4.14/Documentation/usb/ |
| D | CREDITS | 35 and offering suggestions and sharing implementation experiences.
62 PCI-to-USB Controller Board to test the OHCI implementation.
|
| /linux-4.4.14/fs/squashfs/ |
| D | Kconfig | 83 This decompressor implementation uses up to two parallel
94 This decompressor implementation uses a maximum of one
|
| /linux-4.4.14/lib/ |
| D | Kconfig | 116 prompt "CRC32 implementation"
132 This is the default implementation choice. Choose this one unless
469 This option provides an implementation of the CORDIC algorithm;
|
| /linux-4.4.14/Documentation/s390/ |
| D | zfcpdump.txt | 11 This zfcpdump implementation consists of a Linux dump kernel together with
|
| /linux-4.4.14/Documentation/cpuidle/ |
| D | sysfs.txt | 88 implementation of a particular governor. In the ladder governor, for
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | nvdimm.txt | 91 implementation is generic and supports pre-NFIT platforms, it was guided
93 for NVDIMM resources. The bulk of the kernel implementation is in place
133 distinction. The different device-types are an implementation detail
151 One such implementation is defined in the "Driver Writer's Guide" and "DSM
173 complicate the implementation because PMEM and BLK alias in DPA space.
563 implementation wants to supplant the standard nd_blk driver it can with
|
| /linux-4.4.14/Documentation/crypto/ |
| D | async-tx-api.txt | 65 result is zero. The implementation attempts to prevent
165 implementation examples.
|
| /linux-4.4.14/Documentation/block/ |
| D | pr.txt | 116 IOC_PR_REGISTER, and some implementation may support the flag for
|
| /linux-4.4.14/drivers/usb/core/ |
| D | Kconfig | 79 tristate "USB 2.0 OTG FSM implementation"
|
| /linux-4.4.14/fs/xfs/ |
| D | Kconfig | 16 for complete details. This implementation is on-disk compatible
|