XE_RTP_RULE_PLATFORM_STEP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’…βœ¨ XE_RTP_RULE_PLATFORM_STEP(9) βœ¨πŸ’…

okay bestie, welcome to the XE_RTP_RULE_PLATFORM_STEP(9) page from the Kernel API Manual. we're talking about a rule matching platform-level stepping, and yes, you're gonna understand it. no cap. 🫢


πŸŽ€ NAME πŸŽ€

XE_RTP_RULE_PLATFORM_STEP β€” Create rule matching platform-level stepping. periodt. πŸ‘‘

🌸 SYNOPSIS 🌸

XE_RTP_RULE_PLATFORM_STEP (start_ , end_ );

πŸ’– ARGUMENTS πŸ’–

  • start_ β€” First stepping matching the rule. this is your left edge, bestie. 🫢
  • end_ β€” First stepping that does not match the rule. this is the right edge that gets left out. πŸ™ˆ

✨ DESCRIPTION ✨

Okay so the range that matches this rule is [ start_, end_ ) β€” that means inclusive on the left, exclusive on the right. so start_ is in the club, and end_ is literally not on the list. πŸ’…

🚨 before you use this rule: you need to make sure that proper support for reading platform-level stepping information is present for the target platform. no support = no vibes, okay? 😭

Refer to XE_RTP_RULES for expected usage. that's the bestie to check with for how this is supposed to be used. πŸ¦‹

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/gpu/drm/xe/xe_rtp.h β€” and here's the whole squad, no cap:


mwah πŸ’‹ β€” this page is XE_RTP_RULE_PLATFORM_STEP(9), from source ./drivers/gpu/drm/xe, dated October 2026. byeee, go be iconic with your rules. πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from