ilitek,ili9163c (on mipi-dbi bus)
Description
Ilitek ILI9163C display controller
The Ilitek ILI9163C is a 262K colors TFT-LCD controller
with a maximum 240RGBx320 resolution.
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
Select the desired Gamma curve for the current display.
A maximum of 4 fixed gamma curves can be selected.
- 0x01: Gamma curve 1 (default)
- 0x02: Gamma curve 2
- 0x04: Gamma curve 3
- 0x08: Gamma curve 4
Default value: |
|
|
Frame rate control (in normal mode / full colors) (FRMCTR1) register value.
The driver default pair provides a balanced refresh configuration
that avoids visible flicker.
Default value: |
|
|
Gamma adjustment register value.
- 0x00: No gamma adjustment (default)
- 0x01: Apply positive and negative gamma adjustments (pgamctrl and ngamctrl).
Default value: |
|
|
Positive gamma correction (PGAMCTRL) register values.
The driver default values are set to zero to provide a neutral starting
point for the positive gamma curve.
Default value: |
|
|
Negative gamma correction (NGAMCTRL) register values.
The driver default values are set to zero to provide a neutral starting
point for the negative gamma curve.
Default value: |
|
|
Power control 1 - GVDD and voltage.
Default values: 0x0A sets GVDD to 4.8V, and 0x05 sets the voltage to 2.5V.
Default value: |
|
|
Power control 2 - AVDD, VCL, VGH and VGL supply power level.
Default value: 0x05 sets VGH to 3×AVDD and VGL to -3×AVDD.
Default value: |
|
|
Power control 3 - amount of current in Operation amplifier.
The driver default `Least` is set to reduce power
consumption while remaining sufficient for typical operation.
Default value: Legal values: |
|
|
Power control 4 - amount of current in Operational amplifier in Idle.
The driver default `Least` is set to reduce power
consumption while remaining sufficient for typical operation.
Default value: Legal values: |
|
|
Power control 5 - amount of current in Operational amplifier in Partial mode.
The driver default `Small` keeps partial-mode consumption low while still
supporting normal partial refresh behavior.
Default value: Legal values: |
|
|
VCOM control 1 - Set VCOMH Voltage.
The driver default values are set to provide a VCOMH voltage that is
compatible with a wide range of panels.
Default value: |
|
|
VCOM control 2 - Set VCOMH Voltage.
The driver default values are set to keep VCOM tuning centered around
a stable, broadly compatible setting.
Default value: |
|
|
Display rotation (CW) in degrees. If not defined, rotation is off by default.
Legal values: |
|
|
Display inversion mode. Every bit is inverted from the frame memory to the display.
|
|
|
Initial Pixel format of this controller's output data, which is sent
to a panel directly or to an adapter.
See dt-bindings/display/panel.h for a list of pixel format.
This property is required. |
|
|
Height of the panel driven by the controller, with the units in pixels.
This property is required. |
|
|
Width of the panel driven by the controller, with the units in pixels.
This property is required. |
|
|
SPI Duplex mode, full or half. By default it's always full duplex thus 0
as this is, by far, the most common mode.
Selecting half duplex allows to use SPI MOSI as a bidirectional line,
typically used when only one data line is connected.
Use the macros, not the actual enum value. Here is the concordance
list (see dt-bindings/spi/spi.h)
0 SPI_FULL_DUPLEX
2048 SPI_HALF_DUPLEX
|
|
|
SPI clock polarity which indicates the clock idle state.
If it is used, the clock idle state is logic high; otherwise, low.
|
|
|
SPI clock phase that indicates on which edge data is sampled.
If it is used, data is sampled on the second edge; otherwise, on the first edge.
|
|
|
In some cases, it is necessary for the master to manage SPI chip select
under software control, so that multiple spi transactions can be performed
without releasing it. A typical use case is variable length SPI packets
where the first spi transaction reads the length and the second spi transaction
reads length bytes.
|
|
|
Maximum clock frequency of device's MIPI interface in Hz
|
|
|
MIPI DBI mode in use. These definitions should match those in
dt-bindings/mipi_dbi/mipi_dbi.h
Legal values: |
|
|
Color coding for MIPI DBI Type A or Type B(6800/8080) interface. These definitions
should match those in dt-bindings/mipi_dbi/mipi_dbi.h
Legal values: |
|
|
MIPI DBI tearing enable signal mode. Defaults to disabled.
Default value: Legal values: |
|
|
GPIO specifier that controls power to the device.
This property should be provided when the device has a dedicated
switch that controls power to the device. The supply state is
entirely the responsibility of the device driver.
Contrast with vin-supply.
|
|
|
Reference to the regulator that controls power to the device.
The referenced devicetree node must have a regulator compatible.
This property should be provided when device power is supplied
by a shared regulator. The supply state is dependent on the
request status of all devices fed by the regulator.
Contrast with supply-gpios. If both properties are provided
then the regulator must be requested before the supply GPIOS is
set to an active state, and the supply GPIOS must be set to an
inactive state before releasing the regulator.
|
Deprecated properties not inherited from the base binding file.
(None)
Properties inherited from the base binding file, which defines common properties that may be set on many nodes. Not all of these may apply to the “ilitek,ili9163c” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
Indicates the operational status of the hardware or other
resource that the node represents. In particular:
- "okay" means the resource is operational and, for example,
can be used by device drivers
- "disabled" means the resource is not operational and the system
should treat it as if it is not present
For details, see "2.3.4 status" in Devicetree Specification v0.4.
Legal values: See Important properties for more information. |
|
|
This property is a list of strings that essentially define what
type of hardware or other resource this devicetree node
represents. Each device driver checks for specific compatible
property values to find the devicetree nodes that represent
resources that the driver should manage.
The recommended format is "vendor,device", The "vendor" part is
an abbreviated name of the vendor. The "device" is usually from
the datasheet.
The compatible property can have multiple values, ordered from
most- to least-specific. Having additional values is useful when the
device is a specific instance of a more general family, to allow the
system to match the most specific driver available.
For details, see "2.3.1 compatible" in Devicetree Specification v0.4.
This property is required. See Important properties for more information. |
|
|
Information used to address the device. The value is specific to
the device (i.e. is different depending on the compatible
property).
The "reg" property is typically a sequence of (address, length) pairs.
Each pair is called a "register block". Values are
conventionally written in hex.
For details, see "2.3.6 reg" in Devicetree Specification v0.4.
See Important properties for more information. |
|
|
Optional names given to each register block in the "reg" property.
For example:
/ {
soc {
#address-cells = <1>;
#size-cells = <1>;
uart@1000 {
reg = <0x1000 0x2000>, <0x3000 0x4000>;
reg-names = "foo", "bar";
};
};
};
The uart@1000 node has two register blocks:
- one with base address 0x1000, size 0x2000, and name "foo"
- another with base address 0x3000, size 0x4000, and name "bar"
|
|
|
Information about interrupts generated by the device, encoded as an array
of one or more interrupt specifiers. The format of the data in this property
varies by where the device appears in the interrupt tree. Devices with the same
"interrupt-parent" will use the same format in their interrupts properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
See Important properties for more information. |
|
|
Extended interrupt specifier for device, used as an alternative to
the "interrupts" property.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Optional names given to each interrupt generated by a device.
The interrupts themselves are defined in either "interrupts" or
"interrupts-extended" properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
If present, this refers to the node which handles interrupts generated
by this device.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Human readable string describing the device. Use of this property is
deprecated except as needed on a case-by-case basis.
For details, see "4.1.2 Miscellaneous Properties" in Devicetree
Specification v0.4.
See Important properties for more information. |
|
|
Information about the device's clock providers. In general, this property
should follow conventions established in the dt-schema binding:
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
|
|
|
Optional names given to each clock provider in the "clocks" property.
|
|
|
This property encodes the number of <u32> cells used by address fields
in "reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
This property encodes the number of <u32> cells used by size fields in
"reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
DMA channel specifiers relevant to the device.
|
|
|
Optional names given to the DMA channel specifiers in the "dmas" property.
|
|
|
IO channel specifiers relevant to the device.
|
|
|
Optional names given to the IO channel specifiers in the "io-channels" property.
|
|
|
Mailbox / IPM channel specifiers relevant to the device.
|
|
|
Optional names given to the mbox specifiers in the "mboxes" property.
|
|
|
Power domain specifiers relevant to the device.
|
|
|
Optional names given to the power domain specifiers in the "power-domains" property.
|
|
|
Number of cells in power-domains property
|
|
|
HW spinlock id relevant to the device.
|
|
|
Optional names given to the hwlock specifiers in the "hwlocks" property.
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|
|
|
Property to identify that a device can be used as wake up source.
When this property is provided a specific flag is set into the
device that tells the system that the device is capable of
wake up the system.
Wake up capable devices are disabled (interruptions will not wake up
the system) by default but they can be enabled at runtime if necessary.
|
|
|
Automatically configure the device for runtime power management after the
init function runs.
|
|
|
List of power states that will disable this device power.
|