drivers/iio/accel/adxl380.h

File Facts

System

Linux kernel

Corpus path

drivers/iio/accel/adxl380.h

Extension

.h

Size

945 bytes

Lines

39

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 adxl380_chip_info
• enum adxl380_odr

Annotated Snippet

struct adxl380_chip_info {
	const char *name;
	const int scale_tbl[3][2];
	const int samp_freq_tbl[ADXL380_ODR_MAX];
	const struct iio_info *info;
	const int temp_offset;
	const u16 chip_id;
	const bool has_low_power;
};

extern const struct adxl380_chip_info adxl318_chip_info;
extern const struct adxl380_chip_info adxl319_chip_info;
extern const struct adxl380_chip_info adxl380_chip_info;
extern const struct adxl380_chip_info adxl382_chip_info;

int adxl380_probe(struct device *dev, struct regmap *regmap,
		  const struct adxl380_chip_info *chip_info);
bool adxl380_readable_noinc_reg(struct device *dev, unsigned int reg);

#endif /* _ADXL380_H_ */

Annotation

• Detected declarations: `struct adxl380_chip_info`, `enum adxl380_odr`.
• 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.