drivers/iio/imu/bmi160/Kconfig

Source file repositories/reference/linux-study-clean/drivers/iio/imu/bmi160/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/iio/imu/bmi160/Kconfig
Extension: [no extension]
Size: 805 bytes
Lines: 34
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
#
# BMI160 IMU driver
#

config BMI160
	tristate
	select IIO_BUFFER
	select IIO_TRIGGERED_BUFFER

config BMI160_I2C
	tristate "Bosch BMI160 I2C driver"
	depends on I2C
	select BMI160
	select REGMAP_I2C
	help
	  If you say yes here you get support for BMI160 IMU on I2C with
	  accelerometer, gyroscope and external BMG160 magnetometer.

	  This driver can also be built as a module. If so, the module will be
	  called bmi160_i2c.

config BMI160_SPI
	tristate "Bosch BMI160 SPI driver"
	depends on SPI
	select BMI160
	select REGMAP_SPI
	help
	  If you say yes here you get support for BMI160 IMU on SPI with
	  accelerometer, gyroscope and external BMG160 magnetometer.

	  This driver can also be built as a module. If so, the module will be
	  called bmi160_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.