media: dvb: represent min/max/step/tolerance freqs in Hz
Right now, satellite frontend drivers specify frequencies in kHz, while terrestrial/cable ones specify in Hz. That's confusing for developers. However, the main problem is that universal frontends capable of handling both satellite and non-satelite delivery systems are appearing. We end by needing to hack the drivers in order to support such hybrid frontends. So, convert everything to specify frontend frequencies in Hz. Tested-by: Katsuhiro Suzuki <suzuki.katsuhiro@socionext.com> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
This commit is contained in:
@@ -510,15 +510,14 @@ static const struct dvb_frontend_ops s921_ops = {
|
||||
/* Use dib8000 values per default */
|
||||
.info = {
|
||||
.name = "Sharp S921",
|
||||
.frequency_min = 470000000,
|
||||
.frequency_min_hz = 470 * MHz,
|
||||
/*
|
||||
* Max should be 770MHz instead, according with Sharp docs,
|
||||
* but Leadership doc says it works up to 806 MHz. This is
|
||||
* required to get channel 69, used in Brazil
|
||||
*/
|
||||
.frequency_max = 806000000,
|
||||
.frequency_tolerance = 0,
|
||||
.caps = FE_CAN_INVERSION_AUTO |
|
||||
.frequency_max_hz = 806 * MHz,
|
||||
.caps = FE_CAN_INVERSION_AUTO |
|
||||
FE_CAN_FEC_1_2 | FE_CAN_FEC_2_3 | FE_CAN_FEC_3_4 |
|
||||
FE_CAN_FEC_5_6 | FE_CAN_FEC_7_8 | FE_CAN_FEC_AUTO |
|
||||
FE_CAN_QPSK | FE_CAN_QAM_16 | FE_CAN_QAM_64 |
|
||||
|
Reference in New Issue
Block a user