STRUCT I915_PXP_COMPONENT_OPS(9)
π 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms