drivers/gpu/drm/verisilicon/vs_bridge.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/verisilicon/vs_bridge.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/verisilicon/vs_bridge.h- Extension
.h- Size
- 839 bytes
- Lines
- 40
- 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.hdrm/drm_bridge.hdrm/drm_connector.hdrm/drm_encoder.h
Detected Declarations
struct vs_crtcstruct vs_bridgeenum vs_bridge_output_interface
Annotated Snippet
struct vs_bridge {
struct drm_bridge base;
struct drm_encoder *enc;
struct drm_connector *conn;
struct vs_crtc *crtc;
struct drm_bridge *next_bridge;
enum vs_bridge_output_interface intf;
};
static inline struct vs_bridge *drm_bridge_to_vs_bridge(struct drm_bridge *bridge)
{
return container_of(bridge, struct vs_bridge, base);
}
struct vs_bridge *vs_bridge_init(struct drm_device *drm_dev,
struct vs_crtc *crtc);
#endif /* _VS_BRIDGE_H_ */
Annotation
- Immediate include surface: `linux/types.h`, `drm/drm_bridge.h`, `drm/drm_connector.h`, `drm/drm_encoder.h`.
- Detected declarations: `struct vs_crtc`, `struct vs_bridge`, `enum vs_bridge_output_interface`.
- 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.