drivers/gpu/drm/i915/display/intel_sbi.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/i915/display/intel_sbi.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/i915/display/intel_sbi.h- Extension
.h- Size
- 699 bytes
- Lines
- 28
- Domain
- Driver Families
- Bucket
- drivers/gpu
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.h
Detected Declarations
struct intel_displayenum intel_sbi_destination
Annotated Snippet
#ifndef _INTEL_SBI_H_
#define _INTEL_SBI_H_
#include <linux/types.h>
struct intel_display;
enum intel_sbi_destination {
SBI_ICLK,
SBI_MPHY,
};
void intel_sbi_init(struct intel_display *display);
void intel_sbi_fini(struct intel_display *display);
void intel_sbi_lock(struct intel_display *display);
void intel_sbi_unlock(struct intel_display *display);
u32 intel_sbi_read(struct intel_display *display, u16 reg,
enum intel_sbi_destination destination);
void intel_sbi_write(struct intel_display *display, u16 reg, u32 value,
enum intel_sbi_destination destination);
#endif /* _INTEL_SBI_H_ */
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct intel_display`, `enum intel_sbi_destination`.
- Atlas domain: Driver Families / drivers/gpu.
- 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.