framer_get(9)

📦 version 7.3.1, in nixpkgs unstable

💅 framer_get(9) — the Kernel API Manual, bestie edition 🎀

okay so real talk, this is the framer_get page from the Kernel API Manual, and honestly? it's a little baddie with a big job. let's get into it ✨

🌸 NAME 🌸

framer_get — lookup and obtain a reference to a framer.

like, you go find your framer and you grab a refcount on it. main character behavior fr fr 💅

✨ SYNOPSIS ✨

struct framer * framer_get (struct device *dev , const char *con_id );

that's the whole vibe. one function, two args, returns a struct framer *. slay.

🦋 ARGUMENTS 🦋

  • dev — the device that requests the framer. yeah, this one right here is the one asking, no cap 🫶
  • con_id — the name of the framer from the device's point of view. iykyk, it's the device-centric name, not some objective universe name 💫

💖 DESCRIPTION 💖

so this function returns the framer driver — but not before getting a refcount to it, because we're responsible like that. you literally cannot just take the framer and walk away, that's not the vibe.

and if there's no such framer? it returns -ENODEV. 😭 yes, that error. it's giving "not found, bestie."

⚠️ important!! the caller is responsible for calling framer_put to release that count. do NOT forget. the refcount does not clean itself up, and that is a you problem if you ghost it 🙈

🔥 SEE ALSO 🔥

everything lives in the kernel file ./drivers/net/wan/framer/framer-core.c, and here's the whole friend group — go say hi 👑✨

and that's the whole page, periodt 🎀 this little cutie comes to you from ./drivers/net/wan/framer, dated October 2026, and the page name is framer_get(9) — remember the framer_put, bestie, that's the whole moral of the story 💜🌈

📦 where this page comes from