ti_iodelay_p...nf_group_get(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ti_iodelay_pinconf_group_get — or as the header abbreviates it, ti_iodelay_p...nf_group_get(9)

okay bestie, welcome to the Kernel API Manual ✨ this is the group-chat briefing on ti_iodelay_pinconf_group_get, and yes the title up top is getting the censor-bar treatment (ti_iodelay_p...nf_group_get(9)) because kernel headers are dramatic like that 💀

🌸 NAME 🌸

ti_iodelay_pinconf_group_get — Get the group configuration 🫶

like, it literally just gets the group config. iconic behavior, no notes.

🦋 SYNOPSIS 🦋

int ti_iodelay_pinconf_group_get (struct pinctrl_dev *pctldev , unsigned
       int selector , unsigned long *config );

it's giving "three arguments, one int return, main character energy" 👑

🎀 ARGUMENTS 🎀

  • pctldev — the pinctrl device that represents the IODelay device. that's your entry point, bestie, the whole IODelay situation lives behind it ✨
  • selector — the Group selector. yeah it just picks which group you're asking about 🎯
  • config — the Configuration returned. this is where the answer lands, so pls make sure it's a real pointer 🙈

⭐ RETURN ⭐

you get the configuration if the group is valid. and if the group is not valid? it returns -EINVAL 😭 that's the no-thoughts-just-errors moment. so vibe check your selector before you commit, fr fr.

🔥 SEE ALSO 🔥

the whole friend group, in kernel file ./drivers/pinctrl/ti/pinctrl-ti-iodelay.c 💖

ok that's the entire squad and yes they're all (9) because they're all kernel API royalty 👑💅

🧚 sign-off 🧚

this little beauty lives in ./drivers/pinctrl/ti, dated October 2026 🌈 slay, stay hydrated, and may all your groups be valid so you never have to meet -EINVAL again 🍓💜

📦 where this page comes from