Searched full:way (Results 1 – 25 of 747) sorted by relevance
12345678910>>...30
| /Documentation/x86/ |
| D | entry_64.rst | 28 either way.
36 magically-generated functions that make their way to do_IRQ with
64 Now, there's a secondary complication: there's a cheap way to test
65 which mode the CPU is in and an expensive way.
67 The cheap way is to pick this info off the entry frame on the kernel
75 The expensive (paranoid) way is to read back the MSR_GS_BASE value
96 stack but before we executed SWAPGS, then the only safe way to check
|
| /Documentation/devicetree/bindings/mux/ |
| D | mux-controller.txt | 11 space is a simple zero-based enumeration. I.e. 0-1 for a 2-way multiplexer,
12 0-7 for an 8-way multiplexer, etc.
43 /* One consumer of a 2-way mux controller (one GPIO-line) */
69 * parallel 4-way multiplexers controlled by the same two GPIO-lines.
149 4-way multiplexer):
|
| /Documentation/userspace-api/media/v4l/ |
| D | yuv-formats.rst | 12 *color difference* signals, this way the green component can be
16 color in a way compatible with existing receivers a new signal carrier
|
| D | selection-api-vs-crop-api.rst | 30 cropping/composing in a clear, intuitive and portable way. Next, with
34 way to extend their functionality. The new struct
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 20 underlying IP blocks changes in a way that software should be aware of.
30 "sifive,fu540-c000-uart". This way, if SoC-specific
|
| /Documentation/ia64/ |
| D | efirtc.rst | 28 portable way, the CMOS clock. A program like /sbin/hwclock uses such a clock
38 EFI uses a slightly different way of representing the time, noticeably
41 expose this new way of representing time. Instead we use something very
43 One of the reasons for doing it this way is to allow for EFI to still evolve
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-log.rst | 30 This log implementation commits the log state to disk. This way, the
42 This log type simply provides a way to export the log API to userspace,
49 diversity, and 2-way communication nature of the exchanges between
|
| /Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 21 The most common way to achieve this is to use the state container design
62 This way you always get a pointer back to the correct instance of foo in
115 instance this way, while still keeping the number of parameters passed to the
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-rpmsg | 22 a unique rpmsg address (a 32 bits integer). This way when
40 a unique rpmsg address (a 32 bits integer). This way when
70 creation of the channel (this way remote clients know they
|
| D | sysfs-firmware-sfi | 12 can observe them this way::
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | baikal,bt1-l2-ctl.yaml | 16 to change the Tag, Data and Way-select RAM access latencies. Baikal-T1
29 description: Cycles of latency for Way-select RAM accesses
|
| /Documentation/dev-tools/ |
| D | sparse.rst | 40 So the simpler way is to just do::
71 releasing the lock inside the function in a balanced way, no
98 be recompiled or not. The latter is a fast way to check the whole tree if you
|
| /Documentation/process/ |
| D | 2.Process.rst | 67 As fixes make their way into the mainline, the patch rate will slow over
161 describes the process in a somewhat idealized way. A much more detailed
166 - Design. This is where the real requirements for the patch - and the way
180 all the way to the mainline. The patch will show up in the maintainer's
224 unassisted. The way the kernel developers have addressed this growth is
231 subsystem maintainers are the gatekeepers (in a loose way) for the portion
260 normally the right way to go.
313 their way into linux-next some time before the merge window opens.
320 many sub-directories for drivers or filesystems that are on their way to
323 kernel proper. This is a way to keep track of drivers that aren't
[all …]
|
| D | stable-api-nonsense.rst | 55 discuss the binary stuff first to get it out of the way.
81 There is no way that binary drivers from one architecture will run
98 of release, I learned this the hard way a long time ago...
110 current interfaces, or figure out a better way to do things. If they do
126 - A change was made in the way data packets were allocated from the
|
| /Documentation/admin-guide/ |
| D | devices.txt | 207 Partitions are handled in the same way as for IDE
519 Partitions are handled the same way as for IDE disks
530 Partitions are handled the same way as for the first
638 Partitions are handled in the same way as for IDE
726 Partitions are handled the same way as for the first
744 Partitions are handled the same way as for the first
871 Partitions are handled in the same way as for IDE
895 Partitions are handled in the same way as for IDE
1044 Partitions are handled the same way as for the first
1056 Partitions are handled the same way as for the first
[all …]
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 10 make P2P transactions tricky to do in a perfectly safe way.
15 simple way to determine if a given Root Complex supports this or not.
76 this way, the resource must be regular memory with no side effects.
89 way does not need to be unmapped.
|
| /Documentation/input/devices/ |
| D | rotary-encoder.rst | 52 (i.e. the rotation was not reversed half-way).
61 meaning that there it has seen half the way of a one-step transition.
68 should have happened, unless it flipped back on half the way. The
|
| /Documentation/filesystems/ |
| D | inotify.rst | 50 - There would be no way to get event ordering. Events on file foo and
51 file bar would pop poll() on both fd's, but there would be no way to tell
64 - No way to get out of band data.
|
| D | journalling.rst | 63 device you can call jbd2_journal_forget() in much the same way as you
103 there is no way to restore the contents of the reallocated blocks at the
104 end of the last fully committed transaction. One simple way of doing
118 JBD2 also provides a way to block all transaction updates via
155 fails for some reason and the only way to guarantee consistency is for JBD2 to
|
| /Documentation/hwmon/ |
| D | adm1025.rst | 48 chip that way is obscure at least to me. The bit 5 of the configuration
52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
|
| /Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 12 ``devlink-dpipe`` provides a standardized way to provide visibility into the
18 pipeline in a generic way.
20 The hardware offload process is expected to be done in a way that the user
24 standard way.
109 In a similar way to P4 headers and fields are used to describe a table's
|
| /Documentation/arm/ |
| D | firmware.rst | 8 world, which changes the way some things have to be initialized. This makes
70 cpu_boot_legacy(...); /* Try legacy way */
|
| /Documentation/watchdog/ |
| D | pcwd-watchdog.rst | 15 trigger the card into being reset. This way you can make the card
63 enable or disable the card this way.
|
| /Documentation/admin-guide/acpi/ |
| D | ssdt-overlays.rst | 8 boards) we need a way to augment the ACPI configuration provided by the firmware
18 way to augment firmware ACPI configuration is by dynamically loading
77 It works in a similar way with initrd based ACPI tables override/upgrade: SSDT
103 allows a persistent, OS independent way of storing the user defined SSDTs. There
|
| /Documentation/ABI/removed/ |
| D | sysfs-class-rfkill | 9 Description: This file was deprecated because there no longer was a way to
|
12345678910>>...30