rproc_find_carveout_by_name(9)

🌸 NAME 🌸

okay so this page is rproc_find_carveout_by_name(9) from the Kernel API Manual, and it's literally here to lookup the carveout region by a name 🎀. it's giving "name tag for your fave memory region" energy, no cap.

✨ SYNOPSIS ✨

        struct rproc_mem_entry * rproc_find_carveout_by_name (struct rproc
       *rproc , const char *name , ... );

🎀 ARGUMENTS 🎀

• rproc — handle of a remote processor. like, the main character handle you're working with 👑.
• name — carveout name to find (format string). yes bestie, a format string.
• ... — optional parameters matching name string. these are the optional little besties that match the name string 🫶.

💅 DESCRIPTION 💅

okay so picture this: a platform driver has the capability to register some pre-allacoted carveout (physically contiguous memory regions) before rproc firmware loading and associated resource table analysis. yes, "pre-allacoted" is literally the spelling on the page, and we respect the icon's choices 💀. these regions may be dedicated memory regions internal to the coprocessor or specified DDR region with specific attributes — either way, they're specific and they're living their truth 🌈.

this function is a helper function with which we can go over the allocated carveouts and return associated region characteristics like coprocessor address, length or processor virtual address. so it's lowkey the little tour guide for your allocated carveouts — it walks you through and points at the associated region characteristics 🧚.

🫶 RETURN 🫶

a valid pointer on carveout entry on success or NULL on failure. that's it, that's the vibe check ✅.

🔥 SEE ALSO 🔥

• Kernel file ./drivers/remoteproc/remoteproc_core.c
• rproc_da_to_va(9)
• rproc_check_carveout_da(9)
• rproc_handle_vdev(9)
• rproc_handle_trace(9)
• rproc_handle_devmem(9)
• rproc_alloc_carveout(9)
• rproc_release_carveout(9)
• rproc_handle_carveout(9)
• rproc_add_carveout(9)
• rproc_mem_entry_init(9)
• rproc_of_resm_mem_entry_init(9)
• rproc_of_parse_firmware(9)
• rproc_alloc_registered_carveouts(9)
• rproc_resource_cleanup(9)
• rproc_trigger_recovery(9)
• rproc_crash_handler_work(9)
• rproc_boot(9)
• rproc_shutdown(9)
• rproc_detach(9)
• rproc_get_by_phandle(9)
• rproc_set_firmware(9)
• rproc_add(9)
• devm_rproc_add(9)
• rproc_type_release(9)
• rproc_alloc(9)
• rproc_free(9)
• rproc_put(9)
• rproc_del(9)
• devm_rproc_alloc(9)
• rproc_add_subdev(9)
• rproc_remove_subdev(9)
• rproc_get_by_child(9)
• rproc_report_crash(9)

okay bye bestie — source/version is ./drivers/remoteproc, date is October 2026, and this whole thing is rproc_find_carveout_by_name(9). go find your carveout and slay 💋✨