drivers/usb/typec/bus.h
Source file repositories/reference/linux-study-clean/drivers/usb/typec/bus.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/usb/typec/bus.h- Extension
.h- Size
- 627 bytes
- Lines
- 31
- Domain
- Driver Families
- Bucket
- drivers/usb
- 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/usb/typec_altmode.h
Detected Declarations
struct typec_muxstruct typec_retimerstruct altmode
Annotated Snippet
struct altmode {
unsigned int id;
struct typec_altmode adev;
struct typec_mux *mux;
struct typec_retimer *retimer;
enum typec_port_data roles;
struct attribute *attrs[5];
char group_name[8];
struct attribute_group group;
const struct attribute_group *groups[2];
struct altmode *partner;
struct altmode *plug[2];
};
#define to_altmode(d) container_of(d, struct altmode, adev)
#endif /* __USB_TYPEC_ALTMODE_H__ */
Annotation
- Immediate include surface: `linux/usb/typec_altmode.h`.
- Detected declarations: `struct typec_mux`, `struct typec_retimer`, `struct altmode`.
- Atlas domain: Driver Families / drivers/usb.
- 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.