drivers/iio/accel/bma220.h

File Facts

System

Linux kernel

Corpus path

drivers/iio/accel/bma220.h

Extension

.h

Size

687 bytes

Lines

29

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

Detected Declarations

• struct device

Annotated Snippet

#ifndef _BMA220_H
#define _BMA220_H

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

#define BMA220_REG_WDT				0x17
#define BMA220_WDT_MASK				GENMASK(2, 1)
#define BMA220_WDT_OFF				0x0
#define BMA220_WDT_1MS				0x2
#define BMA220_WDT_10MS				0x3

struct device;

extern const struct regmap_config bma220_i2c_regmap_config;
extern const struct regmap_config bma220_spi_regmap_config;
extern const struct dev_pm_ops bma220_pm_ops;

int bma220_common_probe(struct device *dev, struct regmap *regmap, int irq);

#endif

Annotation

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