Dear Mauro We discuss about > At the DVB frontend, the tuner and demodulators should be implemented > on different drivers, even when both are encapsulated on the same silicon. with our HW developers and SW designers.
Our codes for tuner and demodulator driver of user-space driver are encapsulated in order to optimize tuner control sequence. (Our tuner driver often have to set rf tuner registers and demodulator alternately. ) And there are some registers which simultaneously set parameter for tuner and demodulator block. Additionally, we think about current TV tuner IC trend and linux tuner driver. I summarized our study results and proposals as follows. ・In our case the tuner and demodulator are single chip architecture, so the tuner control cannot be distinguished from demodulator functionality. It is therefore difficult to separate tuner code and demodulator code. ・We understand that single chip solutions may become more popular for smartphone and low power tuner device (USB, etc) so mixed driver will be main stream. ・We intend to add the driver incorporating tuner and demodulator code to /media/dvb-frontend/XXXX (XXXX is our tuner name folder) ・We will create our driver to have same API structure as the current tuner and demodulator driver code. (drivers/media/dvb-frontends/m88rs2000.c and tda10071.c also seem to have tuner and demodulator code. We would like to refer to their codes for our creating.) Could you give us your advice and comments? Best Regards & Thanks Takiguchi -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
