of_icc_get(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

okay so welcome to the of_icc_get(9) page in the Kernel API Manual, bestie ✨ — this one is all about getting a path handle from a DT node based on name. It's giving “look up your interconnect path by the name you gave it” energy, and honestly? iconic. 💅

🦋 SYNOPSIS 🦋

struct icc_path * of_icc_get (struct device *dev , const char *name );

🎀 ARGUMENTS 🎀

  • dev — device pointer for the consumer device. It's the device that's asking for the path, iykyk 🫶
  • name — interconnect path name. Literally the name of the interconnect path 🌸

🌸 DESCRIPTION 🌸

This function will search for a path between two endpoints and return an icc_path handle on success. Use icc_put to release constraints when they are not needed anymore. No cap, that cleanup part matters 💖

If the interconnect API is disabled, NULL is returned and the consumer drivers will still build. Drivers are free to handle this specifically, but they don't have to. So yes, sometimes NULL is just the vibe and not a whole crisis 😭

lowkey important: the API can be disabled and everything still builds, so don't assume NULL always means something exploded. It's valid, bestie ✨

⭐ RETURN ⭐

icc_path pointer on success or ERR_PTR on error. NULL is returned when the API is disabled or the "interconnects" DT property is missing.

So: success gets you the pointer, error gets you ERR_PTR, and NULL is the special “API disabled / no "interconnects" DT property” situation 💀✨

👑 SEE ALSO 👑

Kernel file ./drivers/interconnect/core.c

mwah 💋 this lil page is from the Kernel API Manual, source ./drivers/interconnect, dated October 2026. of_icc_get(9) out — slay and read the SEE ALSO bestie 🫶💅

📦 where this page comes from