xvcu_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… xvcu_read(9) πŸ’…

okay bestie, welcome to the Kernel API Manual ✨ β€” today's main character is xvcu_read, and honestly? she's a short one but she serves. πŸŽ€


🌸 NAME 🌸

xvcu_read β€” read a little something from the VCU register space πŸ‘‘ no cap, that's literally her whole job.


✨ SYNOPSIS ✨

u32 xvcu_read (void __iomem *iomem , u32 offset );

yeah that's it, that's the whole vibe check πŸ’… two args in, one u32 out. iconic behavior.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • iomem β€” the base address of the VCU register space 🏠 like, the address of the whole neighborhood, yk? void __iomem * and everything, so behave.
  • offset β€” the VCU register offset from that base 🎯 i.e. which house on the street you're knocking on. u32, obviously.

πŸ’– RETURN πŸ’–

returns the 32-bit value from the VCU register you specified πŸ”₯ β€” yes, a u32, exactly what you asked for, no surprises, we love a predictable queen 🫢


🌈 SEE ALSO 🌈

  • the kernel file ./drivers/clk/xilinx/xlnx_vcu.c πŸ“ (yes, that's the one, go read it, iykyk)
  • struct xvcu_device(9) 🧚
  • struct xvcu_pll_cfg(9) ⭐
  • xvcu_write(9) ✍️ (her counterpart, the yin to her yang)
  • xvcu_probe(9) πŸ”
  • xvcu_remove(9) πŸ’€

ok that's the whole page bestie, she's smol but she ate πŸ’…βœ¨

mwah πŸ’œ this lil page lives in ./drivers/clk/xilinx and it's dated October 2026 β€” future icon behavior, periodt. πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from