Searched refs:consistent (Results 1 – 25 of 172) sorted by relevance
1234567
/Linux-v6.6/drivers/comedi/drivers/ni_routing/ |
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-v6.6/arch/microblaze/mm/ |
D | Makefile | 6 obj-y := consistent.o init.o pgtable.o mmu_context.o fault.o
|
/Linux-v6.6/Documentation/devicetree/bindings/sound/ |
D | eukrea-tlv320.txt | 15 Note: The AUDMUX port numbering should start at 1, which is consistent with
|
D | imx-audio-sgtl5000.txt | 39 Note: The AUDMUX port numbering should start at 1, which is consistent with
|
D | imx-audio-es8328.txt | 37 Note: The AUDMUX port numbering should start at 1, which is consistent with
|
/Linux-v6.6/Documentation/scheduler/ |
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-v6.6/fs/btrfs/ |
D | Kconfig | 59 state of the filesystem on disk is always consistent, i.e., 61 in a consistent state.
|
/Linux-v6.6/Documentation/core-api/ |
D | dma-api-howto.rst | 158 SN2) requires 64-bit consistent allocations to operate correctly when the IO 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, 368 The consistent DMA mapping interfaces, will by default return a DMA address [all …]
|
D | protection-keys.rst | 74 The kernel attempts to make protection keys consistent with the
|
/Linux-v6.6/arch/sh/mm/ |
D | Makefile | 6 obj-y := alignment.o cache.o init.o consistent.o mmap.o
|
/Linux-v6.6/Documentation/devicetree/ |
D | changesets.rst | 16 receiver sees a complete and consistent state of the tree when it
|
/Linux-v6.6/Documentation/i2c/busses/ |
D | i2c-ali1535.rst | 28 be more consistent with the sequencing recommended by the manufacturer and
|
/Linux-v6.6/Documentation/virt/coco/ |
D | tdx-guest.rst | 43 consistent, a subtype index is added as part of the IOCTL CMD.
|
/Linux-v6.6/Documentation/filesystems/ |
D | fuse-io.rst | 21 read-ahead by the kernel to fill the cache. The cache is always kept consistent
|
/Linux-v6.6/Documentation/userspace-api/ |
D | sysfs-platform_profile.rst | 33 gets a consistent experience the sysfs-platform_profile ABI document defines
|
/Linux-v6.6/Documentation/admin-guide/laptops/ |
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-v6.6/Documentation/devicetree/bindings/ |
D | common-properties.txt | 9 different machine types. This document attempts to provide a consistent
|
/Linux-v6.6/Documentation/admin-guide/device-mapper/ |
D | dm-log.rst | 5 RAID targets to track regions of the disk that are not consistent.
|
/Linux-v6.6/Documentation/locking/ |
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-v6.6/drivers/dma-buf/ |
D | Kconfig | 51 This is marked experimental because we don't yet have a consistent
|
/Linux-v6.6/drivers/powercap/ |
D | Kconfig | 10 capping settings to user space in a consistent way. Usually, it consists
|
/Linux-v6.6/Documentation/scsi/ |
D | megaraid.rst | 45 "As Jeff hinted, if your userspace<->driver API is consistent between
|
/Linux-v6.6/Documentation/admin-guide/ |
D | cputopology.rst | 36 To be consistent on all architectures, include/linux/topology.h
|
/Linux-v6.6/Documentation/driver-api/md/ |
D | raid5-ppl.rst | 18 the stripe, consistent with its state before the write operation, regardless of
|
/Linux-v6.6/Documentation/userspace-api/media/v4l/ |
D | audio.rst | 96 only making the API more consistent but also permitting radio devices
|
1234567