summaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq/sti-cpufreq.c
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab+samsung@kernel.org>2018-07-05 18:59:36 -0400
committerMauro Carvalho Chehab <mchehab+samsung@kernel.org>2018-08-02 18:10:48 -0400
commitf1b1eabff0eb3fc46b06668de8174c0f23b271fd (patch)
treeeb4e9ec56be3792965fda7b00760911bd0086efc /drivers/cpufreq/sti-cpufreq.c
parenta3f90c75b833caeff123499e13e0e31cbecf7d5b (diff)
downloadblackbird-obmc-linux-f1b1eabff0eb3fc46b06668de8174c0f23b271fd.tar.gz
blackbird-obmc-linux-f1b1eabff0eb3fc46b06668de8174c0f23b271fd.zip
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>
Diffstat (limited to 'drivers/cpufreq/sti-cpufreq.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud