| /linux-4.4.14/Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 3 The endianness mode of CPU & Device scenarios:
9 For one device driver, which will run in different scenarios above
|
| /linux-4.4.14/Documentation/devicetree/bindings/pci/ |
| D | plda,xpressrich3-axi.txt | 5 scenarios, the host-generic-pci.txt bindings apply with the following additions
|
| /linux-4.4.14/Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.txt | 30 region may not be present in some scenarios, such
|
| /linux-4.4.14/Documentation/networking/ |
| D | tcp-thin.txt | 7 effective. In time-dependent scenarios (like online games, control
|
| D | fib_trie.txt | 112 scenarios. It might conceivably be possible to run trie_rebalance via RCU
|
| D | batman-adv.txt | 99 In very mobile scenarios, you might want to adjust the originator
|
| D | filter.txt | 173 be used to write low-level filters for example scenarios mentioned in the
|
| D | ip-sysctl.txt | 1457 interfaces; mixed router/host scenarios are rather uncommon.
|
| /linux-4.4.14/drivers/pinctrl/ |
| D | pinctrl-pistachio.c | 81 const int *scenarios; member
508 .scenarios = pistachio_##_name##_scenarios, \
978 if (pf->scenarios) { in pistachio_pinmux_enable()
980 if (pf->scenarios[i] == group) in pistachio_pinmux_enable()
|
| /linux-4.4.14/Documentation/fb/ |
| D | deferred_io.txt | 33 It may be the case that this is useful in other scenarios as well. Paul Mundt
|
| D | fbcon.txt | 47 Possible scenarios:
|
| /linux-4.4.14/Documentation/ |
| D | unaligned-memory-access.txt | 48 here; a summary of the common scenarios is presented below:
185 In summary, the 2 main scenarios where you may run into unaligned access
|
| D | futex-requeue-pi.txt | 108 wake-up scenarios.
|
| D | robust-futexes.txt | 58 - it has quite complex locking and race scenarios. The vma-based
|
| D | this_cpu_ops.txt | 322 may be necessary. IPIs are generally recommended in such scenarios instead
|
| D | initrd.txt | 256 Usage scenarios
|
| D | workqueue.txt | 258 The following example execution scenarios try to illustrate how cmwq
|
| D | dma-buf-sharing.txt | 400 scenarios, we can extend dma-buf with a more explicit cache tracking scheme
|
| /linux-4.4.14/drivers/uio/ |
| D | Kconfig | 93 primarily, for virtualization scenarios.
|
| /linux-4.4.14/arch/mips/ |
| D | Kconfig.debug | 146 which may be beneficial in some scenarios.
|
| /linux-4.4.14/net/wireless/ |
| D | Kconfig | 126 scenarios, this relaxation is not allowed in cases that the BSS client
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.x25 | 60 X.25 on top of isdn might be useful with two different scenarios:
|
| /linux-4.4.14/Documentation/trace/ |
| D | coresight.txt | 22 path based on tracing scenarios as configured by users. From there the stream
|
| D | ring-buffer-design.txt | 625 The above are the trivial updates. Now for the more complex scenarios.
|
| /linux-4.4.14/Documentation/thermal/ |
| D | intel_powerclamp.txt | 34 actions that are designed for catastrophic scenarios.
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | net.txt | 299 any form of transaction handling. This means that different race scenarios are
|
| /linux-4.4.14/Documentation/locking/ |
| D | lockdep-design.txt | 182 I.e. complex multi-CPU and multi-task locking scenarios do not have to
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | v4l2-controls.txt | 267 The remainder of this document deals with more advanced topics and scenarios.
467 complex scenarios you can get dependencies from one control to another.
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | cache.txt | 22 scenarios (eg. a vm image server).
|
| D | thin-provisioning.txt | 18 scenarios.
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | timekeeping.txt | 574 distributed, but in contrived as well as real scenarios (guest device access,
612 but in general isn't recommended for real-world deployment scenarios.
|
| D | api.txt | 771 conjunction with KVM_SET_CLOCK, it is used to ensure monotonicity on scenarios
790 In conjunction with KVM_GET_CLOCK, it is used to ensure monotonicity on scenarios
|
| /linux-4.4.14/scripts/ |
| D | spelling.txt | 877 senarios||scenarios
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 1.Intro | 254 few practical scenarios where the agreement of all copyright holders could
|
| D | 4.Coding | 261 lockdep can find a number of scenarios in which the system could, on rare
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | blkio-controller.txt | 355 drive deeper request queue depths to keep the storage busy. In such scenarios
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | relay.txt | 301 relay_open(NULL, NULL, ...). Such channels are useful in scenarios such
|
| /linux-4.4.14/Documentation/RCU/ |
| D | RTFP.txt | 2381 usage scenarios, three classes of RCU implementation, wait-free
2662 usage scenarios, three classes of RCU implementation, wait-free
|
| /linux-4.4.14/Documentation/block/ |
| D | biodoc.txt | 217 done in some scenarios where the low level driver cannot be trusted to
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 1682 recovery of all the possible two disk failure scenarios for a
|