pixel_read_line_t(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ pixel_read_line_t(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for pixel_read_line_t β€” this is the one that reads a whole pixel line out of the source frame, converts it into struct pixel_argb_u16, and then writes it all into @out_pixel. it's giving "glow up pipeline" energy fr fr πŸ’…


🌸 NAME 🌸

pixel_read_line_t β€” these functions are used to read a pixel line in the source frame, convert it to struct pixel_argb_u16 and write it to @out_pixel. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void pixel_read_line_t (const struct vkms_plane_state *plane , int
x_start , int y_start , enum pixel_read_direction direction , int count
, struct pixel_argb_u16 out_pixel[] );

πŸ’– ARGUMENTS πŸ’–

  • plane β€” the plane you're using as the source for the pixel value. your main character, basically πŸ‘‘
  • x_start β€” the X (width) coordinate of the first pixel to copy. ⚠️ the caller must ensure that x_start is non-negative and smaller than plane->frame_info->fb->width. no cap, if you don't do the vibe check here it's on you.
  • y_start β€” the Y (height) coordinate of the first pixel to copy. ⚠️ again, the caller must ensure that y_start is non-negative and smaller than plane->frame_info->fb->height. same energy, don't skip it 🫢
  • direction β€” the direction to use for the copy, starting at x_start/y_start. where we're headed, bestie 🧭
  • count β€” number of pixels to copy. like, exactly how many pixels you're taking home πŸ“
  • out_pixel β€” pointer where to write the pixel values. they will be written from out_pixel[0] (included) to out_pixel[count] (excluded). ⚠️ the caller must ensure that out_pixel has a length of at least count. so yeah, size your array right or it's giving disaster πŸ’€
lowkey the important part: those caller-side guarantees in x_start, y_start and out_pixel are your responsibility, not the function's. it literally says "the caller must ensure" three separate times. that's not a suggestion, that's the whole assignment 😭

πŸ”₯ SEE ALSO πŸ”₯


and that's the whole page, bestie ✨ it lives at ./drivers/gpu/drm/vkms, dated October 2026, and it's filed under pixel_read_line_t(9). go read your pixels responsibly πŸ’œπŸŒˆπŸ¦‹

πŸ“¦ where this page comes from