__zynqmp_clock_get_topology(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __zynqmp_clock_get_topology(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual ✨ β€” this one's a little internal helper coming at you straight out of the kernel, and honestly? it's giving "backstage pass" energy. no cap.


🌸 NAME 🌸

__zynqmp_clock_get_topology β€” the function that grabs the topology data of a clock out of the firmware response data πŸŽ€ lowkey the whole point of the function, and it ate.


πŸ¦‹ SYNOPSIS πŸ¦‹

int __zynqmp_clock_get_topology (struct clock_topology *topology ,
       struct topology_resp *response , u32 *nnodes );

three args, one int, that's the vibe πŸ’œ


✨ ARGUMENTS ✨

  • topology β€” Clock topology. this is where the topology info lands, main character energy fr 🫢
  • response β€” Clock topology data received from firmware. yes, the firmware handed it over, and yes, we're reading it πŸ‘‘
  • nnodes β€” Number of nodes. literally just how many nodes we're dealing with πŸ”₯

πŸ’€ RETURN πŸ’€

0 on success, else error+reason β€” so like, if it's not 0, something went sideways and the reason comes with it 😭 check it, don't ignore it, periodt.


🌈 SEE ALSO 🌈

Kernel file ./drivers/clk/zynqmp/clkc.c β€” plus the whole friend group, because nobody does this alone bestie:

like, that's the group chat right there 🧚 iykyk πŸ’…


bestie reminder: this page lives under ./drivers/clk/zynqmp, and the version vibes are from October 2026, titled __zynqmp_clock_get_topology(9). that's the whole sign-off, mwah πŸ’–βœ¨πŸŽ€
πŸ“¦ where this page comes from