sound/soc/loongson/loongson_i2s_pci.c

File Facts

System

Linux kernel

Corpus path

sound/soc/loongson/loongson_i2s_pci.c

Extension

.c

Size

3029 bytes

Lines

110

Domain

Driver Families

Bucket

sound/soc

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/delay.h
• linux/pm_runtime.h
• linux/dma-mapping.h
• linux/acpi.h
• linux/pci.h
• sound/soc.h
• loongson_i2s.h
• loongson_dma.h

Detected Declarations

• function loongson_i2s_pci_probe

Annotated Snippet

static struct pci_driver loongson_i2s_driver = {
	.name = DRIVER_NAME,
	.id_table = loongson_i2s_ids,
	.probe = loongson_i2s_pci_probe,
	.driver = {
		.pm = pm_sleep_ptr(&loongson_i2s_pm),
	},
};
module_pci_driver(loongson_i2s_driver);

MODULE_DESCRIPTION("Loongson I2S Master Mode ASoC Driver");
MODULE_AUTHOR("Loongson Technology Corporation Limited");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/delay.h`, `linux/pm_runtime.h`, `linux/dma-mapping.h`, `linux/acpi.h`, `linux/pci.h`, `sound/soc.h`, `loongson_i2s.h`.
• Detected declarations: `function loongson_i2s_pci_probe`.
• Atlas domain: Driver Families / sound/soc.
• Implementation status: pattern 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.