Searched refs:consistent (Results 1 – 25 of 167) sorted by relevance
1234567
| /linux/drivers/comedi/drivers/ni_routing/ |
| A D | README | 18 2) The register values are _NOT_ completely consistent. There is no way to
29 4) The sets of routes that are valid are not consistent from device to device.
33 through any documentation. In fact, the only consistent source of this
48 directory are chosen to be consistent with (a) the NI's user level
96 As noted above, the only known consistent source of information for
119 As noted above, the only consistent source of information of valid
178 convention, although the register values are not consistent. This next table
|
| /linux/arch/microblaze/mm/ |
| A D | Makefile | 6 obj-y := consistent.o init.o pgtable.o mmu_context.o fault.o
|
| /linux/Documentation/scheduler/ |
| A D | sched-nice-design.rst | 58 To sum it up: we always wanted to make nice levels more consistent, but
93 it was possible to implement better and more consistent nice +19
98 To address the second complaint (of nice levels not being consistent),
|
| /linux/Documentation/core-api/ |
| A D | dma-api-howto.rst | 177 The setup for consistent allocations is performed via a call
224 uses consistent allocations, one would have to check the return value from
287 Think of "consistent" as "synchronous" or "coherent".
289 The current default is to return consistent memory in the low 32
291 set the consistent mask even if this default is fine for your
294 Good examples of what to use consistent mappings for are:
309 consistent memory just as it may normal memory. Example:
351 To allocate and map large (PAGE_SIZE or so) consistent DMA regions,
370 that it may address the upper 32-bits, consistent allocation will only
371 return > 32-bit addresses for DMA if the consistent DMA mask has been
[all …]
|
| /linux/Documentation/devicetree/bindings/sound/ |
| A D | eukrea-tlv320.txt | 15 Note: The AUDMUX port numbering should start at 1, which is consistent with
|
| A D | imx-audio-sgtl5000.txt | 39 Note: The AUDMUX port numbering should start at 1, which is consistent with
|
| A D | imx-audio-es8328.txt | 37 Note: The AUDMUX port numbering should start at 1, which is consistent with
|
| /linux/fs/btrfs/ |
| A D | Kconfig | 58 state of the filesystem on disk is always consistent, i.e.,
60 in a consistent state.
|
| /linux/arch/sh/mm/ |
| A D | Makefile | 6 obj-y := alignment.o cache.o init.o consistent.o mmap.o
|
| /linux/Documentation/devicetree/ |
| A D | changesets.rst | 16 receiver sees a complete and consistent state of the tree when it
|
| /linux/Documentation/i2c/busses/ |
| A D | i2c-ali1535.rst | 28 be more consistent with the sequencing recommended by the manufacturer and
|
| /linux/drivers/powercap/ |
| A D | Kconfig | 10 capping settings to user space in a consistent way. Usually, it consists
|
| /linux/Documentation/admin-guide/laptops/ |
| A D | sony-laptop.rst | 10 (hopefully consistent) interface. This also means that the sonypi driver is
102 More recent Vaio models expose a consistent set of ACPI methods to
|
| /linux/Documentation/filesystems/ |
| A D | fuse-io.rst | 21 read-ahead by the kernel to fill the cache. The cache is always kept consistent
|
| /linux/Documentation/userspace-api/ |
| A D | sysfs-platform_profile.rst | 33 gets a consistent experience the sysfs-platform_profile ABI document defines
|
| /linux/Documentation/leds/ |
| A D | well-known-leds.txt | 3 It is somehow important to provide consistent interface to the
|
| /linux/Documentation/devicetree/bindings/reserved-memory/ |
| A D | shared-dma-pool.yaml | 57 the default pool of the consistent DMA allocator.
|
| /linux/Documentation/devicetree/bindings/timer/ |
| A D | arm,sp804.yaml | 69 # consistent naming used in the existing DTs. The primecell binding
|
| /linux/Documentation/locking/ |
| A D | seqlock.rst | 11 reader wants a consistent set of information and is willing to retry if
14 A data set is consistent when the sequence count at the beginning of the
|
| /linux/Documentation/admin-guide/device-mapper/ |
| A D | dm-log.rst | 5 RAID targets to track regions of the disk that are not consistent.
|
| /linux/Documentation/devicetree/bindings/ |
| A D | common-properties.txt | 9 different machine types. This document attempts to provide a consistent
|
| /linux/Documentation/fb/ |
| A D | modedb.rst | 80 "The purpose of CVT is to provide a method for generating a consistent
86 consistent manner that ensures greater compatibility."
|
| /linux/drivers/dma-buf/ |
| A D | Kconfig | 51 This is marked experimental because we don't yet have a consistent
|
| /linux/Documentation/PCI/ |
| A D | pci.rst | 284 can directly address "consistent memory" in System RAM above 4G physical
289 ("consistent") data.
294 Once the DMA masks are set, the driver can allocate "consistent" (a.k.a. shared)
370 - Release DMA buffers (both streaming and consistent)
423 Then clean up "consistent" buffers which contain the control data.
|
| /linux/Documentation/scsi/ |
| A D | megaraid.rst | 45 "As Jeff hinted, if your userspace<->driver API is consistent between
|
Completed in 30 milliseconds
1234567