iwl_mvm_start_p2p_roc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 is NL80211_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:

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