drivers/ufs/host/ufs-rockchip.h

File Facts

System

Linux kernel

Corpus path

drivers/ufs/host/ufs-rockchip.h

Extension

.h

Size

3243 bytes

Lines

91

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_rockchip_host

Annotated Snippet

struct ufs_rockchip_host {
	struct ufs_hba *hba;
	void __iomem *ufs_phy_ctrl;
	void __iomem *ufs_sys_ctrl;
	void __iomem *mphy_base;
	struct gpio_desc *rst_gpio;
	struct reset_control *rst;
	struct clk *ref_out_clk;
	struct clk_bulk_data *clks;
	uint64_t caps;
};

#define ufs_sys_writel(base, val, reg)                                    \
	writel((val), (base) + (reg))
#define ufs_sys_readl(base, reg) readl((base) + (reg))
#define ufs_sys_set_bits(base, mask, reg)                                 \
	ufs_sys_writel(                                                   \
		(base), ((mask) | (ufs_sys_readl((base), (reg)))), (reg))
#define ufs_sys_ctrl_clr_bits(base, mask, reg)                                 \
	ufs_sys_writel((base),                                            \
			    ((~(mask)) & (ufs_sys_readl((base), (reg)))), \
			    (reg))

#endif /* _UFS_ROCKCHIP_H_ */

Annotation

• Detected declarations: `struct ufs_rockchip_host`.
• 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.