__fimc_md_cr...c_sink_links(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

Sooo bestie, welcome to the __fimc_md_create_fimc_sink_links(9) page β€” section 9 of the Kernel API Manual, no less β€” and it does exactly one iconic thing: it creates links to all the FIMC entities. That's it. That's the whole vibe. ✨


🌸 SYNOPSIS 🌸

int __fimc_md_create_fimc_sink_links (struct fimc_md *fmd , struct
media_entity *source , struct v4l2_subdev *sensor , int pad , int
link_mask );

She returns an int, she takes five things, and she is not about to explain herself further. Periodt. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

Okay so here's the cast β€” every single one, no skips, no cap:

  • fmd β€” the fimc media device. The main character of this whole situation, fr fr. πŸ‘‘
  • source β€” the source entity you're creating links to all the fimc entities from. Like, the origin point of the slay. πŸ¦‹
  • sensor β€” the sensor subdev linked to the FIMC[fimc_id] entity. Plot twist: it may be null. πŸ™ˆ Not required, just appreciated.
  • pad β€” the pad index of the source entity. Just a lil index, doing its job. 🌸
  • link_mask β€” a bitmask of the fimc devices for which the link should be enabled. Yes, bitmask. Yes, you're gonna need to think in binary. She's giving bitwise realness. πŸ”₯

🌈 SEE ALSO 🌈

Go read these next, bestie, they're all connected iykyk:

Like the whole pipeline friend group, honestly. 🫢


Heads up, babes: the page title and the version line are both kinda truncated in the source β€” the title shows up as __fimc_md_cr...c_sink_links(9), so don't come for me, that's just how she was handed to us. πŸ’€

And that's the whole page, mwah. Signing off from the Kernel API Manual, dated October 2026, sourced from ./drivers/media/platform/samsu... (yes, cut off mid-word, iconic of her honestly) β€” see you in the next one, __fimc_md_cr...c_sink_links(9) out! β­πŸ§šπŸ’œπŸ’…

πŸ“¦ where this page comes from