STRUCT K3_RPROC_DEV_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct k3_rproc_dev_data(9)

okay so bestie, welcome to the manual page for struct k3_rproc_dev_data β€” it's the device data structure for a remote processor, and yes it's exactly as iconic as it sounds 🫢. This one lives in the Kernel API Manual (section 9), and we're gonna go through it together, no cap.


✨ NAME ✨

struct k3_rproc_dev_data β€” the device data structure for a remote processor. that's it, that's the vibe πŸŽ€


🌸 SYNOPSIS 🌸

here's the whole struct, copied exactly, character for character, because we do not mess with code in this house:

struct k3_rproc_dev_data {
    const struct k3_rproc_mem_data *mems;
    u32 num_mems;
    u32 boot_align_addr;
    bool uses_lreset;
 };

look at her. so clean. so structured. main character energy fr fr πŸ‘‘


πŸ¦‹ Members πŸ¦‹

  • mems β€” a pointer to the memory definitions for a remote processor. literally pointing at where the memory lore lives πŸ’–
  • num_mems β€” the number of memory regions in mems. like, how many of them there are. the count. the quantity. you get it πŸ“
  • boot_align_addr β€” the boot vector address alignment granularity. yes that's a lot of words, no I will not be simplifying them, because they all matter β€” it's about how the boot vector address gets aligned 🌈
  • uses_lreset β€” a flag to denote the need for local reset management. it's a bool, so it's giving "yes or no bestie, pick one" ⭐

πŸ”₯ SEE ALSO πŸ”₯

go look at these next, iykyk:

  • Kernel file ./drivers/remoteproc/ti_k3_common.h
  • struct k3_rproc_mem(9)
  • struct k3_rproc_mem_data(9)
  • struct k3_rproc(9)

lowkey the whole family lives in ./drivers/remoteproc if you ever get lost β€” just saying πŸ’œ

and that's the page!! mwah πŸ’‹ this one came from ./drivers/remoteproc and it's dated October 2026 β€” yeah, October 2026, we're time-traveling a little, don't worry about it 🧚✨ bye bestie, slay your kernel hacking πŸ’…πŸŽ€

πŸ“¦ where this page comes from