ti_iodelay_dt_node_to_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ti_iodelay_dt_node_to_map β€” bestie's guide to the kernel API manual ✨

okay so this is the ti_iodelay_dt_node_to_map(9) page from the Kernel API Manual, and honestly? it's a little one but she's doing her job 🫢 let's get into it.


🌸 NAME 🌸

ti_iodelay_dt_node_to_map β€” lowkey the function that maps a device tree node to the appropriate group πŸ’–


✨ SYNOPSIS ✨

int ti_iodelay_dt_node_to_map (struct pinctrl_dev *pctldev , struct
device_node *np , struct pinctrl_map **map , unsigned int *num_maps );

that's the whole signature, no cap. four args, returns an int, slay πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • pctldev β€” the pinctrl device that represents the IODelay device ✨ like, this is the one doing the representing, okay?
  • np β€” the Node Pointer (device tree) 🌳 your tree node, right there
  • map β€” the Pinctrl Map that gets returned back to the pinctrl framework πŸ¦‹ it goes back to the framework, that's the whole bit
  • num_maps β€” the Number of maps, and bestie, it's 1 πŸ’… one singular map, iconic

πŸ’œ DESCRIPTION πŸ’œ

so what does she actually do? she maps the device tree description into a group of configuration parameters for the iodelay block entry 🌈 that's it, that's the vibe. the device tree description goes in, a group of config params for the iodelay block entry comes out. main character energy fr fr ✨


πŸ‘‘ RETURN πŸ‘‘

returns 0 in case of success β€” and otherwise? an appropriate error value 😭 so like, vibe check your return code, girlies.


🌟 SEE ALSO 🌟

first up, the kernel file she lives in:

  • ./drivers/pinctrl/ti/pinctrl-ti-iodelay.c

and then the whole friend group 🫢:

literally the entire squad, go say hi πŸ’–


ngl the group ./drivers/pinctrl/ti dropped this one in October 2026, and the page name is ti_iodelay_dt_node_to_map(9) in case you forgot already πŸ™ˆ

and that's the page, bestie β€” short, sweet, and she ate πŸ“ mwah πŸ’‹πŸ§š

πŸ“¦ where this page comes from