sound/pci/asihpi/hpimsgx.h

File Facts

System

Linux kernel

Corpus path

sound/pci/asihpi/hpimsgx.h

Extension

.h

Size

672 bytes

Lines

26

Domain

Driver Families

Bucket

sound/pci

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

• hpi_internal.h

Detected Declarations

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

Annotated Snippet

AudioScience HPI driver
    Copyright (C) 1997-2011  AudioScience Inc. <support@audioscience.com>


 HPI Extended Message Handler Functions

(C) Copyright AudioScience Inc. 1997-2003
******************************************************************************/

#ifndef _HPIMSGX_H_
#define _HPIMSGX_H_

#include "hpi_internal.h"

#define HPIMSGX_ALLADAPTERS     (0xFFFF)

void hpi_send_recv_ex(struct hpi_message *phm, struct hpi_response *phr,
	void *h_owner);

#define HPI_MESSAGE_LOWER_LAYER hpi_send_recv_ex

#endif				/* _HPIMSGX_H_ */

Annotation

• Immediate include surface: `hpi_internal.h`.
• Atlas domain: Driver Families / sound/pci.
• 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.