zynqmp_pm_clock_getstate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the zynqmp_pm_clock_getstate(9) page from the Kernel API Manual β€” it's giving clock-state main character energy and I'm obsessed πŸ’…βœ¨

πŸŽ€ NAME πŸŽ€

zynqmp_pm_clock_getstate β€” Get the clock state for given id. That's literally it: you're getting the clock state for the given ID, and the way it's that direct? iconic πŸ’–

✨ SYNOPSIS ✨

int zynqmp_pm_clock_getstate (u32 clock_id , u32 *state );

πŸ’– ARGUMENTS πŸ’–

  • clock_id β€” ID of the clock to be queried. It's the clock you're asking about, bestie πŸ•΅οΈβ€β™€οΈ
  • state β€” 1/0 (Enabled/Disabled). That's the lil enabled-or-disabled tea πŸ“

πŸ¦‹ DESCRIPTION πŸ¦‹

This function is used by master to get the state of clock including peripherals and PLL clocks. So yeah, your master calls this to check a clock's state, and it covers peripherals and PLL clocks too β€” highkey thorough, no cap ✨

🌸 RETURN 🌸

It returns a status: either success or error+reason. That's the whole status tea, no hidden lore πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

okay here's the whole friend group of related refs β€” all of them, no skips, periodt πŸ‘‘


okay bestie, that's the whole page β€” mwah πŸ’‹! footer source/version + date vibes: ./drivers/firmware/xilinx, October 2026 🫢

πŸ“¦ where this page comes from