>>> For the past few months, I've been working on refactoring the analog tuner.ko module, such that all hardware-specific code can be separated into dvb_frontend style tuner modules.
>>> This allows for a single module to be used by both the v4l2 tuner interface via the tuner.ko i2c_client driver, and directly by the dvb subsystem's tuning system.
>>> This refactoring process has zero impact to the way that v4l and dvb functions.
>>> I have completed phase one of the refactoring process, and now it is ready for testing and review.
>>> This changeset removes the i2c_client interface between tuner.ko and the tuner sub-drivers.
>>> The i2c_client interface to tuner.ko, itself, remains the same as it has been -- this is only an internal change that affects the interaction between tuner.ko and the hardware-specific code.
>>> Some helper functions and macros were added in this changeset, in order to ease the conversion process, without causing headaches or breakage. (see tuner-i2c.c)  We can remove these extra structs and helper functions after the refactoring process is complete.
>>> This changeset contains the more interesting work, where tuner-core is altered to support attachment of dvb_frontend style tuner modules.  An additional method "set_analog_params" was added to struct dvb_tuner_ops, so as to avoid altering the DVB subsystem userspace API headers.  This change does not create any dependency of the DVB subsystem on V4L, nor does it create any dependency of the V4L subsystem on DVB.
>> header (below) where the operations are really meant for.
>> the end it ends up with lot of stuff which aren't directly related.
> (post-conversion) these source files no longer include "tuner-driver.h"
> internal api, which has been replaced by the dvb_frontend internal api.
belong to the same "device class"
Having it in one place, makes it easier to read the code as well.
> also without creating any dependencies of the V4L subsystem onto DVB.
> module that can receive tuning commands for both analog and digital.
what i stated earlier as well.
Not necessarily. See attached patch.
the same goes for other discussions that came out of it as well.
> hardware that will have to be able to tune both analog and digital.
one would have cared -- but this affects the entire subsystem.
same, which is used elsewhere, ie not used within DVB.
> a patch on top of my tree that will satisfy your requirements.
> Otherwise, I hope that you can get past this small issue.
that you see there ?
The patch attached depicts the same.