drivers/thunderbolt/dma_port.h
Source file repositories/reference/linux-study-clean/drivers/thunderbolt/dma_port.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/thunderbolt/dma_port.h- Extension
.h- Size
- 937 bytes
- Lines
- 32
- Domain
- Driver Families
- Bucket
- drivers/thunderbolt
- 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
tb.h
Detected Declarations
struct tb_switchstruct tb_dma_port
Annotated Snippet
#ifndef DMA_PORT_H_
#define DMA_PORT_H_
#include "tb.h"
struct tb_switch;
struct tb_dma_port;
#define DMA_PORT_CSS_ADDRESS 0x3fffff
#define DMA_PORT_CSS_MAX_SIZE SZ_128
struct tb_dma_port *dma_port_alloc(struct tb_switch *sw);
void dma_port_free(struct tb_dma_port *dma);
int dma_port_flash_read(struct tb_dma_port *dma, unsigned int address,
void *buf, size_t size);
int dma_port_flash_update_auth(struct tb_dma_port *dma);
int dma_port_flash_update_auth_status(struct tb_dma_port *dma, u32 *status);
int dma_port_flash_write(struct tb_dma_port *dma, unsigned int address,
const void *buf, size_t size);
int dma_port_power_cycle(struct tb_dma_port *dma);
#endif
Annotation
- Immediate include surface: `tb.h`.
- Detected declarations: `struct tb_switch`, `struct tb_dma_port`.
- Atlas domain: Driver Families / drivers/thunderbolt.
- 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.