Re: [PATCH 2/5] mb86a20s: convert it to I2C binding model

[Akihiro TSUKADA <tskd08@gmail.com>]

moikka,

On 2015年01月02日 06:30, Antti Palosaari wrote:
> I am on holiday trip now. But generally speaking I would like to separate all drivers from the interfaces. That means for example I2C tuner driver is just a I2C driver and nothing more - no relations to DVB nor V4L API. That is something I said many times earlier too, but for my taste drivers should be agnostics to APIs.

I can't yet fully understand what API agnostic driver means,
but if it is like the implementation of the current i2c tuner/demod drivers,
each adapter drivers must (re-)implement common codes like module loading/ref-counting
and demod/tuner drivers must implement dvb-core related initializations on their own.
In addition, they may take different ways in how the data like "fe", config data and
other device specific output parameters are passed around
between adapters and demod/tuners.

I thought it would be better to intergrate those common codes into dvb_core
to ease maintainance and let each driver concentrate on driver-specific things.

And don't the current i2c tuner drivers already depend on dvb_core practically
by implementing dvb_tuner_ops functions and
filling in their pointers into fe->ops.tuner_ops?

regards,
akihiro