fh_dma_enable(9)
π fh_dma_enable β the manual page, but make it make sense
okay so bestie, welcome to fh_dma_enable(9) from the Kernel API Manual β¨ this is the little hypervisor call that turns DMA on for a device, and honestly? she's short, she's sweet, she's giving "one job and she does it." π
πΈ NAME πΈ
fh_dma_enable β enable DMA for the specified device. that's it. that's the whole vibe. π
β¨ SYNOPSIS β¨
unsigned int fh_dma_enable (unsigned int liodn );
like, literally one argument. we love a low-maintenance icon. π
π¦ ARGUMENTS π¦
liodnβ the LIODN of the I/O device you wanna enable DMA for. yes, that exact device. no, you can't be vague about it. π«Ά
π« DESCRIPTION π«
so you call it, and it returns 0 for success, or an error code. that's the whole plot. no cap. if you get 0 back you're slaying; if you get an error code, that's the universe telling you something's off. ππ₯
π SEE ALSO π
first up, the kernel file this whole family lives in: ./arch/powerpc/include/asm/fsl_hcalls.h π§
and then, the whole friend group β go say hi:
fh_send_nmi(9), fh_partition_get_dtprop(9), fh_partition_restart(9), fh_partition_get_status(9), fh_partition_start(9), fh_partition_stop(9), struct fh_sg_list(9), fh_partition_memcpy(9), fh_dma_disable(9), fh_vmpic_get_msir(9), fh_system_reset(9), fh_err_get_info(9), fh_get_core_state(9), fh_enter_nap(9), fh_exit_nap(9), fh_claim_device(9)
lowkey a note-to-self: fh_dma_disable(9) is right there in that list too, so when you're done enabling, you already know who to call to turn it back off. balance. π
and that's the page, bestie π source/location is ./arch/powerpc/include/asm, dated October 2026, and the page itself is fh_dma_enable(9) β mwah, go enable some DMA responsibly πβ¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms