drivers/media/platform/samsung/s5p-mfc/s5p_mfc_iommu.h
Source file repositories/reference/linux-study-clean/drivers/media/platform/samsung/s5p-mfc/s5p_mfc_iommu.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/platform/samsung/s5p-mfc/s5p_mfc_iommu.h- Extension
.h- Size
- 513 bytes
- Lines
- 29
- Domain
- Driver Families
- Bucket
- drivers/media
- 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/iommu.h
Detected Declarations
function Copyrightfunction exynos_is_iommu_available
Annotated Snippet
#ifndef S5P_MFC_IOMMU_H_
#define S5P_MFC_IOMMU_H_
#if defined(CONFIG_EXYNOS_IOMMU)
#include <linux/iommu.h>
static inline bool exynos_is_iommu_available(struct device *dev)
{
return dev_iommu_priv_get(dev) != NULL;
}
#else
static inline bool exynos_is_iommu_available(struct device *dev)
{
return false;
}
#endif
#endif /* S5P_MFC_IOMMU_H_ */
Annotation
- Immediate include surface: `linux/iommu.h`.
- Detected declarations: `function Copyright`, `function exynos_is_iommu_available`.
- Atlas domain: Driver Families / drivers/media.
- 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.