drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.h

File Facts

System

Linux kernel

Corpus path

drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_pdphy.h

Extension

.h

Size

991 bytes

Lines

38

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/platform_device.h
• linux/regmap.h

Detected Declarations

• struct pmic_typec_pdphy_irq_params
• struct pmic_typec_pdphy_resources
• struct pmic_typec_pdphy

Annotated Snippet

struct pmic_typec_pdphy_irq_params {
	int				virq;
	char				*irq_name;
};

struct pmic_typec_pdphy_resources {
	unsigned int				nr_irqs;
	const struct pmic_typec_pdphy_irq_params	irq_params[PMIC_PDPHY_MAX_IRQS];
};

/* API */
struct pmic_typec_pdphy;

extern const struct pmic_typec_pdphy_resources pm8150b_pdphy_res;
int qcom_pmic_typec_pdphy_probe(struct platform_device *pdev,
				struct pmic_typec *tcpm,
				const struct pmic_typec_pdphy_resources *res,
				struct regmap *regmap,
				u32 base);
int qcom_pmic_typec_pdphy_stub_probe(struct platform_device *pdev,
				     struct pmic_typec *tcpm);

#endif /* __QCOM_PMIC_TYPEC_PDPHY_H__ */

Annotation

• Immediate include surface: `linux/platform_device.h`, `linux/regmap.h`.
• Detected declarations: `struct pmic_typec_pdphy_irq_params`, `struct pmic_typec_pdphy_resources`, `struct pmic_typec_pdphy`.
• 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.