Searched full:possible (Results 1 – 25 of 965) sorted by relevance
12345678910>>...39
| /Documentation/scsi/ |
| D | link_power_management_policy.txt | 2 There are 3 possible options:
7 least possible power when possible. This may
16 when possible, but do not enter the lowest power
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 13 # * What values are possible for CORE?
16 # that are possible for CORE. So for example if CORE_BELL_A_ADVANCED is 'y',
30 # what values are possible for CORE we ended up needing to address questions
31 # regarding possible values of CORE itself again. Answering the original
32 # question of what are the possible values of CORE would make the kconfig
|
| /Documentation/media/uapi/v4l/ |
| D | ext-ctrls-flash.rst | 69 to the flash controller. Setting this control may not be possible in
101 this is a sensor, which makes it possible to synchronises the
110 control may not be possible in presence of some faults. See
127 if possible.
132 if possible. Setting this control may not be possible in presence of
138 possible.
147 and returns the chip to a usable state if possible.
178 which strobing the flash at full current will not be possible.The
191 after strobe during which another strobe will not be possible. This
|
| D | vidioc-g-selection.rst | 80 choose a crop/compose rectangle as close as possible to the requested
96 capture/output window or TV display. The closest possible values of
106 3. Keep center of adjusted rectangle as close as possible to the
109 4. Keep width and height as close as possible to original ones.
111 5. Keep horizontal and vertical offset as close as possible to original
191 It is not possible to adjust struct :c:type:`v4l2_rect`
199 It is not possible to apply change of the selection rectangle at the
|
| /Documentation/networking/ |
| D | mpls-sysctl.txt | 5 possible to configure forwarding for label values equal to or
9 is possible and expected as the platform labels are locally
19 Possible values: 0 - 1048575
38 Possible values: 1 - 255
|
| D | ipv6.txt | 21 The possible values and their effects are:
32 it will not be possible to open an IPv6 socket.
43 The possible values and their effects are:
61 The possible values and their effects are:
|
| /Documentation/devicetree/bindings/power/ |
| D | rockchip-io-domain.txt | 56 Possible supplies for PX30:
65 Possible supplies for PX30 pmu-domains:
69 Possible supplies for rk3188:
80 Possible supplies for rk3228:
86 Possible supplies for rk3288:
98 Possible supplies for rk3368:
107 Possible supplies for rk3368 pmu-domains:
111 Possible supplies for rk3399:
117 Possible supplies for rk3399 pmu-domains:
|
| /Documentation/devicetree/bindings/phy/ |
| D | brcm,brcmstb-usb-phy.txt | 11 the type of the PHY. Possible values are:
19 Possible values are: 0 (Don't invert), 1 (Invert)
21 Possible values are: 0 (Don't invert), 1 (Invert)
26 Possible values are: "host", "peripheral ", "drd" or "typec-pd"
|
| /Documentation/devicetree/bindings/clock/ |
| D | ux500.txt | 19 wants to use, possible values are 1, 2, 3, 5, 6. The second
21 possible values are 0 thru 31.
25 wants to use, possible values are 1, 2, 3, 5, 6. The second
27 possible values are 0 thru 31.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-grcan | 9 Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP
21 Possible values: 0 or 1. See the GRCAN chapter of the GRLIB IP
31 Configuration of which physical interface to be used. Possible
|
| D | sysfs-uevent | 19 a transaction identifier so it's possible to use the same UUID
30 It's possible to define zero or more pairs - each pair is then
33 name gains "SYNTH_ARG_" prefix to avoid possible collisions
|
| D | sysfs-class-power-twl4030 | 6 Possible values are:
25 Possible values are:
|
| D | sysfs-class-scsi_host | 23 stack for a performance advantage when possible. A value of
39 There are four possible options:
42 least possible power when possible. This may sacrifice some
51 when possible, but do not enter the lowest power state, thus
|
| D | sysfs-bus-bcma | 7 include/linux/bcma/bcma.h for possible values.
31 belongs to. See include/linux/bcma/bcma.h for possible values.
|
| D | sysfs-firmware-opal-powercap | 22 possible powercap in Watt units
25 possible powercap in Watt units
|
| D | sysfs-platform-usbip-vudc | 8 controller. It is possible to read this file
33 would like to use this device. It is possible to
|
| D | configfs-rdma_cm | 21 The possible RoCE types are either "IB/RoCE v1" or "RoCE v2".
30 The possible RoCE TOS values are 0-255.
|
| D | sysfs-class-net | 6 Indicates the name assignment type. Possible values are:
17 Indicates the address assignment type. Possible values are:
117 Indicates whether the interface is in dormant state. Possible
132 Indicates the interface latest or current duplex value. Possible
146 include/uapi/linux/if.h for a list of all possible values and
185 to determine the interface usability. Possible values:
216 Possible values are:
263 include/uapi/linux/if_arp.h for all possible values.
|
| /Documentation/media/uapi/dvb/ |
| D | frontend-stat-properties.rst | 46 frontend, but it was not possible to collect it (could be a
68 Possible scales for this metric are:
87 Possible scales for this metric are:
118 Possible scales for this metric are:
146 Possible scales for this metric are:
175 Possible scales for this metric are:
203 Possible scales for this metric are:
224 Possible scales for this metric are:
246 Possible scales for this metric are:
|
| D | fe_property_parameters.rst | 86 Most of the digital TV standards offers more than one possible
123 Possible values: ``1712000``, ``5000000``, ``6000000``, ``7000000``,
127 Terrestrial Standard Possible values for bandwidth
295 Possible values: 0, 1, -1 (AUTO)
309 Possible values: 0, 1, -1 (AUTO)
346 Possible values: 0 .. 41, -1 (AUTO)
362 Possible values: 0 .. ``DTV_ISDBT_SB_SEGMENT_COUNT`` - 1
379 Possible values: 1 .. 13
445 Possible values are: ``FEC_AUTO``, ``FEC_1_2``, ``FEC_2_3``, ``FEC_3_4``,
459 Possible values are: ``QAM_AUTO``, ``QPSK``, ``QAM_16``, ``QAM_64``, ``DQPSK``
[all …]
|
| /Documentation/filesystems/ |
| D | virtiofs.rst | 20 Although it is possible to use existing network file systems for some of these
27 possible with network file systems.
54 FUSE client may choose which request to transfer, making it possible to
56 it is not possible to change the order of requests that have been enqueued.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,imx27-pinctrl.txt | 20 Possible values:
27 Possible values:
36 Possible values:
45 Possible values:
|
| /Documentation/translations/ |
| D | index.rst | 39 applied to the English documents first. Afterwards and when possible, the
44 Translations try to be as accurate as possible but it is not possible to map
|
| /Documentation/admin-guide/ |
| D | ufs.rst | 16 ufs manually by mount option ufstype. Possible values are:
58 Possible Problems
|
| /Documentation/ |
| D | speculation.txt | 13 such as the contents of registers. However, in some cases it is possible to
18 For example, in the presence of branch prediction, it is possible for bounds
40 It is possible that a CPU mis-predicts the conditional branch, and
|
12345678910>>...39