Home
last modified time | relevance | path

Searched full:frontend (Results 1 – 25 of 75) sorted by relevance

123

/Documentation/devicetree/bindings/display/
Dallwinner,sun4i-a10-display-frontend.yaml4 $id: http://devicetree.org/schemas/display/allwinner,sun4i-a10-display-frontend.yaml#
7 title: Allwinner A10 Display Engine Frontend
14 The display engine frontend does formats conversion, scaling,
20 - allwinner,sun4i-a10-display-frontend
21 - allwinner,sun5i-a13-display-frontend
22 - allwinner,sun6i-a31-display-frontend
23 - allwinner,sun7i-a20-display-frontend
24 - allwinner,sun8i-a23-display-frontend
25 - allwinner,sun8i-a33-display-frontend
26 - allwinner,sun9i-a80-display-frontend
[all …]
/Documentation/userspace-api/media/dvb/
Dfrontend_legacy_api.rst5 Frontend Legacy Data Types
14 dvb-frontend-parameters
15 dvb-frontend-event
20 Frontend Legacy Function Calls
35 fe-set-frontend
36 fe-get-frontend
Dquery-dvb-frontend-info.rst3 .. _query-dvb-frontend-info:
6 Querying frontend information
9 Usually, the first thing to do when the frontend is opened is to check
10 the frontend capabilities. This is done using
12 Digital TV API version and other characteristics about the frontend, and can
Ddvbproperty.rst26 to setup the frontend and read its status.
31 This section describes the new and recommended way to set the frontend,
36 1. On Linux DVB API version 3, setting a frontend was done via
45 the multiple delivery systems supported by a frontend.
73 :caption: Example: Setting digital TV frontend properties
79 #include <linux/dvb/frontend.h>
107 printf("Frontend set\\n");
122 frontend-stat-properties
123 frontend-property-terrestrial-systems
124 frontend-property-cable-systems
[all …]
Dfrontend.rst6 Digital TV Frontend API
9 The Digital TV frontend API was designed to support three groups of delivery
20 The Digital TV frontend controls several sub-devices including:
30 The frontend can be accessed through ``/dev/dvb/adapter?/frontend?``.
32 ``linux/dvb/frontend.h`` in your application.
53 query-dvb-frontend-info
Ddvb-fe-read-status.rst6 Querying frontend status and statistics
10 frontend will run a kernel thread that will periodically check for the
14 The information about the frontend tuner locking status can be queried
24 :ref:`Frontend statistics indicators <frontend-stat-properties>` for
Dfe-get-info.rst13 FE_GET_INFO - Query Digital TV frontend capabilities and returns information
35 All Digital TV frontend devices support the :ref:`FE_GET_INFO` ioctl. It is
42 frontend capabilities
45 Capabilities describe what a frontend can do. Some capabilities are
46 supported only on some specific frontend types.
48 The frontend capabilities are described at :c:type:`fe_caps`.
Dfrontend-stat-properties.rst6 Frontend statistics indicators
39 frontend, but it was not possible to collect it (could be a
69 - ``FE_SCALE_RELATIVE`` - The frontend provides a 0% to 100%
87 - ``FE_SCALE_RELATIVE`` - The frontend provides a 0% to 100%
107 This measurement is monotonically increased, as the frontend gets more
108 bit count measurements. The frontend may reset it when a
131 amount of bits on the transport stream, as the frontend may need to
135 This measurement is monotonically increased, as the frontend gets more
136 bit count measurements. The frontend may reset it when a
164 This measurement is monotonically increased, as the frontend gets more
[all …]
Dfe-get-property.rst13 …ROPERTY - FE_SET_PROPERTY sets one or more frontend properties. - FE_GET_PROPERTY returns one or m…
38 All Digital TV frontend devices support the ``FE_SET_PROPERTY`` and
44 - This ioctl is used to set one or more frontend properties.
46 - This is the basic command to request the frontend to tune into
60 frontend.
Dfe-set-frontend-tune-mode.rst13 FE_SET_FRONTEND_TUNE_MODE - Allow setting tuner mode flags to the frontend.
36 hence no frontend events will be generated. If a frontend device
43 Allow setting tuner mode flags to the frontend, between 0 (normal) or
Dfrontend_f_open.rst7 Digital TV frontend open()
13 fe-open - Open a frontend device
48 This system call opens a named frontend device
49 (``/dev/dvb/adapter?/frontend?``) for subsequent use. Usually the first
50 thing to do after a successful open is to find out the frontend type
Dfrontend-header.rst3 Frontend uAPI data types
6 .. kernel-doc:: include/uapi/linux/dvb/frontend.h
Dfe-read-status.rst35 All Digital TV frontend devices support the ``FE_READ_STATUS`` ioctl. It is
36 used to check about the locking status of the frontend after being
50 state changes of the frontend hardware. It is produced using the enum
Dfrontend_fcalls.rst6 Frontend Function Calls
24 fe-set-frontend-tune-mode
/Documentation/devicetree/bindings/display/mediatek/
Dmediatek,ethdr.yaml55 - description: video frontend 0 clock
56 - description: video frontend 1 clock
57 - description: graphic frontend 0 clock
58 - description: graphic frontend 1 clock
61 - description: video frontend 0 async clock
62 - description: video frontend 1 async clock
63 - description: graphic frontend 0 async clock
64 - description: graphic frontend 1 async clock
89 - description: video frontend 0 async reset
90 - description: video frontend 1 async reset
[all …]
/Documentation/driver-api/media/drivers/
Dcontributors.rst60 - for many bugfixes in the generic DVB Core, frontend drivers and
69 - for the tda1004x frontend driver, and various bugfixes
110 - for the lgdt330x frontend driver, and various bugfixes
118 - for the nxt2002 frontend driver
122 - for the nxt2004 frontend driver
126 - for the or51211 and or51132 frontend drivers, and
128 single nxt200x frontend driver.
/Documentation/driver-api/media/
Ddtv-frontend.rst3 Digital TV Frontend kABI
6 Digital TV Frontend
9 The Digital TV Frontend kABI defines a driver-internal interface for
11 frontend layer. It is only of interest for Digital TV device driver writers.
102 standards, they're specified in Hz. Due to that, if the same frontend
139 The core frontend support also supports
145 Attaching frontend driver to the bridge driver
148 Before using the Digital TV frontend core, the bridge driver should attach
149 the frontend demod, tuner and SEC devices and call
151 in order to register the new frontend at the subsystem. At device
[all …]
Ddtv-core.rst12 - Frontend drivers that are usually implemented as two separate drivers:
24 On most hardware, the frontend drivers talk with the bridge driver using an
36 dtv-frontend
/Documentation/userspace-api/media/v4l/
Dpipeline.dot7 …frontend [label="{<frontend_0> 0} | Host\nFrontend | {<frontend_1> 1}", shape=Mrecord, style=fille…
11 sensor:sensor_0 -> frontend:frontend_0 [color=blue, label="HQ: 2592x1968\nHS: 1296x984"]
12 frontend:frontend_1 -> scaler:scaler_0 [color=blue, label="HQ: 2592x1968\nHS: 1296x984"]
/Documentation/gpu/
Dxen-front.rst2 drm/xen-front Xen para-virtualized frontend driver
5 This frontend driver implements Xen para-virtualized display
15 Buffers allocated by the frontend driver
19 :doc: Buffers allocated by the frontend driver
/Documentation/ABI/stable/
Dsysfs-bus-xen-backend39 Number of flush requests from the frontend.
54 Number of read requests from the frontend.
61 Number of sectors read by the frontend.
68 Number of write requests from the frontend.
75 Number of sectors written by the frontend.
/Documentation/admin-guide/media/
Davermedia.rst26 card. The Tuner is otherwise known as the "Frontend" . The
27 Frontend of the Avermedia DVB-T is a Microtune 7202D. A timely
64 The frontend module sp887x.o, requires an external firmware.
72 At present I can say with confidence that the frontend tunes
81 ability of the frontend to function correctly.
Dtechnisat.rst25 dmesg | grep frontend may show you for example:
26 DVB: registering frontend 0 (Conexant CX24123/CX24109)...
50 - Frontend / Tuner / Demodulator module part:
53 => ``Customise the frontend modules to build`` ``Customise DVB frontends`` =>
/Documentation/ABI/testing/
Dsysfs-driver-xen-blkfront6 Maximum number of segments that the frontend will negotiate
9 memory usage. The backend picks the minimum of the frontend
/Documentation/userspace-api/media/
DMakefile10 FILES = ca.h.rst dmx.h.rst frontend.h.rst net.h.rst \
30 $(BUILDDIR)/frontend.h.rst: ${UAPI}/dvb/frontend.h ${PARSER} $(SRC_DIR)/frontend.h.rst.exceptions

123