atmel_lcdfb_...video_memory(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– atmel_lcdfb_alloc_video_memory πŸ’–

okay bestie, welcome to the Kernel API Manual β€” yes we're in atmel_lcdfb_...video_memory(9) territory and honestly? it's giving niche-but-iconic. grab your strawberry drink πŸ“ and let's go.


✨ NAME ✨

atmel_lcdfb_alloc_video_memory β€” literally just allocates framebuffer memory πŸŽ€ that's it, that's the whole vibe.


🌸 SYNOPSIS 🌸

int atmel_lcdfb_alloc_video_memory (struct atmel_lcdfb_info *sinfo );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • sinfo β€” the frame buffer you're allocating memory for πŸ’… like, hand it the framebuffer, it handles the rest, no cap.

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea β˜• β€” this function is called only from the atmel_lcdfb_probe. only. exclusively. nobody else pulls up. πŸ™ˆ

and because of that? there's no locking by fb_info->mm_lock around the smem_len setting needed. not because locking isn't cute (it is, in a safety way), but because there's literally only one caller, so the race condition can't even show up to the party. main character energy for the single-caller life ✨


🌈 SEE ALSO 🌈

all four of these are the friend group, check them out too 🫢


fr fr don't skip the SEE ALSO, bestie β€” that's where the lore lives πŸ’€

mwah πŸ’‹ this page came from the kernel source tree at ./drivers/video/fbdev, dated October 2026, and it's filed under atmel_lcdfb_...video_memory(9) β€” slay, go touch some framebuffer memory, ily πŸŒΈπŸ’–

πŸ“¦ where this page comes from