drivers/net/can/c_can/c_can_pci.c

File Facts

System

Linux kernel

Corpus path

drivers/net/can/c_can/c_can_pci.c

Extension

.c

Size

7146 bytes

Lines

296

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/can/dev.h
• c_can.h

Detected Declarations

• struct c_can_pci_data
• enum c_can_pci_reg_align
• function c_can_pci_read_reg_aligned_to_16bit
• function c_can_pci_write_reg_aligned_to_16bit
• function c_can_pci_read_reg_aligned_to_32bit
• function c_can_pci_write_reg_aligned_to_32bit
• function c_can_pci_read_reg_32bit
• function c_can_pci_write_reg_32bit
• function c_can_pci_read_reg32
• function c_can_pci_write_reg32
• function c_can_pci_reset_pch
• function c_can_pci_probe
• function c_can_pci_remove

Annotated Snippet

static struct pci_driver c_can_pci_driver = {
	.name = KBUILD_MODNAME,
	.id_table = c_can_pci_tbl,
	.probe = c_can_pci_probe,
	.remove = c_can_pci_remove,
};

module_pci_driver(c_can_pci_driver);

MODULE_AUTHOR("Federico Vaga <federico.vaga@gmail.com>");
MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("PCI CAN bus driver for Bosch C_CAN/D_CAN controller");
MODULE_DEVICE_TABLE(pci, c_can_pci_tbl);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/netdevice.h`, `linux/pci.h`, `linux/can/dev.h`, `c_can.h`.
• Detected declarations: `struct c_can_pci_data`, `enum c_can_pci_reg_align`, `function c_can_pci_read_reg_aligned_to_16bit`, `function c_can_pci_write_reg_aligned_to_16bit`, `function c_can_pci_read_reg_aligned_to_32bit`, `function c_can_pci_write_reg_aligned_to_32bit`, `function c_can_pci_read_reg_32bit`, `function c_can_pci_write_reg_32bit`, `function c_can_pci_read_reg32`, `function c_can_pci_write_reg32`.
• Atlas domain: Driver Families / drivers/net.
• 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.