drivers/iio/accel/adxl355.h

File Facts

System

Linux kernel

Corpus path

drivers/iio/accel/adxl355.h

Extension

.h

Size

853 bytes

Lines

40

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

Detected Declarations

• struct adxl355_fractional_type
• struct device
• struct adxl355_chip_info
• enum adxl355_device_type

Annotated Snippet

struct adxl355_fractional_type {
	int integer;
	int decimal;
};

struct device;

struct adxl355_chip_info {
	const char			*name;
	u8				part_id;
	struct adxl355_fractional_type	accel_scale;
	struct adxl355_fractional_type	temp_offset;
};

extern const struct regmap_access_table adxl355_readable_regs_tbl;
extern const struct regmap_access_table adxl355_writeable_regs_tbl;
extern const struct adxl355_chip_info adxl35x_chip_info[];

int adxl355_core_probe(struct device *dev, struct regmap *regmap,
		       const struct adxl355_chip_info *chip_info);

#endif /* _ADXL355_H_ */

Annotation

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