ENUM HAL_RX_BUF_RETURN_BUF_MANAGER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

enum hal_rx_buf_return_buf_manager β€” the manager that decides where your returned rx buffers go, bestie πŸŽ€

So this is a page from the Kernel API Manual, section 9, and it's literally all about enum hal_rx_..._buf_manager(9). Buckle up, it's a whole vibe ✨


🌸 SYNOPSIS 🌸

enum hal_rx_buf_return_buf_manager {
    HAL_RX_BUF_RBM_WBM_IDLE_BUF_LIST ,
    HAL_RX_BUF_RBM_WBM_DEV0_IDLE_DESC_LIST ,
    HAL_RX_BUF_RBM_WBM_DEV1_IDLE_DESC_LIST ,
    HAL_RX_BUF_RBM_WBM_DEV2_IDLE_DESC_LIST ,
    HAL_RX_BUF_RBM_FW_BM ,
    HAL_RX_BUF_RBM_SW0_BM ,
    HAL_RX_BUF_RBM_SW1_BM ,
    HAL_RX_BUF_RBM_SW2_BM ,
    HAL_RX_BUF_RBM_SW3_BM ,
    HAL_RX_BUF_RBM_SW4_BM ,
    HAL_RX_BUF_RBM_SW5_BM ,
    HAL_RX_BUF_RBM_SW6_BM

};

πŸ¦‹ Constants πŸ¦‹

Okay so every single member, one by one, no skips, we're doing the whole thing 🫢

  • HAL_RX_BUF_RBM_WBM_IDLE_BUF_LIST β€” buffer gets returned to the WBM idle buffer list. that's it, that's the whole gig πŸ’…
  • HAL_RX_BUF_RBM_WBM_DEV0_IDLE_DESC_LIST β€” descriptor goes back to the WBM idle descriptor list, and it's device 0's WBM that gets chosen when you're in a multi-device config πŸ‘‘
  • HAL_RX_BUF_RBM_WBM_DEV1_IDLE_DESC_LIST β€” same descriptor-return-to-WBM-idle-descriptor-list situation, but device 1's WBM is the one picked in a multi-device config ✨
  • HAL_RX_BUF_RBM_WBM_DEV2_IDLE_DESC_LIST β€” and again, descriptor back to the WBM idle descriptor list, this time device 2's WBM is chosen when it's a multi-device config πŸ¦‹
  • HAL_RX_BUF_RBM_FW_BM β€” buffer gets returned to FW. short and sweet fr fr
  • HAL_RX_BUF_RBM_SW0_BM β€” for ring 0 β€” it's returned to host πŸ’–
  • HAL_RX_BUF_RBM_SW1_BM β€” for ring 1 β€” returned to host 🌸
  • HAL_RX_BUF_RBM_SW2_BM β€” for ring 2 β€” returned to host πŸŽ€
  • HAL_RX_BUF_RBM_SW3_BM β€” for ring 3 β€” returned to host ⭐
  • HAL_RX_BUF_RBM_SW4_BM β€” for ring 4 β€” returned to host 🌈
  • HAL_RX_BUF_RBM_SW5_BM β€” for ring 5 β€” returned to host πŸ’œ
  • HAL_RX_BUF_RBM_SW6_BM β€” for ring 6 β€” returned to host 🧚

Lowkey the rings are all the same energy, just different numbers, and honestly? iconic consistency πŸ’€


🧚 SEE ALSO 🧚

  • Kernel file ./drivers/net/wireless/ath/ath12k/hal.h enum
  • hal_reo_cmd_type(9)
  • enum hal_reo_cmd_status(9)

Like, go read those too if you're obsessed with REO stuff, iykyk πŸ”₯


ngl there are no warnings or exit statuses on this one β€” it's just an enum and it knows it. main character energy only πŸ‘‘

okay that's the whole page, you ate it, periodt πŸ’…βœ¨ this little drop came to you from ./drivers/net/wireless/ath/ath12k β€” October 2026, go forth and return those buffers correctly bestie πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from