Lines Matching refs:that

35       activities that ensure correct operation of the device.
46   lot of work went into the driver to ensure that any kind of
48   driver internally leverages V4L to do its work but that really has
52   about APIs and also feel that it is a good design principle to keep
57   possible to produce a DVB high level interface that can sit right
71   to link things up with that source tree.  Please see the Makefile
72   here for comments that explain how to do that.
81   pvrusb2-audio.[ch] - This is glue logic that resides between this
98     messages that can be enabled within the driver.
106   pvrusb2-eeprom.[ch] - This is glue logic that resides between this
114     (proxy through USB instead of PCI) are enough different that this
131     that handle overall control of a specific pvrusb2 device.
139     implement just the logic that makes sense for a pure V4L
148     commands that are in turn send to the various I2C modules.
153     commands that are in turn send to the various I2C modules.
159     through here that other V4L modules can reach into this driver to
185   pvrusb2-tuner.[ch] - This is glue logic that resides between this
194     pvrusb2 driver into video4linux.  It is through here that V4L
196     ways.  Note that **ALL** V4L functionality is published only
199   pvrusb2-video-*.[ch] - This is glue logic that resides between this
201     elsewhere in V4L).  Note that saa711x.ko used to be known as
203     selected depending on the particular saa711[5x].ko that is found.
206     (and at the moment the driver has very little that needs to be