drivers/soc/fsl/dpio/dpio-cmd.h

File Facts

System

Linux kernel

Corpus path

drivers/soc/fsl/dpio/dpio-cmd.h

Extension

.h

Size

1288 bytes

Lines

59

Domain

Driver Families

Bucket

drivers/soc

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct dpio_cmd_open
• struct dpio_rsp_get_attr
• struct dpio_stashing_dest

Annotated Snippet

struct dpio_cmd_open {
	__le32 dpio_id;
};

#define DPIO_CHANNEL_MODE_MASK		0x3

struct dpio_rsp_get_attr {
	/* cmd word 0 */
	__le32 id;
	__le16 qbman_portal_id;
	u8 num_priorities;
	u8 channel_mode;
	/* cmd word 1 */
	__le64 qbman_portal_ce_addr;
	/* cmd word 2 */
	__le64 qbman_portal_ci_addr;
	/* cmd word 3 */
	__le32 qbman_version;
	__le32 pad1;
	/* cmd word 4 */
	__le32 clk;
};

struct dpio_stashing_dest {
	u8 sdest;
};

#endif /* _FSL_DPIO_CMD_H */

Annotation

• Detected declarations: `struct dpio_cmd_open`, `struct dpio_rsp_get_attr`, `struct dpio_stashing_dest`.
• Atlas domain: Driver Families / drivers/soc.
• 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.