drivers/firmware/samsung/exynos-acpm-tmu.h

File Facts

System

Linux kernel

Corpus path

drivers/firmware/samsung/exynos-acpm-tmu.h

Extension

.h

Size

1085 bytes

Lines

29

Domain

Driver Families

Bucket

drivers/firmware

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/types.h

Detected Declarations

• struct acpm_handle

Annotated Snippet

#ifndef __EXYNOS_ACPM_TMU_H__
#define __EXYNOS_ACPM_TMU_H__

#include <linux/types.h>

struct acpm_handle;

int acpm_tmu_init(struct acpm_handle *handle, unsigned int acpm_chan_id);
int acpm_tmu_read_temp(struct acpm_handle *handle, unsigned int acpm_chan_id,
		       u8 tz, int *temp);
int acpm_tmu_set_threshold(struct acpm_handle *handle,
			   unsigned int acpm_chan_id, u8 tz,
			   const u8 temperature[8], size_t tlen);
int acpm_tmu_set_interrupt_enable(struct acpm_handle *handle,
				  unsigned int acpm_chan_id, u8 tz, u8 inten);
int acpm_tmu_tz_control(struct acpm_handle *handle, unsigned int acpm_chan_id,
			u8 tz, bool enable);
int acpm_tmu_clear_tz_irq(struct acpm_handle *handle, unsigned int acpm_chan_id,
			  u8 tz);
int acpm_tmu_suspend(struct acpm_handle *handle, unsigned int acpm_chan_id);
int acpm_tmu_resume(struct acpm_handle *handle, unsigned int acpm_chan_id);
#endif /* __EXYNOS_ACPM_TMU_H__ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct acpm_handle`.
• Atlas domain: Driver Families / drivers/firmware.
• 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.