Based on kernel version 6.19. Page generated on 2026-02-12 08:38 EST.
| 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 | # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 --- $id: http://devicetree.org/schemas/display/panel/display-timings.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: display timings maintainers: - Thierry Reding <thierry.reding@gmail.com> - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> - Sam Ravnborg <sam@ravnborg.org> description: | A display panel may be able to handle several display timings, with different resolutions. The display-timings node makes it possible to specify the timings and to specify the timing that is native for the display. properties: $nodename: const: display-timings native-mode: $ref: /schemas/types.yaml#/definitions/phandle description: | The default display timing is the one specified as native-mode. If no native-mode is specified then the first node is assumed to be the native mode. patternProperties: "^timing": type: object $ref: panel-timing.yaml# additionalProperties: false examples: - |+ /* * Example that specifies panel timing using minimum, typical, * maximum values as commonly used in datasheet description. * timing1 is the native-mode. */ display-timings { native-mode = <&timing1>; timing0 { /* 1920x1080p24 */ clock-frequency = <148500000>; hactive = <1920>; vactive = <1080>; hsync-len = <0 44 60>; hfront-porch = <80 88 95>; hback-porch = <100 148 160>; vfront-porch = <0 4 6>; vback-porch = <0 36 50>; vsync-len = <0 5 6>; }; timing1 { /* 1920x1080p24 */ clock-frequency = <52000000>; hactive = <1920>; vactive = <1080>; hfront-porch = <25>; hback-porch = <25>; hsync-len = <0 25 25>; vback-porch = <2>; vfront-porch = <2>; vsync-len = <2>; hsync-active = <1>; pixelclk-active = <1>; }; }; ... |