XE_RTP_ACTION_CLR(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… XE_RTP_ACTION_CLR(9) πŸ’…

okay so this is a page from the Kernel API Manual bestie, and it's about XE_RTP_ACTION_CLR β€” the macro that clears bits from @val_ in a register. no cap, it's simpler than it sounds, let's go 🫢


✨ NAME ✨

XE_RTP_ACTION_CLR β€” Clear bits from @val_ in the register.


πŸ¦‹ SYNOPSIS πŸ¦‹

XE_RTP_ACTION_CLR (reg_ , val_ , ... );

like literally that's it, three-ish things and you're done πŸ’–


πŸŽ€ ARGUMENTS πŸŽ€

  • reg_ β€” the Register. the actual thing you're poking at, iconic πŸ‘‘
  • val_ β€” the Bits to clear in the register. these are the ones getting the ✨un-alive✨ treatment
  • ... β€” Additional fields to override in the struct xe_rtp_action entry. so extra stuff you wanna swap in, go off 🧚

🌸 DESCRIPTION 🌸

okok so here's the tea πŸ“ β€” for masked registers this translates to a single write. one and done, slay. but for other registers it's a RMW (read-modify-write, iykyk). the way that difference matters fr fr.

the correspondent bspec notation is, like, this (example for bits 2 and 5, but could be any):

REGNAME[2] = 0
REGNAME[5] = 0

so you're zeroing out those bits, one line each, cute and tidy πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

kernel file ./drivers/gpu/drm/xe/xe_rtp.h plus the whole friend group of related pages, no gatekeeping here bestie:


πŸ’€ reminder that this is kernel API territory β€” respect the RMW, don't be out here writing registers all willy-nilly, ok? πŸ™ˆ

and that's the whole vibe check! this one lives in ./drivers/gpu/drm/xe, dated October 2026 β€” go off, you understood the assignment πŸ†βœ¨πŸ’œ

πŸ“¦ where this page comes from