rcar_fcp_enable(9)

📦 version 7.3.1, in nixpkgs unstable

💖 rcar_fcp_enable(9) 💖

okay bestie, welcome to the Kernel API Manual — today's main character is rcar_fcp_enable, and honestly? it's giving "small function, big responsibility." let's get into it ✨

🌸 NAME 🌸

rcar_fcp_enable — Enable an FCP. that's it, that's the whole vibe. turning it ON 🫶

🎀 SYNOPSIS 🎀

int rcar_fcp_enable (struct rcar_fcp_device *fcp );

🦋 ARGUMENTS 🦋

  • fcp — The FCP instance. like, the one. the specific FCP you're about to wake up 💅

✨ DESCRIPTION ✨

so here's the tea: before any module does any memory access through an FCP, that FCP must be enabled first — and the way you do that is by calling this function. no skipping steps, no shortcuts, it's not optional 😌

and the enable calls are reference counted, which is the important part. every successful call has to be followed by exactly one rcar_fcp_disable call once no more memory transfer can happen through the FCP. one in, one out. matching set. periodt 🔥

it returns 0 on success, or a negative error code if something goes wrong. and here's the key detail, ngl: the enable reference count isn't increased when this function returns an error. so if it fails, nothing got counted — no phantom references lurking around 💀

🌈 SEE ALSO 🌈

Kernel file ./drivers/media/platform/renesas/rcar-fcp.c

the whole friend group, honestly 👑

🧚 friendly reminder: this one's reference counted, so don't be out here calling rcar_fcp_enable and ghosting it. every successful enable needs its rcar_fcp_disable counterpart. balanced, as all things should be 💜

mwah 💋 this page lives in ./drivers/media/platform/renesas and it's dated October 2026 — signed, sealed, slayed, and shipped with love from the Kernel API Manual 🎀✨

📦 where this page comes from