diff options
author | 2018-07-05 18:59:35 -0400 | |
---|---|---|
committer | 2018-08-02 16:14:50 -0400 | |
commit | a3f90c75b833caeff123499e13e0e31cbecf7d5b (patch) | |
tree | 556af7a0bba42d51bf70c0d3e151bd440416f63b /drivers/media/dvb-frontends/itd1000.c | |
parent | media: dvb_ca_en50221: off by one in dvb_ca_en50221_io_do_ioctl() (diff) | |
download | linux-a3f90c75b833caeff123499e13e0e31cbecf7d5b.tar.gz linux-a3f90c75b833caeff123499e13e0e31cbecf7d5b.tar.bz2 linux-a3f90c75b833caeff123499e13e0e31cbecf7d5b.zip |
media: dvb: convert tuner_info frequencies to Hz
Right now, satellite tuner drivers specify frequencies in kHz,
while terrestrial/cable ones specify in Hz. That's confusing
for developers.
However, the main problem is that universal tuners 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 tuners.
So, convert everything to specify tuner frequencies in Hz.
Plese notice that a similar patch is also needed for frontends.
Tested-by: Katsuhiro Suzuki <suzuki.katsuhiro@socionext.com>
Acked-by: Michael Büsch <m@bues.ch>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Diffstat (limited to 'drivers/media/dvb-frontends/itd1000.c')
-rw-r--r-- | drivers/media/dvb-frontends/itd1000.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/drivers/media/dvb-frontends/itd1000.c b/drivers/media/dvb-frontends/itd1000.c index 04f7f6854f73..c3a6e81ae87f 100644 --- a/drivers/media/dvb-frontends/itd1000.c +++ b/drivers/media/dvb-frontends/itd1000.c @@ -353,10 +353,10 @@ static void itd1000_release(struct dvb_frontend *fe) static const struct dvb_tuner_ops itd1000_tuner_ops = { .info = { - .name = "Integrant ITD1000", - .frequency_min = 950000, - .frequency_max = 2150000, - .frequency_step = 125, /* kHz for QPSK frontends */ + .name = "Integrant ITD1000", + .frequency_min_hz = 950 * MHz, + .frequency_max_hz = 2150 * MHz, + .frequency_step_hz = 125 * kHz, }, .release = itd1000_release, |