drivers/iio/imu/bmi270/bmi270.h

File Facts

System

Linux kernel

Corpus path

drivers/iio/imu/bmi270/bmi270.h

Extension

.h

Size

614 bytes

Lines

26

Domain

Driver Families

Bucket

drivers/iio

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/regmap.h
• linux/iio/iio.h

Detected Declarations

• struct bmi270_chip_info
• struct device

Annotated Snippet

struct bmi270_chip_info {
	const char *name;
	int chip_id;
	const char *fw_name;
};

extern const struct regmap_config bmi270_regmap_config;
extern const struct bmi270_chip_info bmi260_chip_info;
extern const struct bmi270_chip_info bmi270_chip_info;

struct device;
int bmi270_core_probe(struct device *dev, struct regmap *regmap,
		      const struct bmi270_chip_info *chip_info);

extern const struct dev_pm_ops bmi270_core_pm_ops;

#endif  /* BMI270_H_ */

Annotation

• Immediate include surface: `linux/regmap.h`, `linux/iio/iio.h`.
• Detected declarations: `struct bmi270_chip_info`, `struct device`.
• Atlas domain: Driver Families / drivers/iio.
• 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.