drivers/platform/chrome/chromeos_pstore.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/chrome/chromeos_pstore.c

Extension

.c

Size

3531 bytes

Lines

146

Domain

Driver Families

Bucket

drivers/platform

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/acpi.h
• linux/dmi.h
• linux/module.h
• linux/platform_device.h
• linux/pstore_ram.h

Detected Declarations

• function chromeos_probe_acpi
• function chromeos_check_acpi
• function chromeos_check_acpi
• function chromeos_pstore_init
• function chromeos_pstore_exit
• module init chromeos_pstore_init

Annotated Snippet

module_init(chromeos_pstore_init);
module_exit(chromeos_pstore_exit);

MODULE_DESCRIPTION("ChromeOS pstore module");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/dmi.h`, `linux/module.h`, `linux/platform_device.h`, `linux/pstore_ram.h`.
• Detected declarations: `function chromeos_probe_acpi`, `function chromeos_check_acpi`, `function chromeos_check_acpi`, `function chromeos_pstore_init`, `function chromeos_pstore_exit`, `module init chromeos_pstore_init`.
• Atlas domain: Driver Families / drivers/platform.
• Implementation status: integration 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.