drivers/firmware/google/memconsole.h

File Facts

System

Linux kernel

Corpus path

drivers/firmware/google/memconsole.h

Extension

.h

Size

719 bytes

Lines

37

Domain

Driver Families

Bucket

drivers/firmware

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.

Dependency Surface

• linux/types.h

Detected Declarations

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

Annotated Snippet

#ifndef __FIRMWARE_GOOGLE_MEMCONSOLE_H
#define __FIRMWARE_GOOGLE_MEMCONSOLE_H

#include <linux/types.h>

/*
 * memconsole_setup
 *
 * Initialize the memory console, passing the function to handle read accesses.
 */
void memconsole_setup(ssize_t (*read_func)(char *, loff_t, size_t));

/*
 * memconsole_sysfs_init
 *
 * Update memory console length and create binary file
 * for firmware object.
 */
int memconsole_sysfs_init(void);

/* memconsole_exit
 *
 * Unmap the console buffer.
 */
void memconsole_exit(void);

#endif /* __FIRMWARE_GOOGLE_MEMCONSOLE_H */

Annotation

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