dpu_encoder_phys_cmd_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– dpu_encoder_phys_cmd_init(9) πŸ’–

okay so bestie, welcome to the dpu_encoder_phys_cmd_init page from the Kernel API Manual β€” section 9, kernel-space girlie territory. this one is short and sweet and it's giving "one job, does it well." let's get into it 🫢


✨ NAME ✨

dpu_encoder_phys_cmd_init β€” Construct a new command mode physical encoder πŸ’…

like, literally, that's the whole gig. it builds you a brand-new physical encoder that speaks command mode. no cap.


🌸 SYNOPSIS 🌸

struct dpu_encoder_phys * dpu_encoder_phys_cmd_init (struct drm_device
*dev , struct dpu_enc_phys_init_params *p );

that's it, that's the signature, exact characters, don't @ me πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the corresponding device, bestie. it's the struct drm_device * that's gonna handle all the devres management for you. think of it as the responsible friend holding your stuff while you allocate ✨
  • p β€” a pointer to the init params structure (struct dpu_enc_phys_init_params *). all the setup deets live in here. you gotta hand it over, no shortcuts πŸ™ˆ

πŸ‘‘ RETURN πŸ‘‘

it gives you back either an error code (😭) or a newly allocated encoder (πŸ”₯). that's the whole vibe check β€” success or the error code, nothing else.


🌈 SEE ALSO 🌈

  • Kernel file ./drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c β€” go read the source, iykyk πŸ’œ

ok so real talk: this page is tiny but every single word is load-bearing. dev manages devres, p is your params pointer, and the return is an error code or the freshly allocated encoder. nothing more, nothing less. slay. πŸ’…

and that's the page, babe! 🌸 this icon was brought to you by the ./drivers/gpu/drm/msm/disp/dpu1 source tree, dated October 2026, living its best life in the Kernel API Manual. mwah, go write some encoders πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from