drivers/iio/imu/inv_mpu6050/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/iio/imu/inv_mpu6050/Kconfig

Extension

[no extension]

Size

1042 bytes

Lines

36

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-only
#
# inv-mpu6050 drivers for Invensense MPU devices and combos
#

config INV_MPU6050_IIO
	tristate
	select IIO_BUFFER
	select IIO_TRIGGERED_BUFFER
	select IIO_INV_SENSORS_TIMESTAMP

config INV_MPU6050_I2C
	tristate "Invensense MPU6050 devices (I2C)"
	depends on I2C
	select I2C_MUX
	select INV_MPU6050_IIO
	select REGMAP_I2C
	help
	  This driver supports the Invensense MPU6050/9150,
	  MPU6500/6515/6880/9250/9255, ICM20608(D)/20609/20689, ICM20600/20602/20690
	  and IAM20680 motion tracking devices over I2C.
	  This driver can be built as a module. The module will be called
	  inv-mpu6050-i2c.

config INV_MPU6050_SPI
	tristate "Invensense MPU6050 devices (SPI)"
	depends on SPI_MASTER
	select INV_MPU6050_IIO
	select REGMAP_SPI
	help
	  This driver supports the Invensense MPU6000,
	  MPU6500/6515/6880/9250/9255, ICM20608(D)/20609/20689, ICM20600/20602/20690
	  and IAM20680 motion tracking devices over SPI.
	  This driver can be built as a module. The module will be called
	  inv-mpu6050-spi.

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.