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:
@@ -1212,9 +1212,9 @@ static const struct dvb_frontend_ops nxt200x_ops = {
|
||||
.delsys = { SYS_ATSC, SYS_DVBC_ANNEX_B },
|
||||
.info = {
|
||||
.name = "Nextwave NXT200X VSB/QAM frontend",
|
||||
.frequency_min = 54000000,
|
||||
.frequency_max = 860000000,
|
||||
.frequency_stepsize = 166666, /* stepsize is just a guess */
|
||||
.frequency_min_hz = 54 * MHz,
|
||||
.frequency_max_hz = 860 * MHz,
|
||||
.frequency_stepsize_hz = 166666, /* stepsize is just a guess */
|
||||
.caps = 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_8VSB | FE_CAN_QAM_64 | FE_CAN_QAM_256
|
||||
|
Reference in New Issue
Block a user