drivers/ufs/host/ufs-sprd.h

File Facts

System

Linux kernel

Corpus path

drivers/ufs/host/ufs-sprd.h

Extension

.h

Size

1686 bytes

Lines

86

Domain

Driver Families

Bucket

drivers/ufs

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct ufs_sprd_rst
• struct ufs_sprd_syscon
• struct ufs_sprd_vreg
• struct ufs_sprd_priv
• struct ufs_sprd_host
• enum SPRD_UFS_RST_INDEX
• enum SPRD_UFS_SYSCON_INDEX
• enum SPRD_UFS_VREG_INDEX

Annotated Snippet

struct ufs_sprd_rst {
	const char *name;
	struct reset_control *rc;
};

struct ufs_sprd_syscon {
	const char *name;
	struct regmap *regmap;
};

struct ufs_sprd_vreg {
	const char *name;
	struct regulator *vreg;
};

struct ufs_sprd_priv {
	struct ufs_sprd_rst rci[SPRD_UFS_RST_MAX];
	struct ufs_sprd_syscon sysci[SPRD_UFS_SYSCON_MAX];
	struct ufs_sprd_vreg vregi[SPRD_UFS_VREG_MAX];
	const struct ufs_hba_variant_ops ufs_hba_sprd_vops;
};

struct ufs_sprd_host {
	struct ufs_hba *hba;
	struct ufs_sprd_priv *priv;
	void __iomem *ufs_dbg_mmio;

	enum ufs_unipro_ver unipro_ver;
};

#endif /* _UFS_SPRD_H_ */

Annotation

• Detected declarations: `struct ufs_sprd_rst`, `struct ufs_sprd_syscon`, `struct ufs_sprd_vreg`, `struct ufs_sprd_priv`, `struct ufs_sprd_host`, `enum SPRD_UFS_RST_INDEX`, `enum SPRD_UFS_SYSCON_INDEX`, `enum SPRD_UFS_VREG_INDEX`.
• Atlas domain: Driver Families / drivers/ufs.
• 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.