drivers/iio/accel/bmi088-accel.h

File Facts

System

Linux kernel

Corpus path

drivers/iio/accel/bmi088-accel.h

Extension

.h

Size

567 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/pm.h
• linux/regmap.h
• linux/types.h

Detected Declarations

• struct device
• enum bmi_device_type

Annotated Snippet

#ifndef BMI088_ACCEL_H
#define BMI088_ACCEL_H

#include <linux/pm.h>
#include <linux/regmap.h>
#include <linux/types.h>

struct device;

enum bmi_device_type {
	BOSCH_BMI085,
	BOSCH_BMI088,
	BOSCH_BMI090L,
	BOSCH_UNKNOWN,
};

extern const struct regmap_config bmi088_regmap_conf;
extern const struct dev_pm_ops bmi088_accel_pm_ops;

int bmi088_accel_core_probe(struct device *dev, struct regmap *regmap, int irq,
			    enum bmi_device_type type);
void bmi088_accel_core_remove(struct device *dev);

#endif /* BMI088_ACCEL_H */

Annotation

• Immediate include surface: `linux/pm.h`, `linux/regmap.h`, `linux/types.h`.
• Detected declarations: `struct device`, `enum bmi_device_type`.
• 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.