include/drm/drm_privacy_screen_machine.h
Source file repositories/reference/linux-study-clean/include/drm/drm_privacy_screen_machine.h
File Facts
- System
- Linux kernel
- Corpus path
include/drm/drm_privacy_screen_machine.h- Extension
.h- Size
- 1281 bytes
- Lines
- 47
- Domain
- Repository Root And Misc
- Bucket
- include
- Inferred role
- Repository Root And Misc: implementation source
- Status
- source implementation candidate
Why This File Exists
Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/list.h
Detected Declarations
struct drm_privacy_screen_lookupfunction drm_privacy_screen_lookup_init
Annotated Snippet
struct drm_privacy_screen_lookup {
/** @list: Lookup list list-entry. */
struct list_head list;
/** @dev_id: Consumer device name or NULL to match all devices. */
const char *dev_id;
/** @con_id: Consumer connector name or NULL to match all connectors. */
const char *con_id;
/** @provider: dev_name() of the privacy_screen provider. */
const char *provider;
};
void drm_privacy_screen_lookup_add(struct drm_privacy_screen_lookup *lookup);
void drm_privacy_screen_lookup_remove(struct drm_privacy_screen_lookup *lookup);
#if IS_ENABLED(CONFIG_DRM_PRIVACY_SCREEN) && IS_ENABLED(CONFIG_X86)
void drm_privacy_screen_lookup_init(void);
void drm_privacy_screen_lookup_exit(void);
#else
static inline void drm_privacy_screen_lookup_init(void)
{
}
static inline void drm_privacy_screen_lookup_exit(void)
{
}
#endif
#endif
Annotation
- Immediate include surface: `linux/list.h`.
- Detected declarations: `struct drm_privacy_screen_lookup`, `function drm_privacy_screen_lookup_init`.
- Atlas domain: Repository Root And Misc / include.
- 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.