drivers/iio/accel/adxl372.h

File Facts

System

Linux kernel

Corpus path

drivers/iio/accel/adxl372.h

Extension

.h

Size

852 bytes

Lines

34

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct adxl372_chip_info

Annotated Snippet

struct adxl372_chip_info {
	const char *name;
	const int *samp_freq_tbl;
	const int *bw_freq_tbl;
	unsigned int num_freqs;
	unsigned int act_time_scale_us;
	unsigned int act_time_scale_low_us;
	unsigned int inact_time_scale_ms;
	unsigned int inact_time_scale_low_ms;
	unsigned int max_odr;
	bool fifo_supported;
};

extern const struct adxl372_chip_info adxl371_chip_info;
extern const struct adxl372_chip_info adxl372_chip_info;

int adxl372_probe(struct device *dev, struct regmap *regmap,
		  int irq, const struct adxl372_chip_info *chip_info);
bool adxl372_readable_noinc_reg(struct device *dev, unsigned int reg);

#endif /* _ADXL372_H_ */

Annotation

• Detected declarations: `struct adxl372_chip_info`.
• 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.