nfp_cpp_device(9)

okay so bestie, welcome to nfp_cpp_device(9) — that's the page from the Kernel API Manual 💖 it's short, it's sweet, and it's literally just about grabbing the Linux device handle for a CPP handle. no cap.

🌸 NAME 🌸

nfp_cpp_device — get the Linux device handle of a CPP handle ✨

✨ SYNOPSIS ✨

struct device * nfp_cpp_device (struct nfp_cpp *cpp );

🦋 ARGUMENTS 🦋

• cpp — the CPP handle, bestie. that's the one and only argument.

💅 RETURN 💅

Device for the NFP CPP bus — that's the return vibe, periodt. 👑

🎀 SEE ALSO 🎀

Kernel file: ./drivers/net/ethernet/netronome/nfp/nfpcore/nfp_cppcore.c 💖

and the whole function bestie roll call, in original order:

• 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_phys(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_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)

okay that's the whole page, mwah 💋 the footer's source/version bit says ./drivers/net/ethernet/netrono... and the date is October 2026 🎀