ni_get_reg_value_roffs(9)

✨ ni_get_reg_value_roffs ✨

okay so bestie, we're in the Kernel API Manual today and the star of the show is ni_get_reg_value_roffs(9) — yes that's a whole mouthful, i know, but she's iconic and she's here to figure out the proper register value for a particular valid NI signal/terminal route 💅

---

🌸 NAME 🌸

ni_get_reg_value_roffs — literally determines the proper register value for a particular valid NI signal/terminal route. no cap, that's the whole job 🎀

---

🦋 SYNOPSIS 🦋

s8 ni_get_reg_value_roffs (int src , const int dest , const struct ni_route_tables *tables , const int direct_reg_offset );

---

💖 ARGUMENTS 💖

• src — either a direct register value or one of the NI_* signal names. pick your fighter bestie 🫶
• dest — the global-identifier for the route destination.
• tables — pointer to the relevant set of routing tables.
• direct_reg_offset — the compatibility compensation argument. this one is a little diva: she lets us arbitrarily apply an offset to src if src is a direct register value reference. and why do we need that? because it's necessary to be compatible with definitions of register values as previously exported directly to user space. periodt, that's the lore 📜

---

⭐ RETURN ⭐

the register value (>0) to be used at the destination if the src is valid for the given destination; -1 otherwise. so like… valid route = slay, invalid = -1, no in-between 😭

---

🎀 SEE ALSO 🎀

• Kernel file ./drivers/comedi/drivers/ni_routes.h
• struct ni_route_set(9)
• struct ni_device_routes(9)
• struct ni_route_tables(9)
• route_is_valid(9)
• route_register_is_valid(9)
• ni_check_trigger_arg_roffs(9)

go read those, iykyk 📚✨

---

lowkey a reminder: if the src isn't valid for that destination, you're getting -1 and that's on periodt — don't come crying to me 💀

---

and that's the whole page bestie!! brought to you by ./drivers/comedi/drivers, dated October 2026, and yes the footer says ni_get_reg_value_roffs(9) again because she loves a dramatic entrance 🌈👑💜