Lines Matching refs:driver

5 			    pvrusb2 driver
9   This driver is intended for the "Hauppauge WinTV PVR USB 2.0", which
10   is a USB 2.0 hosted TV Tuner.  This driver is a work in progress.
17   create a video4linux compatible driver.  I began with Aurelien's
18   last known snapshot and evolved the driver to the state it is in
21   More information on this driver can be found at:
26   This driver has a strong separation of layers.  They are very
34   1c. High level hardware driver implementation which coordinates all
37   2.  A "context" layer which manages instancing of driver, setup,
42   3.  High level interfaces which glue the driver to various published
46   lot of work went into the driver to ensure that any kind of
47   conceivable API can be laid on top of the core driver.  (Yes, the
48   driver internally leverages V4L to do its work but that really has
49   nothing to do with the API published by the driver to the outside
51   simultaneously access the driver.  I have a strong sense of fairness
60   NOTE: Complete documentation on the pvrusb2 driver is contained in
78   defined functional units within the pvrusb2 driver and bears no
82     driver and the msp3400.ko I2C client driver (which is found
86     instance of the driver.  Everything else eventually ties back to
89     interfaces tie into the driver through this module.  This module
90     helps arbitrate each interface's access to the actual driver core,
98     messages that can be enabled within the driver.
101     oriented debug interface into the driver.  Aside from being part
107     driver the tveeprom.ko module, which is itself implemented
118     in the driver used to track ALL internal state related to control
121     access to the driver should be through one of the high level
147     changes inside the pvrusb2 driver are translated into V4L1
152     changes inside the pvrusb2 driver are translated into V4L2
156     kernel-friendly I2C adaptor driver, through which other external
159     through here that other V4L modules can reach into this driver to
178   pvrusb2-main.c - This is the top level of the driver.  Module level
182     pvrusb2 driver into sysfs.  Through this interface you can do
183     everything with the driver except actually stream data.
186     driver and the tuner.ko I2C client driver (which is found
190     throughout the driver.  These macros are not really specific to
191     the driver, but they had to go somewhere.
194     pvrusb2 driver into video4linux.  It is through here that V4L
195     applications can open and operate the driver in the usual V4L
200     driver and the saa711x.ko I2C client driver (which is found
206     (and at the moment the driver has very little that needs to be