| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | field-order.rst | 28 When the driver provides or accepts images field by field rather than
89 - Images are in progressive (frame-based) format, not interlaced
93 - Images consist of the top (aka odd) field only.
96 - Images consist of the bottom (aka even) field only. Applications
97 may wish to prevent a device from capturing interlaced images
102 - Images contain both fields, interleaved line by line. The temporal
109 - Images contain both fields, the top field lines are stored first
115 - Images contain both fields, the bottom field lines are stored
136 - Images contain both fields, interleaved line by line, top field
140 - Images contain both fields, interleaved line by line, top field
|
| H A D | dev-capture.rst | 11 digitized images in memory. Today nearly all devices can capture at full
13 capture process and move images from the driver into user space.
52 capture, the latter how images are stored in memory, i. e. in RGB or YUV
54 also define how images are scaled in the process.
96 Reading Images
|
| H A D | dev-output.rst | 12 process and move images from user space to the driver.
50 the latter how images are stored in memory, i. e. in RGB or YUV format,
52 define how images are scaled in the process.
93 Writing Images
|
| H A D | pixfmt-intro.rst | 8 In order to exchange images between drivers and applications, it is
16 to convert images to one of the standard formats when needed. But the
21 images to the X Windows screen format when the video is to be displayed.
|
| H A D | vidioc-g-fbuf.rst | 47 destructive overlay copies captured video images into the video memory
48 of a graphics card. A non-destructive overlay blends video images into a
213 - The device supports clipping by chroma-keying the images. That is,
290 framebuffer pixels with video images. The blend function is:
296 images. The blend function is: output = (framebuffer pixel * alpha
305 framebuffer to clip or blend framebuffer pixels with video images,
|
| H A D | crop.rst | 36 the area actually sampled. The target are images read by the application
41 On a video output device the source are the images passed in by the
46 images are inserted.
105 defining the *target* rectangle where the images will be inserted into
315 we should scale the images to this size. */
|
| H A D | dev-overlay.rst | 13 (VGA-)video signal of a graphics card, or to store captured images
15 This can be considerable more efficient than capturing images and
110 contents with video images.
125 the latter how images are overlaid and clipped. Cropping initialization
247 images, if global alpha blending has been negotiated
|
| H A D | metafmt-pisp-be.rst | 18 The PiSP Back End processes images in tiles, and its configuration requires
41 As the ISP processes images in tiles, each set of tiles parameters describe how
|
| H A D | ext-ctrls-camera.rst | 323 feature allows to obtain clear images in situations where intensity
546 counter-clockwise direction to be applied to the captured images once
575 images are meant to be displayed in landscape mode (width > height) on the
581 display images correctly to the user.
585 V4L2_CID_CAMERA_SENSOR_ROTATION control is 180 degrees, as images will
619 side of the device, facing away from the user. The captured images are meant
627 The images once captured to memory will be rotated and the value of the
|
| /linux/Documentation/admin-guide/media/ |
| H A D | raspberrypi-pisp-be.rst | 18 The PiSP Back End ISP processes images in tiles. The handling of image
25 in DRAM memory and processing them in the PiSP Back End to obtain images usable
49 - pispbe-input: output device for images to be submitted to the ISP for
53 - pispbe-output0: first capture device for processed images.
54 - pispbe-output1: second capture device for processed images.
62 Images to be processed by the ISP are queued to the `pispbe-input` output device
69 The `pispbe-tdn_input` output video device receives images to be processed by
79 tonemapping blocks are used. The `pispbe-stitch_output` writes images to memory
|
| /linux/drivers/firmware/arm_ffa/ |
| H A D | Kconfig | 10 software images which includes communication between images in
12 virtualization extension to isolate software images provided
|
| /linux/Documentation/arch/arm/ |
| H A D | sunxi.rst | 111 https://linux-sunxi.org/images/4/4b/Allwinner_H3_Datasheet_V1.2.pdf
156 https://linux-sunxi.org/images/5/5c/Allwinner_H6_V200_Datasheet_V1.1.pdf
160 https://linux-sunxi.org/images/4/46/Allwinner_H6_V200_User_Manual_V1.1.pdf
166 https://linux-sunxi.org/images/b/b9/H616_Datasheet_V1.0_cleaned.pdf
170 https://linux-sunxi.org/images/2/24/H616_User_Manual_V1.0_cleaned.pdf
|
| /linux/arch/parisc/include/asm/ |
| H A D | perf.h | 18 /* Common Onyx and Cuda images */
37 /* Cuda only Images */
45 /* Onyx only Images */
|
| H A D | shmparam.h | 11 * https://parisc.wiki.kernel.org/images-parisc/6/68/Pa11_acd.pdf
13 * https://parisc.wiki.kernel.org/images-parisc/7/73/Parisc2.0.pdf
|
| /linux/drivers/mtd/parsers/ |
| H A D | Kconfig | 110 multiple 'images'. Each such image has a header containing its name
157 'images' in flash devices by putting a table one of the erase
159 the offsets, lengths and names of all the images stored in the
196 bool "Force read-only for RedBoot system images"
199 'FIS directory' images, enable this option.
|
| /linux/Documentation/arch/loongarch/ |
| H A D | booting.rst | 27 Header of Linux/LoongArch kernel images
30 Linux/LoongArch kernel images are EFI images. Being PE files, they have
|
| /linux/Documentation/networking/devlink/ |
| H A D | iosm.rst | 38 the Bootloader images and other modem software images.
56 PSI RAM and EBL are the RAM images which are injected to the device when the
85 place. Below is the sequence of commands used for each of the firmware images.
|
| /linux/include/sound/ |
| H A D | ak4xxx-adda.h | 48 unsigned char images[AK4XXX_IMAGE_SIZE]; /* saved register image */ member
77 (ak)->images[(chip) * 16 + (reg)]
79 ((ak)->images[(chip) * 16 + (reg)] = (val))
|
| /linux/drivers/base/firmware_loader/ |
| H A D | Kconfig | 190 Compressed firmware support does not apply to firmware images
232 images from local FLASH when the card boots. The images in FLASH may
233 be updated with new images provided by the user. Enable this device
|
| /linux/drivers/mtd/ubi/ |
| H A D | Kconfig | 3 tristate "Enable UBI - Unsorted block images"
73 a fastmap on old images, but you can set the UBI module parameter
75 images are still usable with UBI implementations without
|
| /linux/drivers/net/ethernet/qlogic/qed/ |
| H A D | qed_selftest.c | 101 /* Acquire from MFW the amount of available images */ in qed_selftest_nvram()
104 DP_ERR(p_hwfn, "Failed getting number of images\n"); in qed_selftest_nvram()
109 /* Iterate over images and validate CRC */ in qed_selftest_nvram()
|
| /linux/Documentation/devicetree/bindings/media/ |
| H A D | raspberrypi,pispbe.yaml | 15 processor that fetches images in Bayer or Grayscale format from DRAM memory
16 in tiles and produces images consumable by applications.
|
| /linux/Documentation/devicetree/bindings/mtd/partitions/ |
| H A D | linux,ubi.yaml | 7 title: Unsorted Block Images
10 UBI ("Unsorted Block Images") is a volume management system for raw
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-dell-privacy-wmi | 19 shutter assembly that is built onto the camera module to block capturing images
54 shutter assembly that is built onto the camera module to block capturing images
|
| /linux/drivers/net/ethernet/sfc/ |
| H A D | fw_formats.h | 14 /* Header layouts of firmware update images recognised by Efx NICs.
23 * Besides, some packaging formats (such as CMS/PKCS#7 signed images)
|