Documentation/userspace-api/media/v4l/pixfmt-bayer.rst

Source file repositories/reference/linux-study-clean/Documentation/userspace-api/media/v4l/pixfmt-bayer.rst

File Facts

System: Linux kernel
Corpus path: Documentation/userspace-api/media/v4l/pixfmt-bayer.rst
Extension: .rst
Size: 831 bytes
Lines: 36
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

.. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
.. c:namespace:: V4L

.. _pixfmt-bayer:

*****************
Raw Bayer Formats
*****************

Description
===========

The raw Bayer formats are used by image sensors before much if any processing is
performed on the image. The formats contain green, red and blue components, with
alternating lines of red and green, and blue and green pixels in different
orders. See also `the Wikipedia article on Bayer filter
<https://en.wikipedia.org/wiki/Bayer_filter>`__.


.. toctree::
    :maxdepth: 1

    pixfmt-rawnn-cru
    pixfmt-srggb8
    pixfmt-srggb8-pisp-comp
    pixfmt-srggb10
    pixfmt-srggb10p
    pixfmt-srggb10alaw8
    pixfmt-srggb10dpcm8
    pixfmt-srggb10-ipu3
    pixfmt-srggb12
    pixfmt-srggb12p
    pixfmt-srggb14
    pixfmt-srggb14p
    pixfmt-srggb16

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.