Searched full:possible (Results 1 – 25 of 1118) sorted by relevance
12345678910>>...45
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ccp | 18 Possible values:
29 Possible values:
40 Possible values:
51 Possible values:
63 Possible values:
74 Possible values:
85 Possible values:
|
| 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 | 21 a transaction identifier so it's possible to use the same UUID
33 It's possible to define zero or more pairs - each pair is then
36 name gains ``SYNTH_ARG_`` prefix to avoid possible collisions
|
| 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-class-net | 6 Indicates the name assignment type. Possible values are:
20 Indicates the address assignment type. Possible values are:
85 Possible values are:
129 Indicates whether the interface is in dormant state. Possible
144 Indicates whether the interface is under test. Possible
160 Indicates the interface latest or current duplex value. Possible
177 include/uapi/linux/if.h for a list of all possible values and
216 to determine the interface usability. Possible values:
251 Possible values are:
299 include/uapi/linux/if_arp.h for all possible values.
[all …]
|
| 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 | 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.
|
| /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/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 62 to the flash controller. Setting this control may not be possible in
97 this is a sensor, which makes it possible to synchronise the
106 control may not be possible in presence of some faults. See
123 if possible.
128 if possible. Setting this control may not be possible in presence of
134 possible.
143 and returns the chip to a usable state if possible.
174 which strobing the flash at full current will not be possible.The
187 after strobe during which another strobe will not be possible. This
|
| D | vidioc-g-selection.rst | 73 choose a crop/compose rectangle as close as possible to the requested
89 capture/output window or TV display. The closest possible values of
99 3. Keep center of adjusted rectangle as close as possible to the
102 4. Keep width and height as close as possible to original ones.
104 5. Keep horizontal and vertical offset as close as possible to original
181 It is not possible to adjust struct :c:type:`v4l2_rect`
189 It is not possible to apply change of the selection rectangle at the
|
| D | ext-ctrls-codec.rst | 96 of possible VBI formats depends on the driver. The currently defined
122 MPEG Audio sampling frequency. Possible values are:
146 streams. Possible values are:
173 MPEG-1/2 Layer I bitrate. Possible values are:
218 MPEG-1/2 Layer II bitrate. Possible values are:
263 MPEG-1/2 Layer III bitrate. Possible values are:
311 AC-3 bitrate. Possible values are:
366 MPEG Audio mode. Possible values are:
393 in stereo. Layer III is not (yet) supported. Possible values are:
418 Audio Emphasis. Possible values are:
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | stericsson,u8500-clks.yaml | 52 which PRCC block the consumer wants to use, possible values are 1, 2, 3,
54 wants, possible values are 0 thru 31.
66 block the consumer wants to use, possible values are 1, 2, 3, 5, 6. The
67 second cell indicates which clock inside the PRCC block it wants, possible
80 which PRCC block the consumer wants to use, possible values are 1, 2, 3
82 it wants to control, possible values are 0 thru 31.
122 possible values are 0 (CLKOUT1) and 1 (CLKOUT2).
124 possible values are 0 thru 7, see the defines for the different
|
| /Documentation/networking/ |
| D | ipv6.rst | 27 The possible values and their effects are:
38 it will not be possible to open an IPv6 socket.
49 The possible values and their effects are:
67 The possible values and their effects are:
|
| D | mpls-sysctl.rst | 12 possible to configure forwarding for label values equal to or
16 is possible and expected as the platform labels are locally
26 Possible values: 0 - 1048575
46 Possible values: 1 - 255
|
| /Documentation/scsi/ |
| D | link_power_management_policy.rst | 8 There are 3 possible options:
14 least possible power when possible. This may
23 when possible, but do not enter the lowest power
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend-stat-properties.rst | 39 frontend, but it was not possible to collect it (could be a
61 Possible scales for this metric are:
80 Possible scales for this metric are:
111 Possible scales for this metric are:
139 Possible scales for this metric are:
168 Possible scales for this metric are:
196 Possible scales for this metric are:
217 Possible scales for this metric are:
239 Possible scales for this metric are:
|
| D | fe_property_parameters.rst | 79 Most of the digital TV standards offers more than one possible
121 Possible values: ``1712000``, ``5000000``, ``6000000``, ``7000000``,
125 Terrestrial Standard Possible values for bandwidth
293 Possible values: 0, 1, -1 (AUTO)
307 Possible values: 0, 1, -1 (AUTO)
344 Possible values: 0 .. 41, -1 (AUTO)
360 Possible values: 0 .. ``DTV_ISDBT_SB_SEGMENT_COUNT`` - 1
377 Possible values: 1 .. 13
443 Possible values are: ``FEC_AUTO``, ``FEC_1_2``, ``FEC_2_3``, ``FEC_3_4``,
457 Possible values are: ``QAM_AUTO``, ``QPSK``, ``QAM_16``, ``QAM_64``, ``DQPSK``
[all …]
|
| /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 | 45 applied to the English documents first. Afterwards and when possible, the
50 Translations try to be as accurate as possible but it is not possible to map
|
| /Documentation/filesystems/ |
| D | virtiofs.rst | 22 Although it is possible to use existing network file systems for some of these
29 possible with network file systems.
70 FUSE client may choose which request to transfer, making it possible to
72 it is not possible to change the order of requests that have been enqueued.
|
| /Documentation/filesystems/spufs/ |
| D | spufs.rst | 57 possible operations, e.g. read access on the wbox file.
65 data in the address space of the SPU. The possible operations on an
83 blocking mode and it even poll() will not block on it. The possible
97 poll family of system calls can be used to wait for it. The possible
120 poll can be used to wait for it becoming empty again. The possible
142 units and return a big-endian binary integer number. The possible
173 The possible operations on an open npc, decr, decr_status,
215 is reset to zero. The possible operations on an open signal1 or sig-
241 quently written to it. The possible operations on an open signal1_type
|
| /Documentation/devicetree/bindings/regulator/ |
| D | samsung,s5m8767.yaml | 37 change in SOC. The different possible values are:
61 mode change in SOC. The different possible values are:
86 mode change in SOC. The different possible values are:
|
| /Documentation/devicetree/bindings/pwm/ |
| D | microchip,corepwm.yaml | 43 mode is possible for each channel, and is set by the bitstream programmed to the
49 whether synchronous mode is possible for the PWM channel.
56 Optional, per-channel Low Ripple DAC mode is possible on this IP core. It creates
|
| /Documentation/admin-guide/ |
| D | ufs.rst | 16 ufs manually by mount option ufstype. Possible values are:
58 Possible Problems
|
12345678910>>...45