include/uapi/linux/npcm-video.h
Source file repositories/reference/linux-study-clean/include/uapi/linux/npcm-video.h
File Facts
- System
- Linux kernel
- Corpus path
include/uapi/linux/npcm-video.h- Extension
.h- Size
- 1230 bytes
- Lines
- 42
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
Dependency Surface
linux/v4l2-controls.h
Detected Declarations
enum v4l2_npcm_capture_mode
Annotated Snippet
#ifndef _UAPI_LINUX_NPCM_VIDEO_H
#define _UAPI_LINUX_NPCM_VIDEO_H
#include <linux/v4l2-controls.h>
/*
* Check Documentation/userspace-api/media/drivers/npcm-video.rst for control
* details.
*/
/*
* This control is meant to set the mode of NPCM Video Capture/Differentiation
* (VCD) engine.
*
* The VCD engine supports two modes:
* COMPLETE - Capture the next complete frame into memory.
* DIFF - Compare the incoming frame with the frame stored in memory, and
* updates the differentiated frame in memory.
*/
#define V4L2_CID_NPCM_CAPTURE_MODE (V4L2_CID_USER_NPCM_BASE + 0)
enum v4l2_npcm_capture_mode {
V4L2_NPCM_CAPTURE_MODE_COMPLETE = 0, /* COMPLETE mode */
V4L2_NPCM_CAPTURE_MODE_DIFF = 1, /* DIFF mode */
};
/*
* This control is meant to get the count of compressed HEXTILE rectangles which
* is relevant to the number of differentiated frames if VCD is in DIFF mode.
* And the count will always be 1 if VCD is in COMPLETE mode.
*/
#define V4L2_CID_NPCM_RECT_COUNT (V4L2_CID_USER_NPCM_BASE + 1)
#endif /* _UAPI_LINUX_NPCM_VIDEO_H */
Annotation
- Immediate include surface: `linux/v4l2-controls.h`.
- Detected declarations: `enum v4l2_npcm_capture_mode`.
- Atlas domain: Core OS / Core Kernel Interface.
- Implementation status: source implementation candidate.
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.