drm_print_regset32(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

hey bestie πŸ‘‹ welcome to the drm_print_regset32(9) page from the Kernel API Manual β€” it’s short, it’s useful, and it’s lowkey carrying driver debug on its back πŸ’…βœ¨

🌸 NAME 🌸

drm_print_regset32 β€” print the contents of registers to a &drm_printer stream. πŸŽ€

✨ SYNOPSIS ✨

void drm_print_regset32 (struct drm_printer *p , struct debugfs_regset32 *regset );

That’s the whole vibe: void, two pointers, no drama. 🫢

πŸŽ€ ARGUMENTS πŸŽ€

  • p β€” the drm_printer πŸ’–
  • regset β€” the list of registers to print. πŸ¦‹

πŸ¦‹ DESCRIPTION πŸ¦‹

Ok so picture this: you’re doing driver debug, and it is often useful to be able to either capture the contents of registers in the steady state using debugfs, or at specific points during operation. This lets the driver have a single list of registers for both. Obsessed? Same. πŸ”₯

πŸ”₯ SEE ALSO πŸ”₯

Kernel file: ./drivers/gpu/drm/drm_print.c β€” and the besties in crime are drm_puts(9), drm_printf(9), drm_print_bits(9), and drm_print_hex_dump(9). 🫢🌈


Cute sign-off from the ./drivers/gpu/drm source/version corner, October 2026 edition β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from