drivers/staging/media/atomisp/pci/ia_css_host_data.h

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/atomisp/pci/ia_css_host_data.h

Extension

.h

Size

967 bytes

Lines

38

Domain

Driver Families

Bucket

drivers/staging

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

• ia_css_types.h

Detected Declarations

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

Annotated Snippet

#ifndef __SH_CSS_HOST_DATA_H
#define __SH_CSS_HOST_DATA_H

#include <ia_css_types.h>	/* ia_css_pipe */

/**
 * @brief Allocate structure ia_css_host_data.
 *
 * @param[in]	size		Size of the requested host data
 *
 * @return
 *	- NULL, can't allocate requested size
 *	- pointer to structure, field address points to host data with size bytes
 */
struct ia_css_host_data *
ia_css_host_data_allocate(size_t size);

/**
 * @brief Free structure ia_css_host_data.
 *
 * @param[in]	me	Pointer to structure, if a NULL is passed functions
 *			returns without error. Otherwise a valid pointer to
 *			structure must be passed and a related memory
 *			is freed.
 *
 * @return
 */
void ia_css_host_data_free(struct ia_css_host_data *me);

#endif /* __SH_CSS_HOST_DATA_H */

Annotation

• Immediate include surface: `ia_css_types.h`.
• Atlas domain: Driver Families / drivers/staging.
• 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.