drivers/net/wireless/ralink/rt2x00/rt2500pci.c
Source file repositories/reference/linux-study-clean/drivers/net/wireless/ralink/rt2x00/rt2500pci.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/wireless/ralink/rt2x00/rt2500pci.c- Extension
.c- Size
- 66250 bytes
- Lines
- 2145
- 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/delay.hlinux/etherdevice.hlinux/kernel.hlinux/module.hlinux/pci.hlinux/eeprom_93cx6.hlinux/slab.hrt2x00.hrt2x00mmio.hrt2x00pci.hrt2500pci.h
Detected Declarations
function rt2500pci_bbp_writefunction rt2500pci_bbp_readfunction rt2500pci_rf_writefunction rt2500pci_eepromregister_readfunction rt2500pci_eepromregister_writefunction rt2500pci_rfkill_pollfunction rt2500pci_brightness_setfunction rt2500pci_blink_setfunction rt2500pci_init_ledfunction rt2500pci_config_filterfunction rt2500pci_config_intffunction rt2500pci_config_erpfunction rt2500pci_config_antfunction rt2500pci_config_channelfunction rt2500pci_config_txpowerfunction rt2500pci_config_retry_limitfunction rt2500pci_config_psfunction rt2500pci_configfunction rt2500pci_link_statsfunction rt2500pci_set_vgcfunction rt2500pci_reset_tunerfunction rt2500pci_link_tunerfunction stoppedfunction rt2500pci_start_queuefunction rt2500pci_kick_queuefunction rt2500pci_stop_queuefunction rt2500pci_get_entry_statefunction rt2500pci_clear_entryfunction rt2500pci_init_queuesfunction rt2500pci_init_registersfunction rt2500pci_wait_bbp_readyfunction rt2500pci_init_bbpfunction rt2500pci_toggle_irqfunction rt2500pci_enable_radiofunction rt2500pci_disable_radiofunction rt2500pci_set_statefunction rt2500pci_set_device_statefunction rt2500pci_write_tx_descfunction rt2500pci_write_beaconfunction rt2500pci_fill_rxdonefunction rt2500pci_txdonefunction rt2500pci_enable_interruptfunction rt2500pci_txstatus_taskletfunction rt2500pci_tbtt_taskletfunction rt2500pci_rxdone_taskletfunction rt2500pci_interruptfunction rt2500pci_validate_eepromfunction rt2500pci_init_eeprom
Annotated Snippet
static struct pci_driver rt2500pci_driver = {
.name = KBUILD_MODNAME,
.id_table = rt2500pci_device_table,
.probe = rt2500pci_probe,
.remove = rt2x00pci_remove,
.driver.pm = &rt2x00pci_pm_ops,
};
module_pci_driver(rt2500pci_driver);
Annotation
- Immediate include surface: `linux/delay.h`, `linux/etherdevice.h`, `linux/kernel.h`, `linux/module.h`, `linux/pci.h`, `linux/eeprom_93cx6.h`, `linux/slab.h`, `rt2x00.h`.
- Detected declarations: `function rt2500pci_bbp_write`, `function rt2500pci_bbp_read`, `function rt2500pci_rf_write`, `function rt2500pci_eepromregister_read`, `function rt2500pci_eepromregister_write`, `function rt2500pci_rfkill_poll`, `function rt2500pci_brightness_set`, `function rt2500pci_blink_set`, `function rt2500pci_init_led`, `function rt2500pci_config_filter`.
- 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.