Searched full:requested (Results 1 – 25 of 293) sorted by relevance
12345678910>>...12
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-create-bufs.rst | 43 ``count`` field must be set to the number of requested buffers, the
44 ``memory`` field specifies the requested I/O method and the ``reserved``
52 requested format is supported by the driver. Based on the format's
53 ``type`` field the requested buffer size (for single-planar) or plane
64 driver may reject the requested size, but if it is accepted the driver
68 will attempt to allocate up to the requested number of buffers and store
71 than the number requested.
87 - The number of buffers requested or granted. If count == 0, then
131 The buffer type (``format.type`` field), requested I/O method
|
| D | v4l2-selection-flags.rst | 25 size) than was requested. Albeit the driver may choose a lesser
34 size) than was requested. Albeit the driver may choose a greater
|
| D | vidioc-reqbufs.rst | 48 the desired number of buffers, ``memory`` must be set to the requested
51 allocate the requested number of buffers and it stores the actual number
53 requested, even zero, when the driver runs out of free memory. A larger
83 - The number of buffers requested or granted.
168 The buffer type (``type`` field) or the requested I/O method
|
| D | pixfmt-v4l2.rst | 69 the value requested by the application, returning ``width`` times
115 for the captured image data. If the driver cannot handle requested
159 for the captured image data. If the driver cannot handle requested
173 captured image data. If the driver cannot handle requested
189 range for the captured image data. If the driver cannot handle requested
202 for the captured image data. If the driver cannot handle requested
230 colorspace conversion from the received colorspace to the requested
|
| D | vidioc-g-selection.rst | 68 requested rectangle. An application may introduce constraints to control
73 choose a crop/compose rectangle as close as possible to the requested
83 size exactly the same as in the requested rectangle.
87 The driver may have to adjusts the requested dimensions against hardware
|
| D | vidioc-g-priority.rst | 88 The requested priority value is invalid.
91 Another application already requested higher priority.
|
| D | vidioc-g-std.rst | 56 no flags are given or the current input does not support the requested
58 is ambiguous drivers may return ``EINVAL`` or choose any of the requested
|
| D | vidioc-g-fmt.rst | 55 member. When the requested buffer type is not supported drivers return
75 ioctl. When the requested buffer type is not supported drivers return an
148 invalid or the requested buffer type not supported.
|
| D | selection-api-configuration.rst | 17 Therefore, as usual, drivers are expected to adjust the requested
40 The driver may further adjust the requested size and/or position
100 further adjust the requested size and/or position according to hardware
|
| D | crop.rst | 92 capture boundaries and the driver may further adjust the requested size
120 usual, drivers are expected to adjust the requested parameters and
126 limitations, the last requested rectangle shall take priority, and the
129 the driver state and therefore only adjust the requested rectangle.
138 then chooses the cropping rectangle closest to the requested size, that
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-reqbufs.rst | 53 attempt to allocate the requested number of buffers and it stores the actual
54 number allocated in the ``count`` field. The ``count`` can be smaller than the number requested, ev…
57 at ``size``, and can be smaller than what's requested.
75 The the requested I/O method is not supported.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-devfreq | 45 the requested polling interval of the corresponding devfreq
74 sets the requested frequency for the devfreq object if
98 the minimum frequency requested by users. It is 0 if
100 frequency requested by governors.
107 the maximum frequency requested by users. It is 0 if
109 frequency requested by governors and min_freq.
|
| D | sysfs-platform-kim | 12 dameon and opens the device when install is requested.
24 daemon when the ldisc install is requested.
|
| /Documentation/devicetree/bindings/spmi/ |
| D | qcom,spmi-pmic-arb.txt | 39 cell 1: slave ID for the requested interrupt (0-15)
40 cell 2: peripheral ID for requested interrupt (0-255)
41 cell 3: the requested peripheral interrupt (0-7)
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | max6650.txt | 16 - maxim,fan-target-rpm: Initial requested fan rotation speed. If specified, the
17 driver selects closed-loop mode and the requested speed.
|
| /Documentation/filesystems/spufs/ |
| D | spufs.rst | 87 If a count smaller than four is requested, read returns -1 and
101 If a count smaller than four is requested, read returns -1 and
122 four is requested, write returns -1 and sets errno to EINVAL. If there
146 If a count smaller than four is requested, read returns -1 and
198 If a count smaller than four is requested, read returns -1 and
204 If a count smaller than four is requested, write returns -1 and
219 If a count smaller than four is requested, read returns -1 and
225 If a count smaller than four is requested, write returns -1 and
|
| /Documentation/devicetree/bindings/mfd/ |
| D | atmel-hlcdc.txt | 12 - clock-names: the name of the 3 clocks requested by the HLCDC device.
14 - clocks: should contain the 3 clocks requested by the HLCDC device.
|
| /Documentation/w1/ |
| D | w1-netlink.rst | 11 is found either due to automatic or requested search.
143 requested by the user, i.e. read/write/touch IO requests will not contain
171 When found, master device (requested or those one on where slave device
172 is found) is locked. If slave command is requested, then reset/select
175 Then all requested in w1_netlink_msg operations are performed one by one.
|
| /Documentation/devicetree/bindings/clock/ |
| D | ti,cdce925.txt | 34 present, the clock runs at the requested frequency on average. Otherwise
35 the requested frequency is the maximum value of the SCC range.
|
| D | imx31-clock.yaml | 88 interrupt for DVFS when a frequency change is requested, request 2 is
89 to generate interrupt for DPTC when a voltage change is requested.
|
| /Documentation/driver-api/ |
| D | xillybus.rst | 156 has been requested by a read() call. On synchronous pipes, only the amount
157 of data requested by a read() call is transmitted.
165 that read() or write() completes less bytes than requested. There is a
213 applies) may return with less than the requested number of bytes. The common
353 since large continuous physical memory segments are sometimes requested,
358 buffer size in the IDT. If a requested buffer is larger or equal to a page,
359 the necessary number of pages is requested from the kernel, and these are
360 used for this buffer. If the requested buffer is smaller than a page, one
361 single page is requested from the kernel, and that page is partially used.
363 into that page. It can be shown that all pages requested from the kernel
|
| /Documentation/devicetree/bindings/pci/ |
| D | mobiveil-pcie.txt | 21 - apio-wins : number of requested apio outbound windows
25 - ppio-wins : number of requested ppio inbound windows
|
| /Documentation/userspace-api/media/drivers/ |
| D | omap3isp-uapi.rst | 173 module's data output depends on the requested configuration. Although the
181 The internal buffer size allocation considers the requested configuration's
191 data. After a configuration is requested, the config_counter returned to user
194 buffer is requested, this config_counter is used to match a buffer data and a
|
| /Documentation/admin-guide/pm/ |
| D | cpufreq_drivers.rst | 122 the requested frequency. If the request for the target frequency could not be
158 responsible for delivering the requested performance.
185 to deliver the requested processor performance
224 frequency, within limits, requested by the governor. A frequency does not have
237 conditions are met the BIOS can achieve a slightly higher speed than requested
268 to ensure that the same frequency is requested of all dependent CPUs.
|
| /Documentation/driver-api/firmware/ |
| D | fw_search_path.rst | 25 You would echo into it your custom path and firmware requested will be
|
12345678910>>...12