pinctrl_par...ex_with_args(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pinctrl_parse_index_with_args β€” from the Kernel API Manual, section 9 πŸŽ€

okay so bestie, buckle up, because we're diving into pinctrl_parse_index_with_args(9) and honestly? she's a little niche but she serves. πŸ’–


✨ NAME ✨

pinctrl_parse_index_with_args β€” literally just "find a node pointed by index in a list". that's the whole gig. main character energy but make it a lookup function. πŸ¦‹


🌸 SYNOPSIS 🌸

int pinctrl_parse_index_with_args (const struct device_node *np ,
                                   const char *list_name ,
                                   int index ,
                                   struct of_phandle_args *out_args );

yeah she takes four args and returns an int, no cap. πŸ’…


🧚 ARGUMENTS 🧚

  • np β€” pointer to device node with the property. like, the device node that's holding the thing you want. 🫢
  • list_name β€” property that contains the list. yes, the actual list. she's a const char *, be normal about it. ✨
  • index β€” index within the list. you point at which one you want, an int ofc. ⭐
  • out_args β€” entries in the list pointed by index. this is where the good stuff gets dropped, a struct of_phandle_args *. πŸŽ€

πŸ”₯ DESCRIPTION πŸ”₯

so what does she do? she finds the selected element in a pinctrl array. and that array is made of two parts, bestie, keep up:

  • an index within the controller
  • a number of u32 entries specified for each entry
🚨 important vibe check: the device_node is always for the parent pin controller device. always always. don't come for me on this, it's literally in the source. 😭

🌈 SEE ALSO 🌈


and that's the tea, bestie πŸ“ this whole page lives in ./drivers/pinctrl, dated October 2026 β€” so yeah, she's from the future, and she ate. πŸ’œπŸ‘‘πŸ¦‹

πŸ“¦ where this page comes from