qcom_write_data_dma(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so welcome to qcom_write_data_dma(9) from the Kernel API Manual, bestie β€” we are officially in kernel-docs territory now. πŸ’…

qcom_write_data_dma β€” transfer data. That's the name, that's the vibe, and the NAME section is not gonna elaborate further. Periodt. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

she is declared exactly like this, character for character:

int qcom_write_data_dma (struct qcom_nand_controller *nandc , int
reg_off , const u8 *vaddr , int size , unsigned int flags );

πŸ’… ARGUMENTS πŸ’…

  • nandc β€” qpic nand controller. The controller bestie in question. 🫢
  • reg_off β€” offset within the controller's data buffer. Yes, exactly that offset. ✨
  • vaddr β€” virtual address of the buffer we want to read from. Pointer tea. πŸ¦‹
  • size β€” DMA transaction size in bytes. Numbers, but make it DMA. πŸ”₯
  • flags β€” flags to control DMA descriptor preparation. The little switches that steer the prep. πŸŽ€

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so the DESCRIPTION is giving cliffhanger energy, and I need you to see it:

This function will prepares a DMA descriptor to transfer data from

That is literally where it ends β€” from and then nothing. Not me staring at the manpage waiting for the rest of the sentence 😭. It prepares a DMA descriptor to transfer data from … yeah, the original does not finish that thought. We are not inventing the missing part, bestie. No cap. πŸ’€


🌈 SEE ALSO 🌈

Kernel file: ./drivers/mtd/nand/qpic_common.c β€” that's the file tea. πŸ“

And here's the whole related-call squad, every single one:


mwah πŸ’‹ source/version: ./drivers/mtd/nand, date: October 2026. That's the footer tea, bestie β€” qcom_write_data_dma(9) out. πŸŽ€

πŸ“¦ where this page comes from