STRUCT VIDTV_TUNER_HARDWARE_STATE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct vidtv_tuner_hardware_state β€” NAME

okay so bestie, welcome to the Kernel API Manual ✨ (that's the manual name, section 9, no cap). This page is all about struct vidtv_tuner_hardware_state β€” which is literally the vibes-only version of tuner hardware status. It's a simulation, and honestly? it ate. πŸŽ€

πŸ¦‹ SYNOPSIS

struct vidtv_tuner_hardware_state {
    bool asleep;
    u32 lock_status;
    u32 if_frequency;
    u32 tuned_frequency;
    u32 bandwidth;
 };

🌸 Members

  • asleep β€” is the tuner snoozing or what? πŸ’€ this tells you whether _sleep or _suspend was called. she's resting, leave her alone.
  • lock_status β€” did the tuner actually manage to lock on the requested frequency, or is she being flaky? πŸ‘€ this is the receipts.
  • if_frequency β€” the tuner's intermediate frequency. hardcoded β€” for the purposes of simulation, bestie. it's giving "we didn't have real hardware so we made one up." πŸ™ˆ
  • tuned_frequency β€” the actual tuned frequency. yes, the real one. not a drill. πŸ”₯
  • bandwidth β€” the actual bandwidth. same energy. ⭐

🧚 Description

bestie listen β€” this structure is meant to simulate the status of the tuner hardware, as if we had a physical tuner hardware. that's the whole assignment. it's pretend hardware with real field names, and honestly the main character energy is unmatched πŸ‘‘βœ¨

πŸ’œ SEE ALSO

  • Kernel file ./drivers/media/test-drivers/vidtv/vidtv_tuner.c
  • struct vidtv_tuner_dev(9)

and that's the page 🫢 written up all cute from the kernel source at ./drivers/media/test-drivers/v..., dated October 2026 β€” go read the actual tuner code next, iykyk πŸ’…πŸ’–

πŸ“¦ where this page comes from