drivers/cdx/controller/cdx_controller.h

File Facts

System

Linux kernel

Corpus path

drivers/cdx/controller/cdx_controller.h

Extension

.h

Size

773 bytes

Lines

31

Domain

Driver Families

Bucket

drivers/cdx

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

• linux/cdx/cdx_bus.h
• mcdi_functions.h

Detected Declarations

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

Annotated Snippet

#ifndef _CDX_CONTROLLER_H_
#define _CDX_CONTROLLER_H_

#include <linux/cdx/cdx_bus.h>
#include "mcdi_functions.h"

void cdx_rpmsg_post_probe(struct cdx_controller *cdx);

void cdx_rpmsg_pre_remove(struct cdx_controller *cdx);

int cdx_rpmsg_send(struct cdx_mcdi *cdx_mcdi,
		   const struct cdx_dword *hdr, size_t hdr_len,
		   const struct cdx_dword *sdu, size_t sdu_len);

void cdx_rpmsg_read_resp(struct cdx_mcdi *cdx_mcdi,
			 struct cdx_dword *outbuf, size_t offset,
			 size_t outlen);

int cdx_setup_rpmsg(struct platform_device *pdev);

void cdx_destroy_rpmsg(struct platform_device *pdev);

#endif /* _CDX_CONT_PRIV_H_ */

Annotation

• Immediate include surface: `linux/cdx/cdx_bus.h`, `mcdi_functions.h`.
• Atlas domain: Driver Families / drivers/cdx.
• 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.