tuner_probe(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– tuner_probe(9) β€” the kernel API manual, but make it make sense πŸ’–

okay so bestie, welcome to the tuner_probe(9) page from the Kernel API Manual ✨ this one's all about sniffing out tuners on an I2C bus, and honestly? it's giving detective energy πŸ”πŸ’…


🌸 NAME 🌸

tuner_probe β€” literally probes the existing tuners on an I2C bus 🫢


✨ SYNOPSIS ✨

int tuner_probe (struct i2c_client *client );

πŸŽ€ ARGUMENTS πŸŽ€

  • client β€” the i2c_client descriptor, aka the lil ID card for the device we're checking out πŸͺͺ

πŸ¦‹ DESCRIPTION πŸ¦‹

so this routine goes around probing for tuners at the expected I2C addresses πŸ‘‘ In most cases, if a device answers to a given I2C address, it just assumes that the device is a tuner. simple, iconic, no notes ✨

but on a few cases, you need an extra bit of logic to double check if the device is really a tuner, or to identify the tuner type β€” like on tea5767/5761 devices 🍡 that's the extra little vibe check for the devices that wanna be mysterious πŸ™ˆ

heads up bestie πŸ’€ During client attach, set_type is called by the adapter's attach_inform callback. set_type must then be completed by tuner_probe. no skipping steps, periodt πŸ”₯

⭐ SEE ALSO ⭐


and that's the whole page, bestie!! 🌈 this lil gem lives in ./drivers/media/v4l2-core, dated October 2026, and it's part of the Kernel API Manual β€” go off, tuner-core.c, you ate πŸ’…πŸ’–βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from