drivers/usb/typec/pd.h
Source file repositories/reference/linux-study-clean/drivers/usb/typec/pd.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/usb/typec/pd.h- Extension
.h- Size
- 737 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/device.hlinux/usb/typec.h
Detected Declarations
struct usb_power_deliverystruct usb_power_delivery_capabilities
Annotated Snippet
struct usb_power_delivery {
struct device dev;
int id;
u16 revision;
u16 version;
};
struct usb_power_delivery_capabilities {
struct device dev;
struct usb_power_delivery *pd;
enum typec_role role;
};
#define to_usb_power_delivery_capabilities(o) container_of(o, struct usb_power_delivery_capabilities, dev)
#define to_usb_power_delivery(o) container_of(o, struct usb_power_delivery, dev)
struct usb_power_delivery *usb_power_delivery_find(const char *name);
int usb_power_delivery_init(void);
void usb_power_delivery_exit(void);
#endif /* __USB_POWER_DELIVERY__ */
Annotation
- Immediate include surface: `linux/device.h`, `linux/usb/typec.h`.
- Detected declarations: `struct usb_power_delivery`, `struct usb_power_delivery_capabilities`.
- 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.