aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/media/tuners/mt2131.c
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab+samsung@kernel.org>2018-07-05 18:59:35 -0400
committerMauro Carvalho Chehab <mchehab+samsung@kernel.org>2018-08-02 16:14:50 -0400
commita3f90c75b833caeff123499e13e0e31cbecf7d5b (patch)
tree556af7a0bba42d51bf70c0d3e151bd440416f63b /drivers/media/tuners/mt2131.c
parentmedia: dvb_ca_en50221: off by one in dvb_ca_en50221_io_do_ioctl() (diff)
downloadlinux-dev-a3f90c75b833caeff123499e13e0e31cbecf7d5b.tar.xz
linux-dev-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/tuners/mt2131.c')
-rw-r--r--drivers/media/tuners/mt2131.c8
1 files changed, 4 insertions, 4 deletions
diff --git a/drivers/media/tuners/mt2131.c b/drivers/media/tuners/mt2131.c
index 659bf19dc434..086a7b7cf634 100644
--- a/drivers/media/tuners/mt2131.c
+++ b/drivers/media/tuners/mt2131.c
@@ -235,10 +235,10 @@ static void mt2131_release(struct dvb_frontend *fe)
static const struct dvb_tuner_ops mt2131_tuner_ops = {
.info = {
- .name = "Microtune MT2131",
- .frequency_min = 48000000,
- .frequency_max = 860000000,
- .frequency_step = 50000,
+ .name = "Microtune MT2131",
+ .frequency_min_hz = 48 * MHz,
+ .frequency_max_hz = 860 * MHz,
+ .frequency_step_hz = 50 * kHz,
},
.release = mt2131_release,