renesas,smartbond-mipi-dbi
Vendor: Renesas Electronics Corporation
Note
An implementation of a driver matching this compatible is available in drivers/mipi_dbi/mipi_dbi_smartbond.c.
Description
These nodes are “mipi-dbi” bus nodes.
Renesas Smartbond(tm) MIPI DBI Host
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
---|---|---|
|
|
Clock frequency of the SCL signal of the MBI-DBI peripheral, in Hz
|
|
|
Pin configuration/s for the first state. Content is specific to the
selected pin controller driver implementation.
|
|
|
Pin configuration/s for the second state. See pinctrl-0.
|
|
|
Pin configuration/s for the third state. See pinctrl-0.
|
|
|
Pin configuration/s for the fourth state. See pinctrl-0.
|
|
|
Pin configuration/s for the fifth state. See pinctrl-0.
|
|
|
Names for the provided states. The number of names needs to match the
number of states.
|
|
|
Reset GPIO pin. Used to reset the display during initialization.
|
|
|
Boolean to indicate whether the tearing effect (TE) signal is available or not.
|
|
|
Boolean to apply an inversion on the TE signal that triggers the MIPI DBI controller.
|
|
|
Host controller will wait for at least the specified number of bytes before triggering
a single frame update. The prefetch mechanism should be enabled when frame buffer(s)
is stored into external storage mediums, e.g. PSRAM, that introduce comparable delays.
In such a case it might case that the controller runs into underrun conditions which
results in correpting the whole frame update. It's user's responsibility to ensure that
the selected value does not exceed frame's total size as otherwise the controller will
not be able to trigger the frame update.
Legal values: |
|
|
SPI bus to use for display read operations. When this property is present, MIPI DBI read
operations will be exhibited by the driver. This is because, the LCDC IP block does not
support read functionality, natively.
|
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 “renesas,smartbond-mipi-dbi” compatible.
Name |
Type |
Details |
---|---|---|
|
|
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.
|
|
|
indicates the operational status of a device
Legal values: See Important properties for more information. |
|
|
compatible strings
This property is required. See Important properties for more information. |
|
|
register space
This property is required. See Important properties for more information. |
|
|
name of each register space
|
|
|
interrupts for device
This property is required. See Important properties for more information. |
|
|
extended interrupt specifier for device
|
|
|
name of each interrupt
|
|
|
phandle to interrupt controller node
|
|
|
Human readable string describing the device (used as device_get_binding() argument)
See Important properties for more information. This property is deprecated. |
|
|
Clock gate information
|
|
|
name of each clock
|
|
|
number of address cells in reg property
This property is required. Constant value: |
|
|
number of size cells in reg property
This property is required. |
|
|
DMA channels specifiers
|
|
|
Provided names of DMA channel specifiers
|
|
|
IO channels specifiers
|
|
|
Provided names of IO channel specifiers
|
|
|
mailbox / IPM channels specifiers
|
|
|
Provided names of mailbox / IPM channel specifiers
|
|
|
Power domain specifiers
|
|
|
Provided names of power domain specifiers
|
|
|
Number of cells in power-domains property
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|