iwl_mvm_start_p2p_roc(9)
π iwl_mvm_start_p2p_roc β the kernel API manual, bestie edition β¨
Okay so real talk, this page is from the Kernel API Manual and it's literally all about iwl_mvm_start_p2p_roc(9). Buckle up, we're going on a channel π‘
πΈ NAME πΈ
iwl_mvm_start_p2p_roc β start remain on channel for p2p device functionality. That's it, that's the whole vibe π«Ά
β SYNOPSIS β
int iwl_mvm_start_p2p_roc (struct iwl_mvm *mvm , struct ieee80211_vif
*vif , int duration , enum ieee80211_roc_type type );
Look at her. Iconic signature. No notes. π
π ARGUMENTS π
mvmβ the mvm component. your main character struct πvifβ the virtual interface for which the roc is requested. Heads up bestie: it is assumed that the vif type isNL80211_IFTYPE_P2P_DEVICEβ so like, don't come in here with some other type, it's giving assumptions πdurationβ the requested duration in millisecond for the fw to be on the channel that is bound to the vif. milliseconds, not vibes πtypeβ the remain on channel request type. yes, there are types, and yes, this is one of them β¨
π¦ DESCRIPTION π¦
So here's the tea β β this function can be used to issue a remain on channel session, which means the fw will stay in the channel for the request duration milliseconds. It's staying. It's committed. It's not leaving the channel, periodt π
And the way that this function is async?? Meaning it only issues the ROC request but does not wait for it to start. She's like "sent π" and moves on with her life, lowkey the most efficient queen ever.
Once the FW is ready to serve the ROC request, it will issue a notification to the driver that it is on the requested channel π And once the FW completes the ROC request it will issue another notification to the driver. Two notifications, one channel, no cap. π§
π₯ RETURN π₯
negative error code or 0 on success π
(so like, 0 = slay, negative = the situation is not slaying π)
π SEE ALSO π
Kernel file ./drivers/net/wireless/intel/iwlwifi/mvm/time-event.h β Time Events - what is it?(9), Abstraction to the driver(9), plus the whole friend group honestly:
iwl_mvm_protect_session(9)iwl_mvm_stop_session_protection(9)iwl_mvm_rx_roc_notif(9)iwl_mvm_stop_roc(9)iwl_mvm_remove_time_event(9)iwl_mvm_te_clear_data(9)iwl_mvm_schedule_csa_period(9)iwl_mvm_te_scheduled(9)iwl_mvm_schedule_session_protection(9)iwl_mvm_rx_session_protect_notif(9)
Go read them bestie, they're all linked, it's a whole ecosystem π«Ά
okay that's the page!! it lives over at ./drivers/net/wireless/intel/i... and it's dated October 2026, and the man name is iwl_mvm_start_p2p_roc(9) in case you forgot already π bye, ily, go start some ROC sessions responsibly β¨ππ¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms