drivers/memory/tegra/tegra-emc-common.h

File Facts

System

Linux kernel

Corpus path

drivers/memory/tegra/tegra-emc-common.h

Extension

.h

Size

1273 bytes

Lines

47

Domain

Driver Families

Bucket

drivers/memory

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

Detected Declarations

• struct tegra_emc_rate_request
• struct tegra_emc_rate_requests
• enum tegra_emc_rate_request_type

Annotated Snippet

struct tegra_emc_rate_request {
	unsigned long min_rate;
	unsigned long max_rate;
};

struct tegra_emc_rate_requests {
	struct tegra_emc_rate_request requested_rate[TEGRA_EMC_RATE_TYPE_MAX];
	/* Protects @requested_rate. */
	struct mutex rate_lock;
	struct device *dev;
};

void tegra_emc_rate_requests_init(struct tegra_emc_rate_requests *reqs,
				  struct device *dev);

int tegra_emc_set_min_rate(struct tegra_emc_rate_requests *reqs,
			   unsigned long rate,
			   enum tegra_emc_rate_request_type type);

int tegra_emc_set_max_rate(struct tegra_emc_rate_requests *reqs,
			   unsigned long rate,
			   enum tegra_emc_rate_request_type type);

#endif /* TEGRA_EMC_COMMON_H */

Annotation

• Immediate include surface: `linux/device.h`, `linux/mutex.h`.
• Detected declarations: `struct tegra_emc_rate_request`, `struct tegra_emc_rate_requests`, `enum tegra_emc_rate_request_type`.
• Atlas domain: Driver Families / drivers/memory.
• 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.