drivers/iio/dac/ad5064.c

File Facts

System

Linux kernel

Corpus path

drivers/iio/dac/ad5064.c

Extension

.c

Size

28063 bytes

Lines

1108

Domain

Driver Families

Bucket

drivers/iio

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/device.h
• linux/err.h
• linux/module.h
• linux/kernel.h
• linux/spi/spi.h
• linux/i2c.h
• linux/slab.h
• linux/sysfs.h
• linux/regulator/consumer.h
• linux/unaligned.h
• linux/iio/iio.h
• linux/iio/sysfs.h

Detected Declarations

• struct ad5064_chip_info
• struct ad5064_state
• struct ad5064_state
• enum ad5064_regmap_type
• enum ad5064_type
• function ad5064_write
• function ad5064_sync_powerdown_mode
• function ad5064_get_powerdown_mode
• function ad5064_set_powerdown_mode
• function ad5064_read_dac_powerdown
• function ad5064_write_dac_powerdown
• function ad5064_get_vref
• function ad5064_read_raw
• function ad5064_write_raw
• function ad5064_num_vref
• function ad5064_set_config
• function ad5064_request_vref
• function ad5064_bulk_reg_disable
• function ad5064_probe
• function ad5064_spi_write
• function ad5064_spi_probe
• function ad5064_spi_register_driver
• function ad5064_spi_unregister_driver
• function ad5064_spi_register_driver
• function ad5064_spi_unregister_driver
• function ad5064_i2c_probe
• function ad5064_i2c_register_driver
• function ad5064_i2c_unregister_driver
• function ad5064_i2c_register_driver
• function ad5064_i2c_unregister_driver
• function ad5064_exit
• module init ad5064_init

Annotated Snippet

module_init(ad5064_init);

static void __exit ad5064_exit(void)
{
	ad5064_i2c_unregister_driver();
	ad5064_spi_unregister_driver();
}
module_exit(ad5064_exit);

MODULE_AUTHOR("Lars-Peter Clausen <lars@metafoo.de>");
MODULE_DESCRIPTION("Analog Devices AD5024 and similar multi-channel DACs");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/device.h`, `linux/err.h`, `linux/module.h`, `linux/kernel.h`, `linux/spi/spi.h`, `linux/i2c.h`, `linux/slab.h`, `linux/sysfs.h`.
• Detected declarations: `struct ad5064_chip_info`, `struct ad5064_state`, `struct ad5064_state`, `enum ad5064_regmap_type`, `enum ad5064_type`, `function ad5064_write`, `function ad5064_sync_powerdown_mode`, `function ad5064_get_powerdown_mode`, `function ad5064_set_powerdown_mode`, `function ad5064_read_dac_powerdown`.
• Atlas domain: Driver Families / drivers/iio.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.