vsp1_dl_list_add_body(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ vsp1_dl_list_add_body(9) ✨

okay bestie, welcome to the vsp1_dl_list_add_body page from the Kernel API Manual πŸ’– this one's lowkey short but it's giving "small but mighty" and the ownership rules are literally the main character here, so pay attention fr fr 🫢


🌸 NAME 🌸

vsp1_dl_list_add_body β€” add a body to the display list πŸ’…


✨ SYNOPSIS ✨

int vsp1_dl_list_add_body (struct vsp1_dl_list *dl , struct vsp1_dl_body
*dlb );

πŸŽ€ ARGUMENTS πŸŽ€

  • dl β€” the display list πŸ‘‘
  • dlb β€” the body πŸ¦‹

πŸ’œ DESCRIPTION πŸ’œ

So what this does is add a display list body to a display list, periodt. The registers that live inside bodies get processed after the registers in the main display list, and they go in the order the bodies were added β€” first in, first processed, no cap 🧚

⚠️ okay this part is important, don't skip it: adding a body to a display list passes ownership of the body to the list. The caller does retain its reference to the body when adding it to the display list, but it is not allowed to add new entries to the body. Like, at all. πŸ™ˆ

And because of that ownership situation, the reference must be explicitly released by a call to vsp1_dl_body_put when the body isn't needed anymore. Not optional, bestie β€” explicit release only πŸ’€


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/media/platform/renesas/vsp1/vsp1_dl.c and honestly the whole friend group:


that's the whole page, you ate that πŸ’… this lil beauty comes from ./drivers/media/platform/renes... and the date on it is October 2026, version vsp1_dl_list_add_body(9) β€” mwah, go forth and release your references properly πŸŒˆβ­πŸ’–

πŸ“¦ where this page comes from