Lines Matching +full:sync +full:- +full:on +full:- +full:green
9 ---------------
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
22 ---------------
36 - FB_CAP_FOURCC
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
52 bits_per_pixel, grayscale, red, green, blue and transp fields.
58 - FB_TYPE_PACKED_PIXELS
62 next multiple of 8 bits or packed together into bytes depends on the visual.
67 - FB_TYPE_PLANES
75 - FB_TYPE_INTERLEAVED_PLANES
86 - FB_TYPE_FOURCC
91 - FB_VISUAL_MONO01
93 Pixels are black or white and stored on a number of bits (typically one)
102 - FB_VISUAL_MONO10
104 Pixels are black or white and stored on a number of bits (typically one)
113 - FB_VISUAL_TRUECOLOR
115 Pixels are broken into red, green and blue components, and each component
116 indexes a read-only lookup table for the corresponding value. Lookup tables
117 are device-dependent, and provide linear or non-linear ramps.
120 information red, green, blue and transp fields.
122 - FB_VISUAL_PSEUDOCOLOR and FB_VISUAL_STATIC_PSEUDOCOLOR
124 Pixel values are encoded as indices into a colormap that stores red, green and
125 blue components. The colormap is read-only for FB_VISUAL_STATIC_PSEUDOCOLOR
126 and read-write for FB_VISUAL_PSEUDOCOLOR.
131 - FB_VISUAL_DIRECTCOLOR
133 Pixels are broken into red, green and blue components, and each component
137 information red, green, blue and transp fields.
139 - FB_VISUAL_FOURCC
146 ---------------------
194 struct fb_bitfield green; /* else only length is significant */
209 __u32 left_margin; /* time from sync to picture */
210 __u32 right_margin; /* time from picture to sync */
211 __u32 upper_margin; /* time from sync to picture */
213 __u32 hsync_len; /* length of horizontal sync */
214 __u32 vsync_len; /* length of vertical sync */
215 __u32 sync; /* see FB_SYNC_* */
218 __u32 colorspace; /* colorspace for FOURCC-based modes */
232 -----------------------
235 legacy API and the FOURCC-based API.
241 non-standard formats.
247 - For grayscale formats, applications set the grayscale field to one. The red,
248 blue, green and transp fields must be set to 0 by applications and ignored by
249 drivers. Drivers must fill the red, blue and green offsets to 0 and lengths
252 - For pseudocolor formats, applications set the grayscale field to zero. The
253 red, blue, green and transp fields must be set to 0 by applications and
254 ignored by drivers. Drivers must fill the red, blue and green offsets to 0
257 - For truecolor and directcolor formats, applications set the grayscale field
258 to zero, and the red, blue, green and transp fields to describe the layout of
268 Pixel values are bits_per_pixel wide and are split in non-overlapping red,
269 green, blue and alpha (transparency) components. Location and size of each
278 type, visual and line_length fields depending on the selected format.
281 The FOURCC-based API replaces format descriptions by four character codes
284 formats. Drivers are also encouraged to implement the FOURCC-based API for RGB
287 Drivers that support the FOURCC-based API report this capability by setting
293 available in Documentation/userspace-api/media/v4l/pixfmt.rst.
298 documented in Documentation/userspace-api/media/v4l/colorspaces.rst.
300 The red, green, blue and transp fields are not used with the FOURCC-based API.
306 type, visual and line_length fields depending on the selected format. The type