drivers/iio/proximity/Makefile

File Facts

System

Linux kernel

Corpus path

drivers/iio/proximity/Makefile

Extension

[no extension]

Size

946 bytes

Lines

29

Domain

Driver Families

Bucket

drivers/iio

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
#
# Makefile for IIO proximity sensors
#

# When adding new entries keep the list in alphabetical order
obj-$(CONFIG_AS3935)		+= as3935.o
obj-$(CONFIG_CROS_EC_MKBP_PROXIMITY) += cros_ec_mkbp_proximity.o
obj-$(CONFIG_D3323AA)		+= d3323aa.o
obj-$(CONFIG_HX9023S)		+= hx9023s.o
obj-$(CONFIG_IRSD200)		+= irsd200.o
obj-$(CONFIG_ISL29501)		+= isl29501.o
obj-$(CONFIG_LIDAR_LITE_V2)	+= pulsedlight-lidar-lite-v2.o
obj-$(CONFIG_MB1232)		+= mb1232.o
obj-$(CONFIG_PING)		+= ping.o
obj-$(CONFIG_RFD77402)		+= rfd77402.o
obj-$(CONFIG_SRF04)		+= srf04.o
obj-$(CONFIG_SRF08)		+= srf08.o
obj-$(CONFIG_SX9310)		+= sx9310.o
obj-$(CONFIG_SX9324)		+= sx9324.o
obj-$(CONFIG_SX9360)		+= sx9360.o
obj-$(CONFIG_SX_COMMON) 	+= sx_common.o
obj-$(CONFIG_SX9500)		+= sx9500.o
obj-$(CONFIG_VCNL3020)		+= vcnl3020.o
obj-$(CONFIG_VL53L0X_I2C)	+= vl53l0x-i2c.o
obj-$(CONFIG_VL53L1X_I2C)	+= vl53l1x-i2c.o
obj-$(CONFIG_AW96103)		+= aw96103.o

Annotation

• Atlas domain: Driver Families / drivers/iio.
• 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.