nfp_cpp_explicit_acquire(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nfp_cpp_explicit_acquire(9)

okay so first things first, bestie: this little cutie lives in the Kernel API Manual (yes, section 9, the driver-dev section, we stan) and the whole entire function name is nfp_cpp_explicit_acquire πŸŽ€


✨ NAME ✨

nfp_cpp_explicit_acquire β€” acquire an explicit access handle 🫢


✨ SYNOPSIS ✨

struct nfp_cpp_explicit * nfp_cpp_explicit_acquire (struct nfp_cpp *cpp
);

like, that's the whole call. one argument. it hands you back a pointer to a struct nfp_cpp_explicit. no cap.


✨ ARGUMENTS ✨

  • cpp β€” the NFP CPP handle πŸ’– (that's the one you're grabbing the explicit handle off of, obviously)

✨ DESCRIPTION ✨

okay so here's the tea 🍡 β€” the 'data_ref' and 'signal_ref' values are genuinely useful when you're constructing the NFP_EXPL_CSR1 and NFP_EXPL_POST values. that's it, that's the whole description, and honestly? iconic. short and slay. ✨


✨ RETURN ✨

an NFP CPP explicit handle πŸ‘‘ (a struct nfp_cpp_explicit *, if we're being specific, and we are πŸ’…)


✨ SEE ALSO ✨

the whole friend group, fr fr πŸ¦‹ β€” starting with the kernel file:

  • ./drivers/net/ethernet/netronome/nfp/nfpcore/nfp_cppcore.c

then all the besties:


πŸ’€ quick vibe check: if you acquire the explicit handle, go read nfp_cpp_explicit_release(9) too. that's your cleanup era. don't leave the handle hanging, bestie 😭

k bye, this page is brought to you by ./drivers/net/ethernet/netrono... and dated October 2026 πŸ—“οΈ β€” stay slay, go read the source, mwah πŸ’œπŸŒΈ

πŸ“¦ where this page comes from