fimc_active_queue_pop(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fimc_active_queue_pop(9) β€” Kernel API Manual ✨

okay so bestie, you're in the Kernel API Manual and this one is literally called fimc_active_queue_pop β€” say that five times fast, i dare you 🫢 it's not that deep, it's a tiny little helper that yoinks a buffer off the capture active buffers queue. periodt.


🌸 NAME 🌸

fimc_active_queue_pop β€” pop buffer from the capture active buffers queue πŸ’–


✨ SYNOPSIS ✨

struct fimc_vid_buffer * fimc_active_queue_pop (struct fimc_vid_cap
*vid_cap );

like, it returns a struct fimc_vid_buffer * and takes exactly one thing. iconic, no notes πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • vid_cap β€” camera capture device information πŸ“· β€” this is the whole vibe, the capture device you're pulling from.

πŸ¦‹ DESCRIPTION πŸ¦‹

The caller must assure the active_buf_q list is not empty.

⚠️ okay so this is the important part and i need you to listen: you (the caller) have to make sure active_buf_q isn't empty before you call this. nobody's checking for you. no cap. if you roll up on an empty list that's a you problem, not a this-function problem 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/media/platform/samsung/exynos4-is/fimc-core.h β€” go read it, it's giving main character energy πŸ“–

  • struct fimc_dma_offset(9)
  • struct fimc_effect(9)
  • struct fimc_scaler(9)
  • struct fimc_addr(9)
  • struct fimc_vid_buffer(9)
  • struct fimc_frame(9)
  • struct fimc_m2m_device(9)
  • struct fimc_vid_cap(9)
  • struct fimc_pix_limit(9)
  • struct fimc_variant(9)
  • struct fimc_drvdata(9)
  • struct fimc_dev(9)
  • struct fimc_ctrls(9)
  • struct fimc_ctx(9)
  • fimc_active_queue_add(9)
  • fimc_pending_queue_add(9)
  • fimc_pending_queue_pop(9)

like the whole fimc friend group showed up to the function, we love a supportive cast πŸ’œ


and that's the page, bestie πŸŽ€ sourced from ./drivers/media/platform/samsu..., dated October 2026 β€” timestamped and slayed, mwah πŸ’…βœ¨

πŸ“¦ where this page comes from