drivers/net/can/m_can/m_can_pci.c

File Facts

System

Linux kernel

Corpus path

drivers/net/can/m_can/m_can_pci.c

Extension

.c

Size

4895 bytes

Lines

209

Domain

Driver Families

Bucket

drivers/net

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/kernel.h
• linux/module.h
• linux/netdevice.h
• linux/pci.h
• linux/pm_runtime.h
• m_can.h

Detected Declarations

• struct m_can_pci_priv
• function iomap_read_reg
• function iomap_read_fifo
• function iomap_write_reg
• function iomap_write_fifo
• function m_can_pci_probe
• function m_can_pci_remove
• function m_can_pci_suspend
• function m_can_pci_resume

Annotated Snippet

static struct pci_driver m_can_pci_driver = {
	.name = "m_can_pci",
	.probe = m_can_pci_probe,
	.remove = m_can_pci_remove,
	.id_table = m_can_pci_id_table,
	.driver = {
		.pm = &m_can_pci_pm_ops,
	},
};

module_pci_driver(m_can_pci_driver);

MODULE_AUTHOR("Felipe Balbi (Intel)");
MODULE_AUTHOR("Jarkko Nikula <jarkko.nikula@linux.intel.com>");
MODULE_AUTHOR("Raymond Tan <raymond.tan@intel.com>");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("CAN bus driver for Bosch M_CAN controller on PCI bus");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/netdevice.h`, `linux/pci.h`, `linux/pm_runtime.h`, `m_can.h`.
• Detected declarations: `struct m_can_pci_priv`, `function iomap_read_reg`, `function iomap_read_fifo`, `function iomap_write_reg`, `function iomap_write_fifo`, `function m_can_pci_probe`, `function m_can_pci_remove`, `function m_can_pci_suspend`, `function m_can_pci_resume`.
• Atlas domain: Driver Families / drivers/net.
• 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.