drivers/media/pci/pt1/pt1.c

File Facts

System

Linux kernel

Corpus path

drivers/media/pci/pt1/pt1.c

Extension

.c

Size

31531 bytes

Lines

1483

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.
• 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.
• 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/kernel.h
• linux/sched.h
• linux/sched/signal.h
• linux/hrtimer.h
• linux/delay.h
• linux/module.h
• linux/slab.h
• linux/vmalloc.h
• linux/pci.h
• linux/kthread.h
• linux/freezer.h
• linux/ratelimit.h
• linux/string.h
• linux/i2c.h
• media/dvbdev.h
• media/dvb_demux.h
• media/dmxdev.h
• media/dvb_net.h
• media/dvb_frontend.h
• tc90522.h
• qm1d1b0004.h
• dvb-pll.h

Detected Declarations

• struct pt1_buffer_page
• struct pt1_table_page
• struct pt1_buffer
• struct pt1_table
• struct pt1_adapter
• struct pt1
• struct pt1_adapter
• struct pt1_config
• enum pt1_fe_clk
• function config_demod
• function pt1_write_reg
• function pt1_read_reg
• function pt1_increment_table_count
• function pt1_init_table_count
• function pt1_register_tables
• function pt1_unregister_tables
• function pt1_sync
• function pt1_identify
• function pt1_unlock
• function pt1_reset_pci
• function pt1_reset_ram
• function pt1_do_enable_ram
• function pt1_enable_ram
• function pt1_disable_ram
• function pt1_set_stream
• function pt1_init_streams
• function pt1_filter
• function pt1_thread
• function pt1_free_page
• function pt1_cleanup_buffer
• function pt1_init_buffer
• function pt1_cleanup_table
• function pt1_init_table
• function pt1_cleanup_tables
• function pt1_init_tables
• function pt1_start_polling
• function pt1_start_feed
• function pt1_stop_polling
• function pt1_stop_feed
• function pt1_update_power
• function pt1_set_voltage
• function pt1_sleep
• function pt1_wakeup
• function pt1_free_adapter
• function pt1_alloc_adapter
• function pt1_cleanup_adapters
• function pt1_init_adapters
• function pt1_cleanup_frontend

Annotated Snippet

static struct pci_driver pt1_driver = {
	.name		= DRIVER_NAME,
	.probe		= pt1_probe,
	.remove		= pt1_remove,
	.id_table	= pt1_id_table,
	.driver.pm	= &pt1_pm_ops,
};

module_pci_driver(pt1_driver);

MODULE_AUTHOR("Takahito HIRANO <hiranotaka@zng.info>");
MODULE_DESCRIPTION("Earthsoft PT1/PT2 Driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/sched.h`, `linux/sched/signal.h`, `linux/hrtimer.h`, `linux/delay.h`, `linux/module.h`, `linux/slab.h`, `linux/vmalloc.h`.
• Detected declarations: `struct pt1_buffer_page`, `struct pt1_table_page`, `struct pt1_buffer`, `struct pt1_table`, `struct pt1_adapter`, `struct pt1`, `struct pt1_adapter`, `struct pt1_config`, `enum pt1_fe_clk`, `function config_demod`.
• Atlas domain: Driver Families / drivers/media.
• 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.