atmel_lcdfb_...video_memory(9)
π 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 π
- Kernel file
./drivers/video/fbdev/atmel_lcdfb.cβ go read the source, iykyk π atmel_lcdfb_check_var(9)atmel_lcdfb_set_par(9)atmel_lcdfb_setcolreg(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms