of_k3_ringac...t_by_phandle(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

of_k3_ringacc_get_by_phandle β€” okay so this is the little function that finds you a RA by its phandle property, bestie πŸ’… (and yes, this whole page lives in the Kernel API Manual, we're in the kernel docs era now πŸŽ€)


✨ SYNOPSIS ✨

struct k3_ringacc * of_k3_ringacc_get_by_phandle (struct device_node *np
, const char *property );

Like, that's the whole signature. struct k3_ringacc * in, chaos out, we love to see it 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • np β€” the device node. literally the starting point of the whole quest, no cap πŸ“
  • property β€” -- undescribed -- πŸ’€ yeah. the docs said nothing. the manpage is giving mysterious main character energy and honestly? we respect the silence πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

So here's the tea, bestie: this returns a pointer to the RA β€” like, a struct k3_ringacc β€” and that's the slay outcome πŸ‘‘

But it can also go two other ways:

  • it returns -ENODEV if the RA is not found 😭
  • or it returns -EPROBE_DEFER if it's not yet registered β€” which is the "not me, not yet, come back later" of error codes ⏳

Lowkey iconic error-code behaviour honestly πŸ”₯


🌈 SEE ALSO 🌈

Kernel file ./include/linux/soc/ti/k3-ringacc.h β€” go read the source, iykyk πŸ“š and while you're at it, the whole friend group:


kisses bestie, that's the whole page πŸ’‹ sourced straight from the kernel file path ./include/linux/soc/ti, dated October 2026, and yes the page name still looks like of_k3_ringac...t_by_phandle(9) β€” abbreviated and unbothered, periodt πŸ§šβ€β™€οΈβ­

πŸ“¦ where this page comes from