STRUCT I915_PXP_COMPONENT_OPS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct i915_pxp_component_ops β€” a Kernel API Manual moment πŸ’–

okay bestie, so this is from the Kernel API Manual, and it's genuinely one of those little structs that just does its job and looks cute doing it. no cap. ✨


🌸 NAME 🌸

struct i915_pxp_component_ops β€” literally just the ops for PXP services. that's it, that's the whole vibe. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the whole shape of it, iykyk:

struct i915_pxp_component_ops {
    struct module *owner;
    int (*send)(struct device *dev, const void *message, size_t size,
unsigned long timeout_ms);
    int (*recv)(struct device *dev, void *buffer, size_t size, unsigned
long timeout_ms);
    ssize_t (*gsc_command)(struct device *dev, u8 client_id, u32
fence_id, struct scatterlist *sg_in, size_t total_in_len, struct
scatterlist *sg_out);
 };

she's got a module pointer and three function pointers and honestly? main character energy. πŸ‘‘


πŸ’… Members πŸ’…

  • owner β€” the module providing the ops. like, who's the parent here, who's paying the rent. 🫢
  • send β€” send a PXP message. simple, iconic, does what it says on the tin. πŸ“¨
  • recv β€” receive a PXP message. the other half of the conversation, slay. πŸ’Œ
  • gsc_command β€” send a GSC command. yes bestie, GSC and PXP in the same struct, we contain multitudes. πŸ”₯

⭐ SEE ALSO ⭐

  • the kernel file ./include/drm/intel/i915_pxp_tee_interface.h β€” go read it, it's giving source of truth 🧚
  • struct i915_pxp_component(9) β€” the related one, go say hi 🌈

fr fr though, if you're poking at these ops you're already deep in the i915 DRM situation. respect. πŸ’œ

and that's the whole page, bestie β€” written from ./include/drm/intel, dated October 2026, and the title you'd see up top is struct i915...omponent_ops(9) because the column is apparently too narrow for the full name πŸ˜­πŸ¦‹ hope that helped! πŸ“

πŸ“¦ where this page comes from