drivers/media/pci/pluto2/pluto2.c

File Facts

System

Linux kernel

Corpus path

drivers/media/pci/pluto2/pluto2.c

Extension

.c

Size

19070 bytes

Lines

788

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/i2c.h
• linux/i2c-algo-bit.h
• linux/init.h
• linux/interrupt.h
• linux/kernel.h
• linux/module.h
• linux/pci.h
• linux/dma-mapping.h
• linux/slab.h
• media/demux.h
• media/dmxdev.h
• media/dvb_demux.h
• media/dvb_frontend.h
• media/dvb_net.h
• media/dvbdev.h
• tda1004x.h

Detected Declarations

• struct pluto
• function pluto_readreg
• function pluto_writereg
• function pluto_rw
• function pluto_write_tscr
• function pluto_setsda
• function pluto_setscl
• function pluto_getsda
• function pluto_getscl
• function pluto_reset_frontend
• function pluto_reset_ts
• function pluto_set_dma_addr
• function pluto_dma_map
• function pluto_dma_unmap
• function pluto_start_feed
• function pluto_stop_feed
• function pluto_dma_end
• function pluto_irq
• function pluto_enable_irqs
• function pluto_disable_irqs
• function pluto_hw_init
• function pluto_hw_exit
• function divide
• function lg_tdtpe001p_tuner_set_params
• function pluto2_request_firmware
• function frontend_init
• function pluto_read_rev
• function pluto_read_mac
• function pluto_read_serial
• function pluto2_probe
• function pluto2_remove

Annotated Snippet

static struct pci_driver pluto2_driver = {
	.name = DRIVER_NAME,
	.id_table = pluto2_id_table,
	.probe = pluto2_probe,
	.remove = pluto2_remove,
};

module_pci_driver(pluto2_driver);

MODULE_AUTHOR("Andreas Oberritter <obi@linuxtv.org>");
MODULE_DESCRIPTION("Pluto2 driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/i2c.h`, `linux/i2c-algo-bit.h`, `linux/init.h`, `linux/interrupt.h`, `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `linux/dma-mapping.h`.
• Detected declarations: `struct pluto`, `function pluto_readreg`, `function pluto_writereg`, `function pluto_rw`, `function pluto_write_tscr`, `function pluto_setsda`, `function pluto_setscl`, `function pluto_getsda`, `function pluto_getscl`, `function pluto_reset_frontend`.
• 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.