Searched full:timings (Results 1 – 25 of 87) sorted by relevance
1234
| /Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 23 GPMC has certain timings that has to be programmed for proper
25 timings. To have peripheral work with gpmc, peripheral timings has to
28 dependency for certain gpmc timings on gpmc clock frequency. Hence a
31 Generic routine provides a generic method to calculate gpmc timings
32 from gpmc peripheral timings. struct gpmc_device_timings fields has to
33 be updated with timings from the datasheet of the peripheral that is
34 connected to gpmc. A few of the peripheral timings can be fed either
49 on understanding of gpmc timings, peripheral timings, available
54 gpmc timing dependency on peripheral timings:
172 Many of gpmc timings are dependent on other gpmc timings (a few
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | dv-timings.rst | 10 .. _dv-timings:
13 Digital Video (DV) Timings
17 and the corresponding video timings. Today there are many more different
20 extend the API to select the video timings for these interfaces. Since
23 set/get video timings at the input and output.
25 These ioctls deal with the detailed digital video timings that define
28 widths etc. The ``linux/v4l2-dv-timings.h`` header can be used to get
29 the timings of the formats in the :ref:`cea861` and :ref:`vesadmt`
32 To enumerate and query the attributes of the DV timings supported by a
36 DV timings for the device applications use the
[all …]
|
| D | vidioc-query-dv-timings.rst | 45 The hardware may be able to detect the current DV timings automatically,
49 the timings, it will fill in the timings structure.
53 Drivers shall *not* switch timings automatically if new
54 timings are detected. Instead, drivers should send the
57 The reason is that new timings usually mean different buffer sizes as
60 :ref:`VIDIOC_QUERY_DV_TIMINGS`, and if the detected timings are valid they
61 will have to stop streaming, set the new timings, allocate new buffers
64 If the timings could not be detected because there was no signal, then
69 capabilities), then the driver fills in whatever timings it could find
72 found timings with the hardware's capabilities in order to give more
[all …]
|
| D | vidioc-enum-dv-timings.rst | 19 VIDIOC_ENUM_DV_TIMINGS - VIDIOC_SUBDEV_ENUM_DV_TIMINGS - Enumerate supported Digital Video timings
45 While some DV receivers or transmitters support a wide range of timings,
46 others support only a limited number of timings. With this ioctl
47 applications can enumerate a list of known supported timings. Call
49 also supports other standards or even custom timings that are not in
52 To query the available timings, applications initialize the ``index``
58 DV timings, applications shall begin at index zero, incrementing by one
63 Drivers may enumerate a different set of DV timings after
66 When implemented by the driver DV timings of subdevices can be queried
68 subdevice node. The DV timings are specific to inputs (for DV receivers)
[all …]
|
| D | vidioc-g-dv-timings.rst | 19 … VIDIOC_SUBDEV_G_DV_TIMINGS - VIDIOC_SUBDEV_S_DV_TIMINGS - Get or set DV timings for input or outp…
51 To set DV timings for the input or output, applications use the
52 :ref:`VIDIOC_S_DV_TIMINGS <VIDIOC_G_DV_TIMINGS>` ioctl and to get the current timings,
60 The ``linux/v4l2-dv-timings.h`` header can be used to get the timings of
62 the current input or output does not support DV timings (e.g. if
79 Digital video timings are not supported for this input or output.
82 The device is busy and therefore can not change the timings.
187 - Type of DV timings as listed in :ref:`dv-timing-types`.
194 - Timings defined by BT.656/1120 specifications
217 - BT.656/1120 timings
[all …]
|
| D | user-func.rst | 28 vidioc-dv-timings-cap
32 vidioc-enum-dv-timings
45 vidioc-g-dv-timings
69 vidioc-query-dv-timings
|
| D | vidioc-dv-timings-cap.rst | 119 - Type of DV timings as listed in :ref:`dv-timing-types`.
136 - BT.656/1120 timings capabilities of the hardware.
159 - CVT/GTF specific: the timings can make use of reduced blanking
162 - Can support non-standard timings, i.e. timings not belonging to
|
| /Documentation/fb/ |
| D | viafb.modes | 31 timings 39722 48 16 33 10 96 2 endmode mode "480x640-60"
33 geometry 480 640 480 640 32 timings 39722 72 24 19 1 48 3 endmode
54 geometry 640 480 640 480 32 timings 31747 120 16 16 1 64 3 endmode
75 geometry 640 480 640 480 32 timings 27777 80 56 25 1 56 3 endmode
96 geometry 640 480 640 480 32 timings 23168 104 40 25 1 64 3 endmode
117 geometry 640 480 640 480 32 timings 19081 104 40 31 1 64 3 endmode
138 geometry 720 480 720 480 32 timings 37202 88 16 14 1 72 3 endmode
159 geometry 800 480 800 480 32 timings 33805 96 24 10 3 72 7 endmode
180 geometry 720 576 720 576 32 timings 30611 96 24 17 1 72 3 endmode
202 timings 25000 88 40 23 1 128 4 hsync high vsync high endmode
[all …]
|
| D | modedb.rst | 30 <bpp> and <refresh>, if specified) the timings will be calculated using
31 VESA(TM) Coordinated Video Timings instead of looking up the mode from a table.
72 What is the VESA(TM) Coordinated Video Timings (CVT)?
82 common set of tools to enable new timings to be developed in a
85 This is the third standard approved by VESA(TM) concerning video timings. The
86 first was the Discrete Video Timings (DVT) which is a collection of
88 Formula (GTF) which is an algorithm to calculate the timings, given the
128 timings will still be calculated.
|
| /Documentation/devicetree/bindings/lpddr2/ |
| D | lpddr2.txt | 35 - The lpddr2 node may have one or more child nodes of type "lpddr2-timings".
36 "lpddr2-timings" provides AC timing parameters of the device for
37 a given speed-bin. The user may provide the timings for as many
39 bindings/lpddr2/lpddr2-timings.txt for more information on "lpddr2-timings"
60 timings_elpida_ECB240ABACN_400mhz: lpddr2-timings@0 {
61 compatible = "jedec,lpddr2-timings";
81 timings_elpida_ECB240ABACN_200mhz: lpddr2-timings@1 {
82 compatible = "jedec,lpddr2-timings";
|
| D | lpddr2-timings.txt | 4 - compatible : Should be "jedec,lpddr2-timings"
33 timings_elpida_ECB240ABACN_400mhz: lpddr2-timings@0 {
34 compatible = "jedec,lpddr2-timings";
|
| /Documentation/media/v4l-drivers/ |
| D | davinci-vpbe.rst | 52 API to set timings in VENC for a specific display resolution. As of this
58 setting timings at LCD controller port when external encoders are connected
59 at the port or LCD panel timings required. When external encoder/LCD panel
60 is connected, the timings for a specific standard/preset is retrieved from
61 the board specific table and the values are used to set the timings in
66 timings for the resolution supported and setting the dot clock. So we could
68 output name to board-xxx-evm.c). A table of timings for various LCDs
93 - add timings for supporting ths8200
|
| /Documentation/devicetree/bindings/display/imx/ |
| D | ldb.txt | 48 or a display-timings node that describes the video timings for the connected
62 display-timings are used instead.
64 Optional properties (required if display-timings are used):
66 - display-timings : A node that describes the display timings as defined in
117 /* Using display-timings and fsl,data-mapping/width instead */
125 display-timings {
|
| /Documentation/devicetree/bindings/display/exynos/ |
| D | exynos7-decon.txt | 30 - i80-if-timings: timing configuration for lcd i80 interface support.
34 - display-timings: timing settings for DECON, as described in document [1].
35 Can be used in case timings cannot be provided otherwise
36 or to override timings provided by the panel.
|
| D | samsung-fimd.txt | 41 - display-timings: timing settings for FIMD, as described in document [1].
42 Can be used in case timings cannot be provided otherwise
43 or to override timings provided by the panel.
45 - i80-if-timings: timing configuration for lcd i80 interface support.
|
| /Documentation/media/kapi/ |
| D | v4l2-dv-timings.rst | 3 V4L2 DV Timings functions
6 .. kernel-doc:: include/media/v4l2-dv-timings.h
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra30-mc.txt | 26 emc-timings subnode
29 The node should contain a "emc-timings" subnode for each supported RAM type (see field RAM_CODE in
32 Required properties for "emc-timings" nodes :
38 Each "emc-timings" node should contain a subnode for every supported EMC clock rate.
93 emc-timings-3 {
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | samsung,s6e8aa0.txt | 9 - display-timings: timings for the connected panel as described by [1]
43 display-timings {
|
| D | samsung,ld9040.txt | 9 - display-timings: timings for the connected panel according to [1]
43 display-timings {
|
| D | panel-common.yaml | 55 # Display Timings
60 require specific display timings. The panel-timing subnode expresses those
61 timings as specified in the timing subnode section of the display timing
125 order and timings of the power supplies, in many cases a single power
|
| /Documentation/devicetree/bindings/clock/ |
| D | nvidia,tegra124-car.txt | 25 The node should contain a "emc-timings" subnode for each supported RAM type (see
28 Required properties for "emc-timings" nodes :
32 Each "emc-timings" node should contain a "timing" subnode for every supported
90 emc-timings-3 {
|
| /Documentation/devicetree/bindings/mtd/ |
| D | fsmc-nand.txt | 13 - timings: array of 6 bytes for NAND timings. The meanings of these bytes
54 timings = /bits/ 8 <0 0 0 2 3 0>;
|
| /Documentation/devicetree/bindings/display/tilcdc/ |
| D | panel.txt | 15 - display-timings: typical videomode of lcd panel. Multiple video modes
16 can be listed if the panel supports multiple timings, but the 'native-mode'
50 display-timings {
|
| /Documentation/devicetree/bindings/display/ |
| D | wm,wm8505-fb.txt | 10 - display-timings: see display-timing.txt for information
19 display-timings {
|
| D | via,vt8500-fb.txt | 11 - display-timings: see display-timing.txt for information
21 display-timings {
|
1234