vpu_mapping_dm_addr(9)

✨ NAME ✨

okay bestie, welcome to vpu_mapping_dm_addr(9) from the Kernel API Manual 💖 This one is literally about mapping DTCM/DMEM to kernel virtual address — that’s the whole name, no cap. 🦋

🌸 SYNOPSIS 🌸

void * vpu_mapping_dm_addr (struct platform_device *pdev , u32
       dtcm_dmem_addr );

💅 ARGUMENTS 💅

• pdev — VPU platform device. Like, the platform device for the VPU. 🫶
• dtcm_dmem_addr — VPU's data memory address. The data memory address belonging to the VPU. ✨

🎀 DESCRIPTION 🎀

This is the mapping moment: mapping the VPU's DTCM (Data Tightly-Coupled Memory) / DMEM (Data Extended Memory) memory address to kernel virtual address. It’s giving “address glow-up” 💅 — same energy, very demure, very mapped.

🔥 RETURN 🔥

It returns ERR_PTR(-EINVAL) if mapping failed; otherwise, the mapped kernel virtual address. That’s the whole return vibe. 🌈

🌈 SEE ALSO 🌈

• Kernel file ./drivers/media/platform/mediatek/vpu/mtk_vpu.h
• VPU(9)
• enum ipi_id(9)
• enum rst_id(9)
• vpu_ipi_register(9)
• vpu_ipi_send(9)
• vpu_get_plat_device(9)
• vpu_wdt_reg_handler(9)
• vpu_get_vdec_hw_capa(9)
• vpu_get_venc_hw_capa(9)
• vpu_load_firmware(9)

mwah 💋 source/version: ./drivers/media/platform/media... · October 2026 · vpu_mapping_dm_addr(9)