STRUCT DPU_HW_FMT_LAYOUT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct dpu_hw_fmt_layout(9) β€” like, the whole kernel API manual but make it make sense

okay bestie, so we're in the struct dpu_hw_fmt_layout(9) page, and it is literally a Kernel API Manual moment. the NAME says it all: this struct is format information of the source pixel data ✨ like, it's the glow-up blueprint for how your pixels are laid out. no cap.


🌸 SYNOPSIS 🌸

here's the whole vibe, character for character, do not touch:

struct dpu_hw_fmt_layout {
    uint32_t num_planes;
    uint32_t width;
    uint32_t height;
    uint32_t total_size;
    uint32_t plane_addr[DPU_MAX_PLANES];
    uint32_t plane_size[DPU_MAX_PLANES];
    uint32_t plane_pitch[DPU_MAX_PLANES];
 };

like… the arrays are all DPU_MAX_PLANES sized, that's the main character detail πŸŽ€


πŸ¦‹ Members πŸ¦‹

okay so every single field, one by one, because we do not skip:

  • num_planes β€” number of planes (including meta data planes). yes, meta data planes count too, they're part of the group chat πŸ’…
  • width β€” image width. the horizontal situation.
  • height β€” image height. the vertical situation.
  • total_size β€” total size in bytes. all of it. the whole thing πŸ”₯
  • plane_addr β€” address of each plane. where each plane actually lives.
  • plane_size β€” length of each plane. how long each one is.
  • plane_pitch β€” pitch of each plane. the pitch, bestie, per plane.

that's it, that's the roster. every field accounted for, no ghosts πŸ‘‘


🌈 SEE ALSO 🌈

go read these next, iykyk:

  • Kernel file ./drivers/gpu/drm/msm/disp/dpu1/dpu_hw_mdss.h enum
  • dpu_3d_blend_mode(9)
  • struct dpu_mdss_color(9)
  • struct dpu_hw_tear_check(9)
  • struct dpu_hw_pp_vsync_info(9)

🫢 friendly reminder: the docs live under ./drivers/gpu/drm/msm/disp/dpu1, so if you're lost, that's the neighborhood, bestie.

and that's the page fr fr πŸ’– this lil sign-off comes to you from the source at ./drivers/gpu/drm/msm/disp/dpu1, dated October 2026, tagged struct dpu_hw_fmt_layout(9) β€” slay, go read some kernel headers, ily πŸŽ€βœ¨

πŸ“¦ where this page comes from