sound/soc/sof/amd/pci-rmb.c
Source file repositories/reference/linux-study-clean/sound/soc/sof/amd/pci-rmb.c
File Facts
- System
- Linux kernel
- Corpus path
sound/soc/sof/amd/pci-rmb.c- Extension
.c- Size
- 2880 bytes
- Lines
- 105
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/pci.hlinux/platform_device.hsound/sof.hsound/soc-acpi.h../ops.h../sof-pci-dev.h../../amd/mach-config.hacp.hacp-dsp-offset.h
Detected Declarations
function acp_pci_rmb_probefunction acp_pci_rmb_remove
Annotated Snippet
static struct pci_driver snd_sof_pci_amd_rmb_driver = {
.name = KBUILD_MODNAME,
.id_table = rmb_pci_ids,
.probe = acp_pci_rmb_probe,
.remove = acp_pci_rmb_remove,
};
module_pci_driver(snd_sof_pci_amd_rmb_driver);
MODULE_LICENSE("Dual BSD/GPL");
MODULE_DESCRIPTION("REMBRANDT SOF Driver");
MODULE_IMPORT_NS("SND_SOC_SOF_AMD_COMMON");
MODULE_IMPORT_NS("SND_SOC_SOF_PCI_DEV");
Annotation
- Immediate include surface: `linux/module.h`, `linux/pci.h`, `linux/platform_device.h`, `sound/sof.h`, `sound/soc-acpi.h`, `../ops.h`, `../sof-pci-dev.h`, `../../amd/mach-config.h`.
- Detected declarations: `function acp_pci_rmb_probe`, `function acp_pci_rmb_remove`.
- 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.