summaryrefslogtreecommitdiffstats
path: root/mm/msync.c
diff options
context:
space:
mode:
authorMichael Krufky <mkrufky@m1k.net>2006-01-13 14:10:25 -0200
committerMauro Carvalho Chehab <mchehab@brturbo.com.br>2006-01-13 14:10:25 -0200
commit7b0ac9cdd42b254ae2ec0f6c1cc6389655e4ba96 (patch)
treec290ba6d44a608feb22e7d7af177a915419f88f3 /mm/msync.c
parentf4efb4dbf21c78939e32d96cad145421c8b5f106 (diff)
downloadblackbird-op-linux-7b0ac9cdd42b254ae2ec0f6c1cc6389655e4ba96.tar.gz
blackbird-op-linux-7b0ac9cdd42b254ae2ec0f6c1cc6389655e4ba96.zip
V4L/DVB (3359): Redesign tuners struct for maximum flexibility
- Tunertype struct redefined to allow one or more tuner_params structs per tuner definition, one for each video standard. - Each tuner_params struct has an element containing an arbitrary amount of tuner_ranges. (this is needed for dvb tuners - to be handled later) - A tuner_range may be referenced by multiple tuner_params structs. There are many duplicates in here. Reusing tuner_range structs, rather than defining new ones for each tuner, will cut down on memory usage, and is preferred when possible. - tunertype struct contains an element, has_tda988x. We must set this for all tunertypes that contain a tda988x chip, and then we can remove this setting from the various card structs. - Improves tuners array memory usage efficiency. - Right now, all tuners are using the first tuner_params[] array element for analog mode. In the future, we will be merging similar tuner definitions together, such that each tuner definition will have a tuner_params struct for each available video standard. At that point, the tuner_params[] array element will be chosen based on the video standard in use. Signed-off-by: Michael Krufky <mkrufky@m1k.net> Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
Diffstat (limited to 'mm/msync.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud