Home
last modified time | relevance | path

Searched full:timings (Results 1 – 25 of 91) sorted by relevance

1234

/Documentation/driver-api/memory-devices/
Dti-gpmc.rst23 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/userspace-api/media/v4l/
Ddv-timings.rst3 .. _dv-timings:
6 Digital Video (DV) Timings
10 and the corresponding video timings. Today there are many more different
13 extend the API to select the video timings for these interfaces. Since
16 set/get video timings at the input and output.
18 These ioctls deal with the detailed digital video timings that define
21 widths etc. The ``linux/v4l2-dv-timings.h`` header can be used to get
22 the timings of the formats in the :ref:`cea861` and :ref:`vesadmt`
25 To enumerate and query the attributes of the DV timings supported by a
29 DV timings for the device applications use the
[all …]
Dvidioc-query-dv-timings.rst38 The hardware may be able to detect the current DV timings automatically,
42 the timings, it will fill in the timings structure.
46 Drivers shall *not* switch timings automatically if new
47 timings are detected. Instead, drivers should send the
50 The reason is that new timings usually mean different buffer sizes as
53 :ref:`VIDIOC_QUERY_DV_TIMINGS`, and if the detected timings are valid they
54 will have to stop streaming, set the new timings, allocate new buffers
57 If the timings could not be detected because there was no signal, then
62 capabilities), then the driver fills in whatever timings it could find
65 found timings with the hardware's capabilities in order to give more
[all …]
Dvidioc-enum-dv-timings.rst13 VIDIOC_ENUM_DV_TIMINGS - VIDIOC_SUBDEV_ENUM_DV_TIMINGS - Enumerate supported Digital Video timings
38 While some DV receivers or transmitters support a wide range of timings,
39 others support only a limited number of timings. With this ioctl
40 applications can enumerate a list of known supported timings. Call
42 also supports other standards or even custom timings that are not in
45 To query the available timings, applications initialize the ``index``
51 DV timings, applications shall begin at index zero, incrementing by one
56 Drivers may enumerate a different set of DV timings after
59 When implemented by the driver DV timings of subdevices can be queried
61 subdevice node. The DV timings are specific to inputs (for DV receivers)
[all …]
Dvidioc-g-dv-timings.rst13 … VIDIOC_SUBDEV_G_DV_TIMINGS - VIDIOC_SUBDEV_S_DV_TIMINGS - Get or set DV timings for input or outp…
46 To set DV timings for the input or output, applications use the
47 :ref:`VIDIOC_S_DV_TIMINGS <VIDIOC_G_DV_TIMINGS>` ioctl and to get the current timings,
59 The ``linux/v4l2-dv-timings.h`` header can be used to get the timings of
61 the current input or output does not support DV timings (e.g. if
77 Digital video timings are not supported for this input or output.
80 The device is busy and therefore can not change the timings.
187 - Type of DV timings as listed in :ref:`dv-timing-types`.
192 - Timings defined by BT.656/1120 specifications
216 - BT.656/1120 timings
[all …]
Duser-func.rst21 vidioc-dv-timings-cap
25 vidioc-enum-dv-timings
38 vidioc-g-dv-timings
62 vidioc-query-dv-timings
Dvidioc-dv-timings-cap.rst110 - Type of DV timings as listed in :ref:`dv-timing-types`.
125 - BT.656/1120 timings capabilities of the hardware.
148 - CVT/GTF specific: the timings can make use of reduced blanking
151 - Can support non-standard timings, i.e. timings not belonging to
/Documentation/fb/
Dviafb.modes31 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 …]
Dmodedb.rst38 <bpp> and <refresh>, if specified) the timings will be calculated using
39 VESA(TM) Coordinated Video Timings instead of looking up the mode from a table.
85 What is the VESA(TM) Coordinated Video Timings (CVT)?
95 common set of tools to enable new timings to be developed in a
98 This is the third standard approved by VESA(TM) concerning video timings. The
99 first was the Discrete Video Timings (DVT) which is a collection of
101 Formula (GTF) which is an algorithm to calculate the timings, given the
141 timings will still be calculated.
/Documentation/devicetree/bindings/display/panel/
Ddisplay-timings.yaml4 $id: http://devicetree.org/schemas/display/panel/display-timings.yaml#
7 title: display timings
15 A display panel may be able to handle several display timings,
17 The display-timings node makes it possible to specify the timings
22 const: display-timings
46 display-timings {
Dpanel-common.yaml54 # Display Timings
58 require specific display timings. The panel-timing subnode expresses those
59 timings.
62 display-timings:
64 Some display panels support several resolutions with different timings.
65 The display-timings bindings supports specifying several timings and
67 $ref: display-timings.yaml#
133 order and timings of the power supplies, in many cases a single power
Dsamsung,s6e8aa0.yaml23 display-timings: true
63 - display-timings
87 display-timings {
Dsamsung,ld9040.yaml23 display-timings: true
56 - display-timings
81 display-timings {
/Documentation/devicetree/bindings/display/imx/
Dldb.txt48 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/memory-controllers/
Dnvidia,tegra124-emc.yaml51 "^emc-timings-[0-9]+$":
75 timings
81 timings
87 timings
99 value of the EMC_BGBIAS_CTL0 register for this set of timings
104 value of the EMC_CFG register for this set of timings
109 value of the EMC_CFG_2 register for this set of timings
114 value of the EMC_CTT_TERM_CTRL register for this set of timings
119 value of the EMC_MRW register for this set of timings
124 value of the EMC_MRW2 register for this set of timings
[all …]
Dti,gpmc-child.yaml17 configuring the GPMC settings/timings and will accompany the bindings
28 # Chip-select signal timings corresponding to GPMC_CONFIG2:
41 # ADV signal timings corresponding to GPMC_CONFIG3:
66 # WE signals timings corresponding to GPMC_CONFIG4:
75 # OE signals timings corresponding to GPMC_CONFIG4:
92 # Access time and cycle time timings (in nanoseconds) corresponding to
/Documentation/driver-api/media/
Dv4l2-dv-timings.rst3 V4L2 DV Timings functions
6 .. kernel-doc:: include/media/v4l2-dv-timings.h
/Documentation/devicetree/bindings/memory-controllers/ddr/
Djedec,lpddr2.yaml128 "^lpddr2-timings":
129 $ref: jedec,lpddr2-timings.yaml
131 The lpddr2 node may have one or more child nodes of type "lpddr2-timings".
132 "lpddr2-timings" provides AC timing parameters of the device for
133 a given speed-bin. The user may provide the timings for as many
164 compatible = "jedec,lpddr2-timings";
185 compatible = "jedec,lpddr2-timings";
Djedec,lpddr2-timings.yaml4 $id: http://devicetree.org/schemas/memory-controllers/ddr/jedec,lpddr2-timings.yaml#
14 const: jedec,lpddr2-timings
116 timings {
117 compatible = "jedec,lpddr2-timings";
Djedec,lpddr3-timings.yaml4 $id: http://devicetree.org/schemas/memory-controllers/ddr/jedec,lpddr3-timings.yaml#
14 const: jedec,lpddr3-timings
134 timings {
135 compatible = "jedec,lpddr3-timings";
/Documentation/devicetree/bindings/display/tilcdc/
Dpanel.txt15 - 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/mtd/
Dfsmc-nand.txt13 - 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/
Dwm,wm8505-fb.txt10 - display-timings: see display-timing.txt for information
19 display-timings {
Dvia,vt8500-fb.txt11 - display-timings: see display-timing.txt for information
21 display-timings {
/Documentation/devicetree/bindings/display/samsung/
Dsamsung,exynos7-decon.yaml34 display-timings:
35 $ref: ../panel/display-timings.yaml#
37 i80-if-timings:

1234