ur_find_group_route(9)

💅 ur_find_group_route(9) — find the route matching a function and pin set 💅

okay so welcome to ur_find_group_route(9), straight out of the Kernel API Manual ✨ this is the little helper that goes looking for the route that matches a function plus a pin set, and honestly? iconic behavior.

💖 NAME 💖

ur_find_group_route — find the route matching a function and pin set. no cap, that's the whole vibe 🎀

✨ SYNOPSIS ✨

int ur_find_group_route (struct ur_pinctrl *pctrl , const char *function
, u64 group_mask , const struct ur_func_route **route_out );

🎀 ARGUMENTS 🎀

• pctrl — the pin controller instance, bestie. your main character struct 💅
• function — the mux function name, literally the function we're matching.
• group_mask — a bitmap of pins in the selected group. yes, it's giving bitmask realness 🦋
• route_out — the returned route entry on success. this is where the good stuff lands ✨

🦋 DESCRIPTION 🦋

so lowkey a mux function can be associated with multiple hardware routing options, and each one is valid for a specific set of pins. this helper's whole job is finding the unique route whose valid_pins mask covers all pins in group_mask 🫶

the routing table has to guarantee that a given function plus pin set resolves to exactly one route. periodt. if multiple routes match, the routing description is considered ambiguous and the lookup fails. no cap, that's the rule 😭

🌸 RETURN 🌸

0 on success, or -EINVAL if no matching route exists or if the routing table contains ambiguous entries. that's it, that's the return vibe 💜

👑 SEE ALSO 👑

kernel file ./drivers/pinctrl/ultrarisc/pinctrl-ultrarisc.c — go look, iykyk 🔥

mwah 💋 — source/version: ./drivers/pinctrl/ultrarisc, date: October 2026, and this ur_find_group_route(9) page is out 🫶✨