It could be nice to validate transmission parameters, coming from the userspace, against standards before those are passed to the individual chipset driver. As a starting point towards that I implemented checks for few common standards. Those checks could be better as I added almost none checks for comparing allowed parameter combinations. I found it quite time consuming to search all allowed parameters and combinations... Those checks are now exported from the dvb-frontend, making for example demodulator driver possible to call. Maybe someday those could be used by frontend itself to validate data before pass call for the driver. I also noticed our documentation lacks quite totally possible values, only possible parameters were listed. How do we expect application makers could know those? Antti Palosaari (4): dvb_frontend: add routine for DVB-T parameter validation dvb_frontend: add routine for DVB-T2 parameter validation dvb_frontend: add routine for DVB-C annex A parameter validation dvb_frontend: add routine for DTMB parameter validation drivers/media/dvb-core/dvb_frontend.c | 405 ++++++++++++++++++++++++++++++++++ drivers/media/dvb-core/dvb_frontend.h | 5 + 2 files changed, 410 insertions(+) -- 1.7.11.2 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
