OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/dts/bindings/display/ilitek,ili9340.yaml

98 lines
2.0 KiB
YAML
Raw Normal View History

drivers: display: Added DTS support for ili9340 Added device tree support for ili9340 display driver Part of #10894 Signed-off-by: Jan Van Winkel <jan.van_winkel@dxplore.eu>
2018-10-30 02:01:50 +08:00
# Copyright (c) 2018, Jan Van Winkel <jan.van_winkel@dxplore.eu>
drivers: display: ili9xxx: generalize ILI display driver Make driver generic for multiple ILI displays. The adopted strategy is to share all driver code except register initialization, which has been found to have some specific registers/values depending on the controller. The driver has been adjusted to support multiple compatibles. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-10-27 02:20:16 +08:00
# Copyright (c) 2020, Teslabs Engineering S.L.
drivers: display: Added DTS support for ili9340 Added device tree support for ili9340 display driver Part of #10894 Signed-off-by: Jan Van Winkel <jan.van_winkel@dxplore.eu>
2018-10-30 02:01:50 +08:00
# SPDX-License-Identifier: Apache-2.0
yaml: Remove redundant document separators YAML document separators are needed e.g. when doing $ cat doc1.yaml doc2.yaml | <parser> For the bindings, we never parse concatenated documents. Assume we don't for any other .yaml files either. Having document separators in e.g. base.yaml makes !include a bit confusing, since the !included files are merged and not separate documents (the merging is done in Python code though, so it makes no difference for behavior). The replacement was done with $ git ls-files '*.yaml' | \ xargs sed -i -e '${/\s*\.\.\.\s*/d;}' -e 's/^\s*---\s*$//' First pattern removes ... at the end of files, second pattern clears a line with a lone --- on it. Some redundant blank lines at the end of files were cleared with $ git ls-files '*.yaml' | xargs sed -i '${/^\s*$/d}' This is more about making sure people can understand why every part of a binding is there than about removing some text. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-06-19 06:03:49 +08:00
dts: bindings: Remove 'title:' and put all info. into 'description:' Add any useful information from 'title:' to the 'description:' strings (e.g. explanations of acronyms), and remove 'title:' as well as any copy-pasted "this binding gives a ..." boilerplate. Also clean some description strings up a bit. Some other things could probably be cleaned up (replacing 'GPIO node' with 'GPIO controller' on controllers for consistency, for example), but I kept things close to the original to avoid accidentally messing up. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-19 15:39:11 +08:00
description: ILI9340 320x240 display controller
drivers: display: Added DTS support for ili9340 Added device tree support for ili9340 display driver Part of #10894 Signed-off-by: Jan Van Winkel <jan.van_winkel@dxplore.eu>
2018-10-30 02:01:50 +08:00
scripts: dts: Simplify and improve 'compatible' matching Instead of properties: compatible: constraint: "foo" , just have compatible: "foo" at the top level of the binding. For backwards compatibility, the old 'properties: compatible: ...' form is still accepted for now, and is treated the same as a single-element 'compatible:'. The old syntax was inspired by dt-schema (though it isn't dt-schema-compatible), which is in turn a thin wrapper around json-schema (the idea is to transform .dts files into YAML and then verify them). Maybe the idea was to gradually switch the syntax over to dt-schema and then be able to use unmodified dt-schema bindings, but dt-schema is really a different kind of tool (a completely standalone linter), and works very differently from our stuff (see schemas/dt-core.yaml in the dt-schema repo to get an idea of just how differently). Better to keep it simple. This commit also piggybacks some clarifications to the binding template re. '#cells:'. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-08-20 02:32:25 +08:00
compatible: "ilitek,ili9340"
drivers: display: ili9xxx: generalize ILI display driver Make driver generic for multiple ILI displays. The adopted strategy is to share all driver code except register initialization, which has been found to have some specific registers/values depending on the controller. The driver has been adjusted to support multiple compatibles. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-10-27 02:20:16 +08:00
include: ilitek,ili9xxx-common.yaml
drivers: display: Added DTS support for ili9340 Added device tree support for ili9340 display driver Part of #10894 Signed-off-by: Jan Van Winkel <jan.van_winkel@dxplore.eu>
2018-10-30 02:01:50 +08:00
properties:
drivers: display: ili9340: move gamma parameters to DT Move gamma curve and correction registers GAMSET, PGAMCTRL and NGAMCTRL to DT. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-09-15 20:44:46 +08:00
gamset:
type: uint8-array
default: [0x01]
description:
Gamma set (GAMSET) register value.
drivers: display: ili9340: move frame rate control register to DT Move FRMCTR1 register settings to DT. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-09-15 21:29:12 +08:00
frmctr1:
type: uint8-array
default: [0x00, 0x1b]
description:
Frame rate control (in normal mode / full colors) (FRMCTR1) register value.
drivers: display: ili9340: move display function control to DT Move display function control (DISCTRL) register settings to DT. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-09-15 21:40:36 +08:00
disctrl:
type: uint8-array
default: [0x0a, 0x82, 0x27]
description:
Display function control (DISCTRL) register value. Note that changing
default SS bit value (0) may interfere with display rotation.
drivers: display: ili9340: add support for pwctrl in DT Add support for setting PWRCTRL1/2 registers via DT. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-09-15 18:23:07 +08:00
pwctrl1:
type: uint8-array
default: [0x26, 0x00]
description:
Power control 1 (PWCTRL1) register values.
pwctrl2:
type: uint8-array
default: [0x00]
description:
Power control 2 (PWCTRL2) register values.
drivers: display: ili9340: move gamma parameters to DT Move gamma curve and correction registers GAMSET, PGAMCTRL and NGAMCTRL to DT. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-09-15 20:44:46 +08:00
drivers: display: ili9340: move VCOM parameters to DT Move VCOM control 1/2 register values to DT. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-09-15 21:18:20 +08:00
vmctrl1:
type: uint8-array
default: [0x31, 0x3c]
description:
VCOM control 1 (VMCTRL1) register values.
vmctrl2:
type: uint8-array
default: [0xc0]
description:
VCOM control 2 (VMCTRL2) register values.
drivers: display: ili9340: move gamma parameters to DT Move gamma curve and correction registers GAMSET, PGAMCTRL and NGAMCTRL to DT. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-09-15 20:44:46 +08:00
pgamctrl:
type: uint8-array
default: [
0x0f,
0x22,
0x1f,
0x0a,
0x0e,
0x06,
0x4d,
0x76,
0x3b,
0x03,
0x0e,
0x04,
0x13,
0x0e,
0x0c
]
description:
Positive gamma correction (PGAMCTRL) register values.
ngamctrl:
type: uint8-array
default: [
0x0c,
0x23,
0x26,
0x04,
0x10,
0x04,
0x39,
0x24,
0x4b,
0x03,
0x0b,
0x0b,
0x33,
0x37,
0x0f
]
description:
Negative gamma correction (NGAMCTRL) register values.