qed_chain_consume(9)

okay so bestie, we're looking at qed_chain_consume(9) from the Kernel API Manual, and it's giving “driver consumes firmware-written data” energy. let's get into it 🫶

✨ NAME ✨

qed_chain_consume is for a Chain where the driver utilizes data written by a different source — i.e., FW — and it should use this to access the passed buffers. literally that's the whole vibe 💅

🌸 SYNOPSIS 🌸

the signature is exactly this, no cap:

void * qed_chain_consume (struct qed_chain *p_chain );

🎀 ARGUMENTS 🎀

• p_chain — Chain. that's the one, bestie 🦋

🦋 RETURN 🦋

you get void*, a pointer to the next buffer written. slay ✨

🌈 SEE ALSO 🌈

the Kernel file is ./include/linux/qed/qed_chain.h, and the whole bestie lineup is:

• qed_chain_advance_page(9)
• qed_chain_return_produced(9)
• qed_chain_produce(9)
• qed_chain_get_capacity(9)
• qed_chain_recycle_consumed(9)
• qed_chain_reset(9)
• qed_chain_get_last_elem(9)
• qed_chain_set_prod(9)
• qed_chain_pbl_zero_mem(9)

mwah 💋 — this qed_chain_consume(9) page comes from source ./include/linux/qed, dated October 2026. periodt 🫶