STRUCT ZYNQMP_CLOCK(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct zynqmp_clock β€” Clock ✨

okay so real talk, bestie, this is a page from the Kernel API Manual β€” we're in the deep lore of the kernel here, no cap 🧚


✨ SYNOPSIS ✨

here's the whole vibe of the struct, verbatim, don't @ me:

struct zynqmp_clock {
    char clk_name[MAX_NAME_LEN];
    u32 valid;
    enum clk_type type;
    struct clock_topology node[MAX_NODES];
    u32 num_nodes;
    struct clock_parent parent[MAX_PARENT];
    u32 num_parents;
    u32 clk_id;
 };

🫢 Members 🫢

  • clk_name β€” Clock name. like, the actual name-name, the government name 😭
  • valid β€” Validity flag of clock. is this clock even real? vibe check βœ…
  • type β€” Clock type (Output/External). pick a lane, icon πŸ’…
  • node β€” Clock topology nodes. the whole family tree of wiring, lowkey
  • num_nodes β€” Number of nodes present in topology. yes, we counted, we're thorough πŸŽ€
  • parent β€” Parent of clock. who made this clock, fr fr
  • num_parents β€” Number of parents of clock. some clocks have multiple parents and honestly? main character energy πŸ‘‘
  • clk_id β€” Clock id. the numeric little passport for the clock 🌸

🌈 SEE ALSO 🌈

bestie you gotta go read the whole friend group, they all hang out together:

no cap, those double-underscore ones are the inner-circle versions of the plain-named ones, iykyk πŸ”₯

that's the whole page, diva πŸ’œ it lives in <code>./drivers/clk/zynqmp</code>, and this edition was dated October 2026, sourced straight from <code>./drivers/clk/zynqmp</code> and stamped <code>struct zynqmp_clock(9)</code> at the bottom. slay, drink water, and go read your kernel docs 🫢✨

πŸ“¦ where this page comes from