drivers/media/pci/ddbridge/ddbridge-main.c
Source file repositories/reference/linux-study-clean/drivers/media/pci/ddbridge/ddbridge-main.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/pci/ddbridge/ddbridge-main.c- Extension
.c- Size
- 7616 bytes
- Lines
- 314
- Domain
- Driver Families
- Bucket
- drivers/media
- 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.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- 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.hlinux/init.hlinux/interrupt.hlinux/delay.hlinux/slab.hlinux/poll.hlinux/io.hlinux/pci.hlinux/pci_ids.hlinux/timer.hlinux/i2c.hlinux/swab.hlinux/vmalloc.hddbridge.hddbridge-i2c.hddbridge-regs.hddbridge-hw.hddbridge-io.h
Detected Declarations
function ddb_irq_disablefunction ddb_msi_exitfunction ddb_irq_exitfunction ddb_removefunction ddb_irq_msifunction ddb_irq_initfunction ddb_probefunction module_init_ddbridgefunction module_exit_ddbridgemodule init module_init_ddbridge
Annotated Snippet
static struct pci_driver ddb_pci_driver = {
.name = "ddbridge",
.id_table = ddb_id_table,
.probe = ddb_probe,
.remove = ddb_remove,
};
static __init int module_init_ddbridge(void)
{
int stat;
pr_info("Digital Devices PCIE bridge driver "
DDBRIDGE_VERSION
", Copyright (C) 2010-17 Digital Devices GmbH\n");
stat = ddb_init_ddbridge();
if (stat < 0)
return stat;
stat = pci_register_driver(&ddb_pci_driver);
if (stat < 0)
ddb_exit_ddbridge(0, stat);
return stat;
}
static __exit void module_exit_ddbridge(void)
{
pci_unregister_driver(&ddb_pci_driver);
ddb_exit_ddbridge(0, 0);
}
module_init(module_init_ddbridge);
module_exit(module_exit_ddbridge);
MODULE_DESCRIPTION("Digital Devices PCIe Bridge");
MODULE_AUTHOR("Ralph and Marcus Metzler, Metzler Brothers Systementwicklung GbR");
MODULE_LICENSE("GPL v2");
MODULE_VERSION(DDBRIDGE_VERSION);
Annotation
- Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/interrupt.h`, `linux/delay.h`, `linux/slab.h`, `linux/poll.h`, `linux/io.h`, `linux/pci.h`.
- Detected declarations: `function ddb_irq_disable`, `function ddb_msi_exit`, `function ddb_irq_exit`, `function ddb_remove`, `function ddb_irq_msi`, `function ddb_irq_init`, `function ddb_probe`, `function module_init_ddbridge`, `function module_exit_ddbridge`, `module init module_init_ddbridge`.
- Atlas domain: Driver Families / drivers/media.
- Implementation status: pattern implementation candidate.
- IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.
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.