| /linux/drivers/pps/ |
| A D | kapi.c | 163 int captured = 0; in pps_event() local
194 captured = ~0; in pps_event()
208 captured = ~0; in pps_event()
214 if (captured) { in pps_event()
|
| /linux/drivers/media/i2c/m5mols/ |
| A D | m5mols_capture.c | 142 bool captured = false; in m5mols_start_capture() local
148 captured = true; in m5mols_start_capture()
151 size = captured ? info->cap.main : 0; in m5mols_start_capture()
|
| /linux/Documentation/devicetree/bindings/media/ |
| A D | video-interface-devices.yaml | 31 defined on the external world scene to be captured when projected on the
227 casing used for video calls. The captured images are meant to be displayed
250 image once captured to memory buffers to correctly display it to users:
285 The image once captured to memory will then be rotated by 180 degrees:
317 the user. The captured images are meant to be displayed in portrait mode
351 The image once captured to memory will be rotated:
|
| /linux/Documentation/userspace-api/media/drivers/ |
| A D | cx2341x-uapi.rst | 41 If the height is not a multiple of 32 lines, then the captured video is
149 for a bitmask determining which lines are captured and 4 bytes for a magic cookie,
155 unsigned long denote which lines of the first field are captured. Bits 18-31 of
159 'ITV0': This magic number assumes all VBI lines are captured, i.e. it implicitly
163 captured VBI lines start:
|
| /linux/Documentation/ABI/testing/ |
| A D | pstore | 10 provide a generic interface to show records captured in
12 of the console log is captured, but other interesting
|
| /linux/Documentation/userspace-api/media/v4l/ |
| A D | field-order.rst | 22 fields are in fact captured at two different instances in time. An
34 However because fields were captured one after the other, arguing
48 bus in the same order they were captured, so if the top field was
49 captured first (is the older field), the top field is also transmitted
|
| A D | pixfmt-v4l2.rst | 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
|
| A D | func-poll.rst | 32 until the driver has captured data or is ready to accept data for
69 it waits until data has been captured and can be read. When the driver
|
| A D | ext-ctrls-camera.rst | 255 is set to ``TRUE`` (1), no image can be captured by the camera.
542 counter-clockwise direction to be applied to the captured images once
543 captured to memory to compensate for the camera sensor mounting rotation.
570 laptop screen casing, and is typically used for video calls. The captured
582 result rotated when captured to memory. ::
615 side of the device, facing away from the user. The captured images are meant
623 The images once captured to memory will be rotated and the value of the
|
| A D | streaming-par.rst | 15 second. If less than this number of frames is to be captured or output,
|
| A D | dev-sliced-vbi.rst | 321 captured packet is zero, the packet is empty and the contents of
328 - The video field number this data has been captured from, or shall
334 captured from, or shall be inserted at. See :ref:`vbi-525` and
363 captured frame does not carry any of the requested data services drivers
397 service be captured.
|
| A D | vidioc-streamon.rst | 58 means all images captured but not dequeued yet will be lost, likewise
|
| A D | func-select.rst | 48 execution until the driver has captured data or is ready to accept data
|
| /linux/drivers/platform/x86/intel/int1092/ |
| A D | Kconfig | 8 sensors captured in the BIOS. ACPI interface exposes this data from the BIOS
|
| /linux/Documentation/admin-guide/media/ |
| A D | ipu3.rst | 27 The Imaging Unit (ImgU) is responsible for processing images captured
75 from the raw sensors connected to the CSI2 ports. The captured frames are used
82 -- The IPU3 CSI2 receiver outputs the captured frames from the sensor in packed
129 With the above command, 10 frames are captured at 2592x1944 resolution, with
132 The captured frames are available as /tmp/frame-#.bin files.
371 For an image captured with 2592x1944 [#f4]_ resolution, with desired output
543 captured image. Two related structs are being defined,
|
| /linux/tools/perf/Documentation/ |
| A D | perf-kvm.txt | 43 files captured via perf record.
49 was captured with --guestmount in perf kvm record.
|
| A D | perf-inject.txt | 71 found in the jitdumps files captured in the input perf.data file. Use this option
|
| /linux/Documentation/admin-guide/ |
| A D | perf-security.rst | 27 captured hardware and software events.
241 user or in kernel space can be monitored and captured for later
250 monitored and captured for later analysis. Per-user per-cpu
257 monitored and captured for later analysis. Per-user per-cpu
|
| /linux/Documentation/devicetree/bindings/ipmi/ |
| A D | aspeed,ast2400-kcs-bmc.yaml | 61 thus the target interrupt controller is not captured by the BMC's
|
| /linux/fs/ocfs2/ |
| A D | Kconfig | 57 This option allows some fs statistics to be captured. Enabling
|
| /linux/Documentation/admin-guide/device-mapper/ |
| A D | dm-uevent.rst | 75 An example of the uevents generated as captured by udevmonitor is shown
|
| /linux/Documentation/networking/ |
| A D | mac80211-injection.rst | 71 facilitating replay of captured radiotap headers directly.
|
| /linux/Documentation/arm64/ |
| A D | perf.rst | 88 window at the guest entry/exit where host events are not captured.
|
| /linux/Documentation/devicetree/bindings/serial/ |
| A D | nvidia,tegra20-hsuart.txt | 44 Tx deviation of connected device can be captured over scope (or noted from
|
| /linux/Documentation/filesystems/ |
| A D | quota.rst | 30 the above events to userspace. There they can be captured by an application
|