drivers/net/wireless/ralink/rt2x00/rt61pci.c
Source file repositories/reference/linux-study-clean/drivers/net/wireless/ralink/rt2x00/rt61pci.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/wireless/ralink/rt2x00/rt61pci.c- Extension
.c- Size
- 93308 bytes
- Lines
- 3023
- 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.
- 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/crc-itu-t.hlinux/delay.hlinux/etherdevice.hlinux/kernel.hlinux/module.hlinux/slab.hlinux/pci.hlinux/eeprom_93cx6.hrt2x00.hrt2x00mmio.hrt2x00pci.hrt61pci.h
Detected Declarations
struct antenna_selfunction rt61pci_bbp_writefunction rt61pci_bbp_readfunction rt61pci_rf_writefunction rt61pci_mcu_requestfunction rt61pci_eepromregister_readfunction rt61pci_eepromregister_writefunction rt61pci_rfkill_pollfunction rt61pci_brightness_setfunction rt61pci_blink_setfunction rt61pci_init_ledfunction rt61pci_config_shared_keyfunction rt61pci_config_pairwise_keyfunction rt61pci_config_filterfunction rt61pci_config_intffunction rt61pci_config_erpfunction rt61pci_config_antenna_5xfunction rt61pci_config_antenna_2xfunction rt61pci_config_antenna_2529_rxfunction rt61pci_config_antenna_2529function rt61pci_config_antfunction rt61pci_config_lna_gainfunction rt61pci_config_channelfunction rt61pci_config_txpowerfunction rt61pci_config_retry_limitfunction rt61pci_config_psfunction rt61pci_configfunction rt61pci_link_statsfunction rt61pci_set_vgcfunction rt61pci_reset_tunerfunction rt61pci_link_tunerfunction rt61pci_start_queuefunction rt61pci_kick_queuefunction rt61pci_stop_queuefunction rt61pci_check_firmwarefunction rt61pci_load_firmwarefunction rt61pci_get_entry_statefunction rt61pci_clear_entryfunction rt61pci_init_queuesfunction rt61pci_init_registersfunction rt61pci_wait_bbp_readyfunction rt61pci_init_bbpfunction rt61pci_toggle_irqfunction rt61pci_enable_radiofunction rt61pci_disable_radiofunction rt61pci_set_statefunction rt61pci_set_device_statefunction rt61pci_write_tx_desc
Annotated Snippet
static struct pci_driver rt61pci_driver = {
.name = KBUILD_MODNAME,
.id_table = rt61pci_device_table,
.probe = rt61pci_probe,
.remove = rt2x00pci_remove,
.driver.pm = &rt2x00pci_pm_ops,
};
module_pci_driver(rt61pci_driver);
Annotation
- Immediate include surface: `linux/crc-itu-t.h`, `linux/delay.h`, `linux/etherdevice.h`, `linux/kernel.h`, `linux/module.h`, `linux/slab.h`, `linux/pci.h`, `linux/eeprom_93cx6.h`.
- Detected declarations: `struct antenna_sel`, `function rt61pci_bbp_write`, `function rt61pci_bbp_read`, `function rt61pci_rf_write`, `function rt61pci_mcu_request`, `function rt61pci_eepromregister_read`, `function rt61pci_eepromregister_write`, `function rt61pci_rfkill_poll`, `function rt61pci_brightness_set`, `function rt61pci_blink_set`.
- Atlas domain: Driver Families / drivers/net.
- 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.