is_manual_mode(9)

💅 is_manual_mode(9) — a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual ✨ this one's a lil function called is_manual_mode, and honestly she's giving gatekeeper-but-make-it-helpful 🎀

---

✨ NAME ✨

is_manual_mode — check if TMCC should be used for parameters settings 🌸

---

🌈 SYNOPSIS 🌈

int is_manual_mode (struct dtv_frontend_properties *c );

---

🦋 ARGUMENTS 🦋

• c — a struct dvb_frontend_properties, literally the whole vibe of the frontend properties being passed in 💜

---

🔥 DESCRIPTION 🔥

so, default behaviour, right? By default, the TMCC table should be used for parameter settings on most usecases. That's the main character path, no cap 👑

but sometimes — and hear me out — it is desirable to lock the demod to use the manual parameters. like, that's the whole point of manual mode, and we respect her choices 💅

here's the tea tho 🫖 On manual mode, the current dib8000_tune state machine is very restrict: it requires that both per-layer and per-transponder parameters be properly specified, otherwise the device won't lock. not "might not", not "probably won't" — it won't. periodt 💀

so this function checks if all those conditions are properly satisfied before allowing the device to use the manual frequency lock mode. think of her as the bouncer at the club — nobody gets in with an incomplete set of parameters 🙈✨

bestie fr fr: if you skip the parameter checks, the device just sits there refusing to lock and you'll be staring at it like 😭 — so check first, slay after 🦋

---

👀 SEE ALSO 👀

• Kernel file ./drivers/media/dvb-frontends/dib8000.c — go read her, iykyk 💖

---

okay that's the whole thing, you ate that 🍓 this lil page lives in ./drivers/media/dvb-frontends and her version/date stamp says October 2026 — so she's from the future, iconic behavior honestly ⭐🫶💜