icc_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… icc_get(9) β€” the Kernel API Manual glow-up, bestie ✨

Okay so real talk, this is the icc_get(9) man page from the Kernel API Manual and honestly it's way more iconic than it lets on. It's all about grabbing yourself a path handle between two endpoints, and I'm gonna walk you through it like we're texting at 2am. 🫢


🌸 NAME 🌸

icc_get β€” get a path handle between two endpoints. That's the whole vibe. Lowkey does exactly what it says on the tin. ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

struct icc_path * icc_get (struct device *dev , const char *src , const char *dst );

Like, that's the function signature and you should copy it exactly, no cap. πŸ’–


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” device pointer for the consumer device. Basically "who's asking for this path", iykyk.
  • src β€” source node name. The starting point, the main character of the journey. 🌟
  • dst β€” destination node name. Where we're headed, the final boss. 🏁

πŸ”₯ DESCRIPTION πŸ”₯

So here's the tea: this function will search for a path between two endpoints and return an icc_path handle on success. That's it, that's the whole move. πŸ’…

⚠️ Bestie, listen: use icc_put to release constraints when they are not needed anymore. Don't just leave them hanging, it's giving clingy ex energy and the kernel will Not be amused. 😭

πŸ‘‘ RETURN πŸ‘‘

  • Returns an icc_path pointer on success. Slay. πŸŽ‰
  • Returns ERR_PTR on error. Not slay, but at least it tells you. πŸ’€
  • Returns NULL when the API is disabled. It's literally not even available, so don't come for it. πŸ™ˆ

🌈 SEE ALSO 🌈

Okay so there are a LOT of friends in this friend group, let me introduce you:

That's the whole crew, every single one, don't skip a single name or I will know. πŸ‘€


~ cute sign-off time ~ 🧚

This lil masterpiece lives in ./drivers/interconnect, and it's dated October 2026 in the kernel docs, so yeah, future vibes. Periodt. πŸ’œβœ¨

πŸ“¦ where this page comes from