DRIVER SYSTEM FLOWS - DRV COMPONENT(9)

🦋 Driver system flows - drv component 🦋

okay bestie, welcome to the Kernel API Manual — this is the drv component page, section (9), and it's literally the group chat for driver system flows. ✨

🌸 NAME 🌸

Driver system flows - drv component

💖 DESCRIPTION 💖

okay so this component implements the system flows such as bus enumeration and bus removal. 🚌 No cap.

The bus dependent parts of those system flows (such as iwl_pci_probe) are in the bus specific files (the transport files). This is the code that is common among the different buses — the shared vibe, basically. 🫶

This component is also in charge of managing the several implementations of the wifi flows: it will allow to have several fw API implementation. 👑 These different implementations will differ in the way they implement mac80211's handlers too. iykyk.

The init flow wrt to the drv component looks like this, bestie:

1. The bus specific component is called from module_init
2. The bus specific component registers the bus driver
3. The bus driver calls the probe function
4. The bus specific component configures the bus
5. The bus specific component calls to the drv bus agnostic part (iwl_drv_start)
6. iwl_drv_start fetches the fw ASYNC, iwl_req_fw_callback
7. iwl_req_fw_callback parses the fw file
8. iwl_req_fw_callback starts the wifi implementation to matches the fw

👀 SEE ALSO 👀

• Kernel file ./drivers/net/wireless/intel/iwlwifi/iwl-drv.h
• iwl_drv_start(9), iwl_drv_stop(9)

that's the whole vibe 💅 — source: ./drivers/net/wireless/intel/i..., date: October 2026, and the footer energy is literally Driver syst...rv component(9) 🫶🎀