nfp_cpp_readq(9)

💅 nfp_cpp_readq(9) — from the Kernel API Manual, bestie 🎀

okay so picture this: you're deep in the kernel, and you need to pull a whole u64 word out of a CPP location. that's it. that's the whole vibe. this function is the main character of that exact moment ✨

---

🌸 NAME 🌸

nfp_cpp_readq — literally just read a u64 word from a CPP location. one job. slays it. 💖

---

🦋 SYNOPSIS 🦋

int nfp_cpp_readq (struct nfp_cpp *cpp , u32 cpp_id , unsigned long long
address , u64 *value );

---

✨ ARGUMENTS ✨

• cpp — the CPP device handle 🫶 this is your whole ticket in, no handle no entry, periodt.
• cpp_id — the CPP ID for the operation 💅 which operation? this operation. be specific bestie.
• address — the address for the operation ⭐ yeah she's just the address. iconic of her honestly.
• value — pointer to the read buffer 🎀 this is where the word lands when it comes home. it's giving "destination" energy.

---

🔥 RETURN 🔥

0 on success, or -ERRNO 😭 so like... zero means we ate, and anything negative means check your errno, ngl.

no cap, that -ERRNO is doing a lot of heavy lifting there — it's not one specific error, it's the whole errno family. keep that in mind 🙈

---

🧚 SEE ALSO 🧚

• Kernel file ./drivers/net/ethernet/netronome/nfp/nfpcore/nfp_cpplib.c — go read the source, the source is the blueprint bestie 👑
• nfp_cpp_readl(9)
• nfp_cpp_writel(9)
• nfp_cpp_writeq(9)
• nfp_cpp_map_area(9)

like, if reading a q isn't enough for you, the l version and the write versions and the mapping one are all right there. the whole friend group fr fr 🌈

---

and that's the page!! 💜 this masterpiece of a manpage came to you courtesy of the source/version line ./drivers/net/ethernet/netrono... and it's stamped October 2026 — so yeah, she's from the future, she's from nfp_cpp_readq(9), and she's perfect. mwah 💅✨