rpi_firmware_property_list(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– rpi_firmware_property_list(9) β€” Kernel API Manual πŸ’–

okay bestie, so this is the rpi_firmware_property_list page from the Kernel API Manual and honestly? it's kinda the main character of Raspberry Pi firmware calls. let's get into it ✨


🌸 NAME 🌸

rpi_firmware_property_list β€” submit a firmware property list, periodt πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

int rpi_firmware_property_list (struct rpi_firmware *fw , void *data ,
       size_t tag_size );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • fw β€” pointer to the firmware structure, the one you got from rpi_firmware_get. it's giving "where you got your fw from" energy 🫢
  • data β€” the buffer holding the tags. this is the actual content, the moment, the vibe check πŸ’–
  • tag_size β€” size of the tags buffer. gotta tell it how big the tea is πŸ“

✨ DESCRIPTION ✨

so what it does: it submits a set of concatenated tags to the VPU firmware through the mailbox property interface. like, all your tags bundled up and sent off together β€” very "let's go girls" πŸ’…

plot twist that saves you work: the buffer header and the ending tag are added by this function itself, and don't need to be supplied. so you literally just bring the actual tags for your operation and it handles the rest. obsessed 😭

wanna know what the per-tag structure looks like? see struct rpi_firmware_property_tag_header πŸ”₯

πŸ’œ SEE ALSO πŸ’œ

all the sister pages, iykyk 🌈


and that's the whole page, no cap πŸ’€πŸ’– this cutie lives in ./drivers/firmware and the footer said October 2026 β€” so mark your calendars bestie, the kernel API manual is booked and busy πŸ‘‘βœ¨

πŸ“¦ where this page comes from