Searched refs:Pixel (Results 1 – 25 of 36) sorted by relevance
12
20 tristate "STM32 Digital Camera Memory Interface Pixel Processor (DCMIPP) support"30 Pixel Processor (DCMIPP) available as a v4l2 device.
31 Bits Per Pixel34 * PCLK: Pixel Clock41 * PPLL: Pixel PLL
26 * **Output Pixel Processing (OPP)**: Process and format pixels to be sent to66 1. Pixel data interface (red): Represents the pixel data flow;
90 Pixel blend mode is a DRM plane composition property of :c:type:`drm_plane` used to
91 #define LCCR1_DisWdth(Pixel) (((Pixel) - 1) << FShft (LCCR1_PPL)) argument
47 tristate "NXP i.MX Pixel Pipeline (PXP)"53 The i.MX Pixel Pipeline is a memory-to-memory engine for scaling,
5 Pixel data transmitter and receiver drivers62 Pixel rate
31 Pixel sampling rate in the device's pixel array. This control is
145 - IN: Pixel format for which the frame sizes are enumerated.
131 - IN: Pixel format for which the frame intervals are enumerated.
661 - Pixel data stream from Sensor A665 - Pixel data stream from Sensor B677 - Pixel data stream from Sensor A681 - Pixel data stream from Sensor B
109 - Graphics content. Pixel data should be passed unfiltered and
391 Pixel format erratum.
116 - Pixel clock in Hz. Ex. 74.25MHz->74250000
15 Pixel Valve (DRM CRTC)
55 The Pixel lightbar has a number of built-in sequences
33 imx-pxp i.MX Pixel Pipeline (PXP)
39 hardware blocks. The VFE has different input interfaces. The PIX (Pixel) input
3 * Device tree for Google Pixel 3a, adapted from google-blueline device tree,30 model = "Google Pixel 3a";
20 /* Pixel clock, porches, etc */
33 Pixel clock in picoseconds
124 Pixel values are encoded as indices into a colormap that stores red, green and268 Pixel values are bits_per_pixel wide and are split in non-overlapping red,
20 Pixel Array sub-device
173 tristate "Chromebook Pixel's lightbar support"177 This option exposes the Chromebook Pixel's lightbar to
1713 #define LCCR1_DisWdth(Pixel) /* Display Width [16..1024 pix.] */ \ argument1714 (((Pixel) - 16)/16 << FShft (LCCR1_PPL))