Lines Matching full:api
1 <title>Kernel Demux API</title>
2 <para>The kernel demux API defines a driver-internal interface for registering low-level,
4 DVB device driver writers. The header file for this API is named <emphasis role="tt">demux.h</empha…
67 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
90 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
97 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
116 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
123 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
185 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
228 void⋆ priv; /⋆ Pointer to private data of the API client ⋆/
293 <title>Demux Directory API</title>
296 is possible using this API.
459 <title>Demux API</title>
460 <para>The demux API should be implemented for each demux in the system. It is used to select
462 client allocates a resource via the demux API, it receives a pointer to the API of that
466 demux API. In a system with more than one front-end, the API can be used to select one of
468 demux API only controls front-ends regarding their connections with demuxes; the APIs
475 might support Section filtering, but not TS or PES filtering). The API client is expected to
479 <para>Whenever the functions of the demux API modify shared data, the possibilities of lost
486 interface from a bottom half context. Thus, if a demux API function is called from network
519 <para>Pointer to the demux API and instance data.</para>
576 <para>Pointer to the demux API and instance data.</para>
615 callback API (see 0). The function returns when all the data in the buffer has
636 <para>Pointer to the demux API and instance data.</para>
704 <para>Pointer to the demux API and instance data.</para>
712 <para>Pointer to the TS feed API and instance data.</para>
780 <para>Pointer to the demux API and instance data.</para>
787 <para>Pointer to the TS feed API and instance data.</para>
818 software. The caller obtains an API pointer of type dmx_section_feed_t as an
819 out parameter. Using this API the caller can set filtering parameters and start
838 <para>Pointer to the demux API and instance data.</para>
846 <para>Pointer to the section feed API and instance data.</para>
916 <para>Pointer to the demux API and instance data.</para>
924 <para>Pointer to the section feed API and instance data.</para>
974 <para>Pointer to the demux API and instance data.</para>
1051 version. The function will be called from the demux API implementation;
1052 the API client need not call this function directly. Section-level scrambling
1057 function not available) in most demux API implementations. Nevertheless, it
1087 <para>Pointer to the demux API and instance data.</para>
1187 <para>Pointer to the demux API and instance data.</para>
1269 <para>Pointer to the demux API and instance data.</para>
1339 <para>Pointer to the demux API and instance data.</para>
1387 <para>Pointer to the demux API and instance data.</para>
1448 <para>Pointer to the demux API and instance data.</para>
1470 <title>Demux Callback API</title>
1471 <para>This kernel-space API comprises the callback functions that deliver filtered data to the
1472 demux client. Unlike the other APIs, these API functions are provided by the client and called
1477 of each other. As an example, it is possible for the API client to provide several
1481 <para>The functions that implement the callback API need not be re-entrant: when a demux
1494 <para>This function, provided by the client of the demux API, is called from the
1503 of the set() function in the TS Feed API. It is expected that the buffer1 and
1525 duration is controlled by the set() function in the TS Feed API.</para>
1625 stop_filtering() on the TS Feed API.</para>
1635 <para>This function, provided by the client of the demux API, is called from the
1637 enabled using the function start_filtering() of the section feed API. When the
1646 API is implemented as a client of the TS Feed API, because the TS Feed
1648 can be configured using the set() function in the Section Feed API. If there
1730 stop_filtering() on the Section Feed API.</para>
1735 <title>TS Feed API</title>
1737 Using this API, the client can set the filtering properties to start/stop filtering TS
1738 packets on a particular TS feed. The API is defined as an abstract interface of the type
1742 client can get the handle of a TS feed API by calling the function allocate_ts_feed() in the
1743 demux API.
1772 <para>Pointer to the TS feed API and instance data.</para>
1780 specified PID will be passed to the API client.</para>
1856 value to filter can be set by the API client. All matching TS packets are
1875 <para>Pointer to the TS feed API and instance data.</para>
1919 <para>Pointer to the TS feed API and instance data.</para>
1941 <title>Section Feed API</title>
1943 API, the client can set the properties of a section feed and to start/stop filtering. The API is
1946 a section feed API by calling the function allocate_section_feed() in the demux
1947 API.
1949 <para>On demux platforms that provide section filtering in hardware, the Section Feed API
1952 software. In the latter case the Section Feed API implementation can be a client of the TS
1953 Feed API.
1969 demux API. Note that according to the MPEG-2 Systems specification, only
1991 <para>Pointer to the section feed API and instance data.</para>
2076 the struct is initialized by the API implementation to the value of the feed
2077 parameter. The priv pointer is not used by the API implementation, and can
2112 <para>Pointer to the section feed API and instance data.</para>
2176 <para>Pointer to the section feed API and instance data.</para>
2221 at least one section filter, it is delivered to the API client. The section
2241 <para>Pointer to the section feed API and instance data.</para>
2288 <para>Pointer to the section feed API and instance data.</para>