nfp_cpp_area_phys(9)

💅 nfp_cpp_area_phys (9) — Kernel API Manual, but make it make sense

okay so bestie, welcome to the nfp_cpp_area_phys girlies' club 🎀 this is a page from the Kernel API Manual and it's literally so short you'll have time to read it and still make it to the function before the compiler does. no cap.

✨ NAME ✨

nfp_cpp_area_phys — get the physical address of a CPP area. that's it. that's the whole vibe. 🦋

---

🌸 SYNOPSIS 🌸

phys_addr_t nfp_cpp_area_phys (struct nfp_cpp_area *area );

one function, one argument, one return type, and zero drama. the way it just sits there being a getter. main character energy honestly. 👑

💖 ARGUMENTS 💖

• area — your CPP area handle. like, the handle to the area. you bring it, the function does the rest. 🫶

🧚 NOTE 🧚

okay this is the important bit so listen up: the area must have been locked down with an 'acquire' first. no acquire, no address. that's the rule. i don't make the rules, i just deliver them with sparkle ✨

⭐ RETURN ⭐

phy_addr_t of the area, or NULL. yes it's spelled phy_addr_t right there in the return section while the synopsis says phys_addr_t — that's the manpage's business, not mine, and i'm not touching it 💀

🌈 SEE ALSO 🌈

• Kernel file ./drivers/net/ethernet/netronome/nfp/nfpcore/nfp_cppcore.c
• struct nfp_cpp(9), nfp_cpp_free(9), nfp_cpp_model(9)
• nfp_cpp_interface(9), nfp_cpp_serial(9)
• nfp_cpp_area_alloc_with_name(9), nfp_cpp_area_alloc(9)
• nfp_cpp_area_alloc_acquire(9), nfp_cpp_area_free(9)
• nfp_cpp_area_acquire(9), nfp_cpp_area_acquire_nonblocking(9)
• nfp_cpp_area_release(9), nfp_cpp_area_release_free(9)
• nfp_cpp_area_read(9), nfp_cpp_area_write(9), nfp_cpp_area_size(9)
• nfp_cpp_area_name(9), nfp_cpp_area_priv(9), nfp_cpp_area_cpp(9)
• nfp_cpp_area_resource(9), nfp_cpp_area_iomem(9), nfp_cpp_area_readl(9)
• nfp_cpp_area_writel(9), nfp_cpp_area_readq(9), nfp_cpp_area_writeq(9)
• nfp_cpp_area_fill(9), nfp_cpp_area_cache_add(9), nfp_cpp_read(9)
• nfp_cpp_write(9), nfp_xpb_readl(9), nfp_xpb_writel(9)
• nfp_xpb_writelm(9), nfp_cpp_from_operations(9), nfp_cpp_priv(9)
• nfp_cpp_device(9), nfp_cpp_explicit_acquire(9)
• nfp_cpp_explicit_set_target(9), nfp_cpp_explicit_set_data(9)
• nfp_cpp_explicit_set_signal(9), nfp_cpp_explicit_set_posted(9)
• nfp_cpp_explicit_put(9), nfp_cpp_explicit_do(9)
• nfp_cpp_explicit_get(9), nfp_cpp_explicit_release(9)
• nfp_cpp_explicit_cpp(9), nfp_cpp_explicit_priv(9)

(the whole friend group showed up to the function party and honestly? iconic 💅)

---

okay that's the page!! source/version fam, this came out of ./drivers/net/ethernet/netrono... and it's dated October 2026 if you're keeping receipts 🧾 and the manual itself is nfp_cpp_area_phys(9). mwah, go lock your area with an acquire first, ilysm, bye 🍓💜