drivers/media/platform/qcom/iris/iris_firmware.c

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/qcom/iris/iris_firmware.c

Extension

.c

Size

2635 bytes

Lines

114

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/firmware.h
• linux/firmware/qcom/qcom_scm.h
• linux/of_address.h
• linux/of_reserved_mem.h
• linux/soc/qcom/mdt_loader.h
• iris_core.h
• iris_firmware.h

Detected Declarations

• function Copyright
• function iris_fw_load
• function iris_fw_unload
• function iris_set_hw_state

Annotated Snippet

if (ret) {
			dev_err(core->dev, "qcom_scm_mem_protect_video_var failed: %d\n", ret);
			qcom_scm_pas_shutdown(IRIS_PAS_ID);
			return ret;
		}
	}

	return ret;
}

int iris_fw_unload(struct iris_core *core)
{
	return qcom_scm_pas_shutdown(IRIS_PAS_ID);
}

int iris_set_hw_state(struct iris_core *core, bool resume)
{
	return qcom_scm_set_remote_state(resume, 0);
}

Annotation

• Immediate include surface: `linux/firmware.h`, `linux/firmware/qcom/qcom_scm.h`, `linux/of_address.h`, `linux/of_reserved_mem.h`, `linux/soc/qcom/mdt_loader.h`, `iris_core.h`, `iris_firmware.h`.
• Detected declarations: `function Copyright`, `function iris_fw_load`, `function iris_fw_unload`, `function iris_set_hw_state`.
• 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.