aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/media/common (follow)
AgeCommit message (Collapse)AuthorFilesLines
2012-01-04[media] mt2063: Fix commentsMauro Carvalho Chehab1-589/+370
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Fix analog/digital set params logicMauro Carvalho Chehab2-201/+190
The driver were using a hacky way of setting analog and digital frequencies. Remove the hack and properly add the tuner logic for each supported type of standard. I was tempted to add more standards there, like SECAM and to fix radio (as stepping seems broken), but I opted to keep it as-is, as tests would be needed to add additional standards. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: make checkpatch.pl happyMauro Carvalho Chehab1-81/+48
Fix everything but 80 columns and two msleep warnings Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Cleanup some function prototypesMauro Carvalho Chehab1-28/+16
No functional changes here. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Reorder the code to avoid function prototypesMauro Carvalho Chehab1-181/+150
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Remove setParm/getParm abstraction layerMauro Carvalho Chehab2-960/+172
This layer just increases the code size for no good reason, and makes harder to debug. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Rework on the publicly-exported functionsMauro Carvalho Chehab2-32/+14
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Simplify mt2063_setTune logicMauro Carvalho Chehab1-34/+3
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: simplify lockstatus logicMauro Carvalho Chehab1-94/+43
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Remove several unused parametersMauro Carvalho Chehab1-362/+2
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Use linux default max functionMauro Carvalho Chehab1-31/+3
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Don't violate the DVB APIMauro Carvalho Chehab1-42/+9
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Simplify device init logicMauro Carvalho Chehab1-333/+242
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Simplify some functionsMauro Carvalho Chehab1-138/+12
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Rewrite read/write logic at the driverMauro Carvalho Chehab1-189/+73
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Remove the code for more than one adjacent mt2063 tunersMauro Carvalho Chehab1-327/+1
Such code is disabled via ifdef's. Also, they're ugly and rely on some static structures. Just remove. If ever needed, the git log can be used to recover it. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Use state for the state structureMauro Carvalho Chehab1-415/+415
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Merge the two state structures into oneMauro Carvalho Chehab1-567/+454
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Remove unused data structuresMauro Carvalho Chehab1-83/+14
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Use Unix standard error handlingMauro Carvalho Chehab1-1220/+1139
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Remove internal version checksMauro Carvalho Chehab1-7/+1
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Move data structures to the driverMauro Carvalho Chehab2-527/+528
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: get rid of compilation warningsMauro Carvalho Chehab2-22/+24
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Remove unused stuffMauro Carvalho Chehab1-512/+0
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Re-define functions as staticMauro Carvalho Chehab2-114/+44
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Remove most of the #if'sMauro Carvalho Chehab2-93/+4
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Use standard Linux types, instead of redefining themMauro Carvalho Chehab2-418/+406
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Fix the driver to make it compileMauro Carvalho Chehab2-9/+17
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Move code from mt2063_cfg.hMauro Carvalho Chehab2-122/+129
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: Fix some Coding styles at mt2063.hMauro Carvalho Chehab1-152/+119
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] mt2063: CodingStyle fixesMauro Carvalho Chehab3-5191/+5373
convert to Unix eol, run Lindent and remove bad whitespaces Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-01-04[media] add driver for mt2063Mauro Carvalho Chehab3-0/+5326
Those files are marked as licensed with GPL, so, it is ok to merge. They came from Terratec site: http://linux.terratec.de/files/TERRATEC_H7/20110323_TERRATEC_H7_Linux.tar.gz Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] dvb: don't use DVBv3 bandwidth macrosMauro Carvalho Chehab7-53/+12
Every frontend now uses DVBv5 way. So, let's not use the DVBv3 macros internally anymore. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] tuners: remove dvb_frontend_parameters from set_params()Mauro Carvalho Chehab16-34/+18
This is a big patch, yet trivial: now that all tuners use the DVBv5 way to pass parameters (e. g. via fe->dtv_property_cache), the extra parameter can be removed from set_params() call. After this change, very few DVBv3 specific stuff are left at the tuners. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] dvb: remove dvb_frontend_parameters from calc_regs()Mauro Carvalho Chehab1-18/+13
The calc_regs() callback is used by a few frontends (mt352, nxt200x, digitv and zl10353). On all places it is called, the parameters are set by DVBv5 way. So, just use the DVBv5 struct and remove the extra parameter. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] tuner-simple: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-17/+46
Despite its name, tuner-simple has a complex logic to set freqs ;) Basically, it can be called by two different ways: via set_params() or via calc_regs() callbacks. Both are bound to the DVBv3 API. Also, set_params internally calls calc_regs(). In order to get rid of DVBv3 params at set_params(), it shouldn't call calc_regs() anymore. The code duplication is very small, as most of the code there is just to check for invalid parameters. With regards to calc_regs(), it should still trust on bandwidth and frequency parameters passed via DVBv3, until a later patch fixes it. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] xc4000: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-55/+42
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] tuner-xc2028: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-47/+36
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] tda827x: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-21/+28
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] tda18271-fe: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-40/+34
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] tda18271: add support for QAM 7 MHz mapMauro Carvalho Chehab2-0/+5
This standard is not properly documented, but its settings are at the tda18271dd driver, and are somewhat obvious, as they follow the same logic as DVB-T 7MHz. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] tda18218: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-9/+6
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] mxl5007t: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-27/+24
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] mxl5005s: fix: don't discard bandwidth changesMauro Carvalho Chehab1-1/+2
There is a bug on mxl5005s logic: when the bandwidth changes, but using the same delivery system, the code discard the set_params() reconfiguration request. This was happening because, in the previous coding, the bandwidth calculus were after the check for delivery system changes. The previous patch changed the logic to estimate the bandwidth to happend together with the changes at the delivery system. So, with a one-statement change, it is possible to make the tuner to reconfigure, in order to adjust to bandwidth changes. this will likely fix issues on countries that use 7MHz/8MHz DVB-T channels. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] mxl5005s: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-36/+29
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] mt2266: use DVBv5 parameters for set_params()Mauro Carvalho Chehab1-11/+14
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] max2165: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-23/+13
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] mc44s803: use DVBv5 parameters on set_params()Mauro Carvalho Chehab1-3/+4
Instead of using DVBv3 parameters, rely on DVBv5 parameters to set the tuner. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] mt2031: remove fake implementaion of get_bandwidth()Mauro Carvalho Chehab2-16/+2
This driver implements a fake get_bandwidth() callback. In reallity, the tuner driver won't adjust its low-pass filter based on a bandwidth, and were just providing a fake method for demods to read whatever was "set". This code is useless, as none of the drivers that use this tuner seems to require a get_bandwidth() callback. While here, convert set_params to use the DVBv5 way to pass parameters to tuners. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2011-12-31[media] mt2060: remove fake implementaion of get_bandwidth()Mauro Carvalho Chehab2-11/+2
This driver implements a fake get_bandwidth() callback. In reallity, the tuner driver won't adjust its low-pass filter based on a bandwidth, and were just providing a fake method for demods to read whatever was "set". This code is useless, as none of the drivers that use this tuner seems to require a get_bandwidth() callback. While here, convert set_params to use the DVBv5 way to pass parameters to tuners. Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.