qed_get_reg...lts_buf_size(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

qed_get_reg_fifo_results_buf_size — returns the required buffer size for reg_fifo results, and yes bestie it's in bytes ✨

🦋 SYNOPSIS 🦋

enum dbg_status qed_get_reg_fifo_results_buf_size (struct qed_hwfn
*p_hwfn , u32 *dump_buf , u32 num_dumped_dwords , u32 *results_buf_size
);

okay so this is the whole function signature, no cap — enum dbg_status coming back at you, taking a struct qed_hwfn *p_hwfn, a u32 *dump_buf, a u32 num_dumped_dwords, and a u32 *results_buf_size. It's giving "I just do math on buffer sizes" energy and honestly? iconic 🎀

🌸 ARGUMENTS 🌸

  • p_hwfn — HW device data. like, the whole hardware function vibe, the main character of the struct world 👑
  • dump_buf — the Reg fifo dump buffer. this is where the dumped stuff lives 💖
  • num_dumped_dwords — how many dwords got dumped. dwords! not bytes! keep that in mind fr fr 🧚
  • results_buf_size — this one's (OUT), meaning the function writes into it, and it's the required buffer size in bytes for the parsed results. she's an output parameter and she knows it 💅

🔥 RETURN 🔥

Error if the parsing fails — ok otherwise. that's it, that's the whole vibe check 😭

⭐ SEE ALSO ⭐

first up, the kernel file:

./drivers/net/ethernet/qlogic/qed/qed_dbg_hsi.h

and then the whole friend group, all of them, no one left behind 🫶

✨ and that's the page, bestie ✨ this one lives in ./drivers/net/ethernet/qlogic/qed and it's dated October 2026, so like… future vibes 👑🦋 go read your buffer sizes, ily, bye 💜

📦 where this page comes from