Searched refs:scenarios (Results 1 – 25 of 54) sorted by relevance
123
| /Linux-v4.19/Documentation/devicetree/bindings/pci/ |
| D | plda,xpressrich3-axi.txt | 5 scenarios, the host-generic-pci.txt bindings apply with the following additions
|
| /Linux-v4.19/Documentation/devicetree/bindings/timer/ |
| D | andestech,atcpit100-timer.txt | 10 multi-function timer and provide the following usage scenarios:
|
| /Linux-v4.19/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-palmas.txt | 43 scenarios. So for GPIO7 if ti,palmas-override-powerhold is set
46 power off scenarios the driver will over ride the mux value.
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-lptimer-stm32 | 43 In quadrature mode, encoder counting scenarios are as follows:
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | l1tf.rst | 65 Attack scenarios
182 scenarios where guest VMEXIT/VMENTER are rare the performance impact is
185 application scenarios might still suffer from a high VMEXIT rate.
239 scenarios.
262 configuration and the scenarios which run on the system. While for some
606 analyze the risk for their scenarios and make the appropriate
610 kind of scenarios.
|
| /Linux-v4.19/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.rst | 102 In very mobile scenarios, you might want to adjust the originator interval to a
|
| D | dpaa.txt | 152 provides a big performance boost for the forwarding scenarios, allowing
|
| /Linux-v4.19/drivers/pinctrl/ |
| D | pinctrl-pistachio.c | 81 const int *scenarios; member
508 .scenarios = pistachio_##_name##_scenarios, \
973 if (pf->scenarios) { in pistachio_pinmux_enable()
975 if (pf->scenarios[i] == group) in pistachio_pinmux_enable()
|
| /Linux-v4.19/Documentation/sound/hd-audio/ |
| D | dp-mst.rst | 47 So there are the following scenarios:
|
| /Linux-v4.19/Documentation/fb/ |
| D | deferred_io.txt | 33 It may be the case that this is useful in other scenarios as well. Paul Mundt
|
| /Linux-v4.19/Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.txt | 30 region may not be present in some scenarios, such
|
| /Linux-v4.19/Documentation/admin-guide/pm/ |
| D | strategies.rst | 45 Moreover, the two power management strategies address different usage scenarios.
|
| /Linux-v4.19/drivers/staging/erofs/ |
| D | Kconfig | 9 blocks, inline xattrs/data, etc.) for scenarios which need
|
| /Linux-v4.19/Documentation/devicetree/bindings/usb/ |
| D | mediatek,mtk-xhci.txt | 5 There are two scenarios: the first one only supports xHCI driver;
|
| /Linux-v4.19/Documentation/filesystems/cifs/ |
| D | TODO | 61 failover scenarios, e.g. when client knows multiple DFS entries point to
|
| /Linux-v4.19/Documentation/ |
| D | unaligned-memory-access.txt | 57 here; a summary of the common scenarios is presented below:
195 In summary, the 2 main scenarios where you may run into unaligned access
|
| D | futex-requeue-pi.txt | 109 wake-up scenarios.
|
| D | ntb.txt | 76 As one can see the described scenarios can be combined in one portable
|
| D | robust-futexes.txt | 62 - it has quite complex locking and race scenarios. The vma-based
|
| D | this_cpu_ops.txt | 332 may be necessary. IPIs are generally recommended in such scenarios instead
|
| /Linux-v4.19/drivers/uio/ |
| D | Kconfig | 93 primarily, for virtualization scenarios.
|
| /Linux-v4.19/net/wireless/ |
| D | Kconfig | 151 scenarios, this relaxation is not allowed in cases where the BSS client
|
| /Linux-v4.19/Documentation/isdn/ |
| D | README.x25 | 60 X.25 on top of isdn might be useful with two different scenarios:
|
123
