ni_tio_set_routing(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ni_tio_set_routing(9) — the Kernel API Manual page your group chat has been waiting for

okay so picture this: you're deep in the Kernel API Manual, right, and you need to point a signal at a destination. That's literally this function. It sets the register value of the selector MUX for the given destination. MUX, as in multiplexer, as in the traffic cop of your counter. icon status fr fr ✨

🌸 NAME 🌸

ni_tio_set_routing — sets the register value of the selector MUX for the given destination. she picks the lane, she writes the value, she doesn't ask questions 💅

🦋 SYNOPSIS 🦋

int ni_tio_set_routing (struct ni_gpct_device *counter_dev , unsigned
int dest , unsigned int reg );

🎀 ARGUMENTS 🎀

  • counter_dev — pointer to the general counter device 🫶 like, the whole vibe. The device itself. You hand her the pointer and she knows what's up.
  • dest — the device-global identifier of the route destination 🗺️ not a local thing, not an "ah whatever" thing — device-global. She needs to know exactly which destination you mean.
  • reg — okay bestie, this one's got layers, listen:
    • the first several bits of this value should store the desired value to write to the register 🔥 that's the payload, the main character bits
    • all other bits are for transmitting information that modifies the mode of that particular destination/gate ✨
    • those mode bits might include a bitwise or of CR_INVERT and CR_EDGE 🧚
    • > ⚠️ note that the calling function should have already validated the correctness of this value. Not her job. She is NOT doing the vibe check for you — you already did it, right? Right?? 😭

👑 SEE ALSO 👑

the Kernel file ./drivers/comedi/drivers/ni_tio.c plus her whole friend group:

all of them ate, no notes 💖

and that's the page!! 🎀 brought to you by the legends over at ./drivers/comedi/drivers, dated October 2026 — yes, October 2026, she's ahead of her time, lowkey iconic of her. mwah 💜 slay, bye 🦋

📦 where this page comes from