drivers/gpu/drm/i915/vlv_iosf_sb.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/i915/vlv_iosf_sb.h

Extension

.h

Size

795 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
• drm/intel/vlv_iosf_sb_regs.h

Detected Declarations

• struct drm_device
• struct drm_i915_private

Annotated Snippet

#ifndef _VLV_IOSF_SB_H_
#define _VLV_IOSF_SB_H_

#include <linux/types.h>

#include <drm/intel/vlv_iosf_sb_regs.h>

struct drm_device;
struct drm_i915_private;

void vlv_iosf_sb_init(struct drm_i915_private *i915);
void vlv_iosf_sb_fini(struct drm_i915_private *i915);

void vlv_iosf_sb_get(struct drm_device *drm, unsigned long unit_mask);
void vlv_iosf_sb_put(struct drm_device *drm, unsigned long unit_mask);

u32 vlv_iosf_sb_read(struct drm_device *drm, enum vlv_iosf_sb_unit unit, u32 addr);
int vlv_iosf_sb_write(struct drm_device *drm, enum vlv_iosf_sb_unit unit, u32 addr, u32 val);

extern const struct intel_display_vlv_iosf_interface i915_display_vlv_iosf_interface;

#endif /* _VLV_IOSF_SB_H_ */

Annotation

• Immediate include surface: `linux/types.h`, `drm/intel/vlv_iosf_sb_regs.h`.
• Detected declarations: `struct drm_device`, `struct drm_i915_private`.
• 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.