Lines Matching refs:a
9 The Kernel Digital TV Demux kABI defines a driver-internal interface for
10 registering low-level, hardware specific driver to a hardware independent
16 used to select the TS source of a demux and to manage the demux resources.
17 When the demux client allocates a resource via the demux kABI, it receives
18 a pointer to the kABI of that resource.
20 Each demux receives its TS input from a DVB front-end or from memory, as
21 set via this demux kABI. In a system with more than one front-end, the kABI
22 can be used to select one of the DVB front-ends as a TS source for a demux,
32 :c:type:`dmx_demux`. For example, a demux interface might support Section filtering,
41 Note that functions called from a bottom half context must not sleep.
42 Even a simple memory allocation without using ``GFP_ATOMIC`` can result in a
44 Linux Kernel calls the functions of a network device interface from a
45 bottom half context. Thus, if a demux kABI function is called from network
55 The function pointers of this abstract interface are not packed into a
62 a demux driver calls one of these functions, the driver is not allowed to
63 call the function again before the original call returns. If a callback is
64 triggered by a hardware interrupt, it is recommended to use the Linux
65 bottom half mechanism or start a tasklet instead of making the callback
66 function call directly from a hardware interrupt.