drivers/dma/amba-pl08x.c

File Facts

System

Linux kernel

Corpus path

drivers/dma/amba-pl08x.c

Extension

.c

Size

82155 bytes

Lines

3073

Domain

Driver Families

Bucket

drivers/dma

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/amba/bus.h
• linux/amba/pl08x.h
• linux/debugfs.h
• linux/delay.h
• linux/device.h
• linux/dmaengine.h
• linux/dmapool.h
• linux/dma-mapping.h
• linux/export.h
• linux/init.h
• linux/interrupt.h
• linux/module.h
• linux/of.h
• linux/of_dma.h
• linux/pm_runtime.h
• linux/seq_file.h
• linux/slab.h
• linux/amba/pl080.h
• dmaengine.h
• virt-dma.h

Detected Declarations

• struct pl08x_driver_data
• struct vendor_data
• struct pl08x_bus_data
• struct pl08x_phy_chan
• struct pl08x_sg
• struct pl08x_txd
• struct pl08x_dma_chan
• struct pl08x_driver_data
• struct pl08x_lli_build_data
• struct burst_table
• enum pl08x_dma_chan_state
• function pl08x_request_mux
• function pl08x_release_mux
• function pl08x_phy_channel_busy
• function pl08x_write_lli
• function pl08x_start_next_txd
• function pl08x_pause_phy_chan
• function pl08x_resume_phy_chan
• function pl08x_terminate_phy_chan
• function get_bytes_in_phy_channel
• function get_bytes_in_lli
• function pl08x_getbytes_chan
• function pl08x_get_phy_channel
• function pl08x_put_phy_channel
• function pl08x_phy_alloc_and_start
• function pl08x_phy_reassign_start
• function pl08x_phy_free
• function pl08x_get_bytes_for_lli
• function pl08x_lli_control_bits
• function transfer
• function pl08x_fill_lli_for_desc
• function prep_byte_width_lli
• function pl08x_dump_lli
• function pl08x_dump_lli
• function list_for_each_entry
• function pl08x_free_txd
• function list_for_each_entry_safe
• function pl08x_desc_free
• function pl08x_free_txd_list
• function pl08x_free_chan_resources
• function dma_async_is_complete
• function pl08x_select_bus
• function pl08x_cctl
• function pl08x_width
• function pl08x_burst
• function pl08x_get_cctl
• function pl08x_issue_pending
• function pl08x_memcpy_cctl

Annotated Snippet

subsys_initcall(pl08x_init);

Annotation

• Immediate include surface: `linux/amba/bus.h`, `linux/amba/pl08x.h`, `linux/debugfs.h`, `linux/delay.h`, `linux/device.h`, `linux/dmaengine.h`, `linux/dmapool.h`, `linux/dma-mapping.h`.
• Detected declarations: `struct pl08x_driver_data`, `struct vendor_data`, `struct pl08x_bus_data`, `struct pl08x_phy_chan`, `struct pl08x_sg`, `struct pl08x_txd`, `struct pl08x_dma_chan`, `struct pl08x_driver_data`, `struct pl08x_lli_build_data`, `struct burst_table`.
• Atlas domain: Driver Families / drivers/dma.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.