drivers/comedi/drivers/amplc_pci230.c

File Facts

System

Linux kernel

Corpus path

drivers/comedi/drivers/amplc_pci230.c

Extension

.c

Size

78112 bytes

Lines

2574

Domain

Driver Families

Bucket

drivers/comedi

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/module.h
• linux/delay.h
• linux/interrupt.h
• linux/comedi/comedi_pci.h
• linux/comedi/comedi_8255.h
• linux/comedi/comedi_8254.h

Detected Declarations

• struct pci230_board
• struct pci230_private
• function PCI230
• function pci230_gat_config
• function pci230_ai_read
• function pci230_ao_mangle_datum
• function pci230_ao_write_nofifo
• function pci230_ao_write_fifo
• function pci230_claim_shared
• function pci230_release_shared
• function pci230_release_all_resources
• function pci230_divide_ns
• function pci230_choose_clk_count
• function pci230_ns_to_single_timer
• function pci230_ct_setup_ns_mode
• function pci230_cancel_ct
• function pci230_ai_eoc
• function pci230_ai_insn_read
• function pci230_ao_insn_write
• function pci230_ao_check_chanlist
• function pci230_ao_cmdtest
• function pci230_ao_stop
• function pci230_handle_ao_nofifo
• function FIFO
• function pci230_ao_inttrig_scan_begin
• function pci230_ao_start
• function pci230_ao_inttrig_start
• function pci230_ao_cmd
• function pci230_ao_cancel
• function pci230_ai_check_scan_period
• function pci230_ai_check_chanlist
• function pci230_ai_cmdtest
• function pci230_ai_update_fifo_trigger_level
• function pci230_ai_inttrig_convert
• function enabled
• function pci230_ai_inttrig_scan_begin
• function pci230_ai_stop
• function pci230_ai_start
• function pci230_ai_inttrig_start
• function pci230_handle_ai
• function pci230_ai_cmd
• function pci230_ai_cancel
• function pci230_interrupt
• function pci230_match_pci_board
• function pci230_auto_attach
• function amplc_pci230_pci_probe

Annotated Snippet

static struct pci_driver amplc_pci230_pci_driver = {
	.name		= "amplc_pci230",
	.id_table	= amplc_pci230_pci_table,
	.probe		= amplc_pci230_pci_probe,
	.remove		= comedi_pci_auto_unconfig,
};
module_comedi_pci_driver(amplc_pci230_driver, amplc_pci230_pci_driver);

MODULE_AUTHOR("Comedi https://www.comedi.org");
MODULE_DESCRIPTION("Comedi driver for Amplicon PCI230(+) and PCI260(+)");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/comedi/comedi_pci.h`, `linux/comedi/comedi_8255.h`, `linux/comedi/comedi_8254.h`.
• Detected declarations: `struct pci230_board`, `struct pci230_private`, `function PCI230`, `function pci230_gat_config`, `function pci230_ai_read`, `function pci230_ao_mangle_datum`, `function pci230_ao_write_nofifo`, `function pci230_ao_write_fifo`, `function pci230_claim_shared`, `function pci230_release_shared`.
• Atlas domain: Driver Families / drivers/comedi.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.