drivers/media/platform/qcom/camss/Makefile

Source file repositories/reference/linux-study-clean/drivers/media/platform/qcom/camss/Makefile

File Facts

System: Linux kernel
Corpus path: drivers/media/platform/qcom/camss/Makefile
Extension: [no extension]
Size: 686 bytes
Lines: 34
Domain: Driver Families
Bucket: drivers/media
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
# Makefile for Qualcomm CAMSS driver

qcom-camss-objs += \
		camss.o \
		camss-csid.o \
		camss-csid-4-1.o \
		camss-csid-4-7.o \
		camss-csid-340.o \
		camss-csid-680.o \
		camss-csid-gen2.o \
		camss-csid-gen3.o \
		camss-csiphy.o \
		camss-csiphy-2ph-1-0.o \
		camss-csiphy-3ph-1-0.o \
		camss-format.o \
		camss-ispif.o \
		camss-tpg.o \
		camss-tpg-gen1.o \
		camss-vfe.o \
		camss-vfe-4-1.o \
		camss-vfe-4-7.o \
		camss-vfe-4-8.o \
		camss-vfe-17x.o \
		camss-vfe-340.o \
		camss-vfe-480.o \
		camss-vfe-680.o \
		camss-vfe-gen1.o \
		camss-vfe-gen3.o \
		camss-vfe-vbif.o \
		camss-video.o

obj-$(CONFIG_VIDEO_QCOM_CAMSS) += qcom-camss.o

Annotation

Atlas domain: Driver Families / drivers/media.
Implementation status: atlas-only.

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.