drivers/iio/TODO

File Facts

System

Linux kernel

Corpus path

drivers/iio/TODO

Extension

[no extension]

Size

454 bytes

Lines

17

Domain

Driver Families

Bucket

drivers/iio

Inferred role

Driver Families: drivers/iio

Status

atlas-only

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

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

2020-02-29

Documentation
  - Binding docs for devices that are obviously used via device
tree
  - Yaml conversions for abandoned drivers
  - ABI Documentation
  - Audit driviers/iio/staging/Documentation

- Converting drivers from device tree centric to more generic
property handlers.

- Refactor old platform_data constructs from drivers and convert it
to state struct and using property handlers and readers.

Mailing list: linux-iio@vger.kernel.org

Annotation

• Atlas domain: Driver Families / drivers/iio.
• Implementation status: atlas-only.

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.