bam_apply_new_config(9)

📦 version 7.3.1, in nixpkgs unstable

💅 bam_apply_new_config(9) — Kernel API Manual, but make it make sense 🎀

okay so bestie, this is a page from the Kernel API Manual and it's literally the whole manual entry for bam_apply_new_config(9). yes, that's the function name. no, there is not a description. i know. i'm as shook as you are 😭

✨ NAME ✨

bam_apply_new_config —

and that's it. that's the whole description. nothing. the manpage said "no thoughts, head empty" and honestly? iconic of it. no cap, there's no text here to copy, so don't come for me 🫶

🌸 SYNOPSIS 🌸

the whole signature, exactly as written, no edits, queen:

void bam_apply_new_config (struct bam_chan *bchan , enum
dma_transfer_direction dir );

so it returns void — meaning it gives you nothing back, which is very demure, very mindful of it 💅 — and it takes two things. scroll down for the tea on those 👇

🦋 ARGUMENTS 🦋

two arguments, both main character energy:

  • bchan — the bam dma channel 💖 that's the channel you're working with, bestie. it's a struct bam_chan *.
  • dir — the DMA direction ✨ it's an enum dma_transfer_direction, so it's that whole "which way is the data going" situation.

and that's the full cast. no extras, no surprise cameos 🙈

👑 SEE ALSO 👑

grab a snack, this list is long and we're getting through every single one of them, periodt 🔥

first up, the source: the kernel file lives at ./drivers/dma/qcom/bam_dma.c 🍓 — that's where the actual code is, iykyk.

then the whole friend group, in order, no skipping:

nineteen of them. all accounted for. go read them if you're nosy, i support it 💜

heads up: this page was pulled from ./drivers/dma/qcom 🌈 and it's dated October 2026. so when you're citing it, you know exactly where it came from and when, no guessing fr fr.

and that's the page bestie 💖 bam_apply_new_config(9), from the Kernel API Manual, sourced at ./drivers/dma/qcom, dated October 2026 — slay, go apply some new config, mwah 🎀🦋✨

📦 where this page comes from