adi,adv7535 (on i2c bus)
Description
Analog Devices ADV7535 MIPI DSI to HDMI bridge
The ADV7535 is an I2C-controlled bridge that converts MIPI DSI video to HDMI.
The MIPI DSI endpoint is represented separately as a child of the MIPI DSI host.
Examples
#include <zephyr/dt-bindings/mipi_dsi/mipi_dsi.h>
i2c {
#address-cells = <1>;
#size-cells = <0>;
display-bridge@39 {
compatible = "adi,adv7535";
reg = <0x39>;
pd-gpios = <&gpio0 0 GPIO_ACTIVE_HIGH>;
int-gpios = <&gpio0 1 GPIO_ACTIVE_LOW>;
dsi-device = <&adv7535_dsi>;
/* Optional I2C addresses, if omitted defaults are used */
adi,edid-addr = <0x3f>;
adi,packet-addr = <0x38>;
adi,cec-addr = <0x3c>;
adi,fixed-addr = <0x00>;
};
};
mipi_dsi: mipi-dsi@40000000 {
compatible = "vnd,mipi-dsi-host";
reg = <0x40000000 0x1000>;
#address-cells = <1>;
#size-cells = <0>;
adv7535_dsi: display-bridge@0 {
compatible = "adi,adv7535-dsi";
reg = <0>;
data-lanes = <4>;
pixel-format = <MIPI_DSI_PIXFMT_RGB888>;
display-timing = <&hdmi_timing>;
/* test-pattern = <0>; */
};
};
display-controller {
width = <1920>;
height = <1080>;
hdmi_timing: display-timings {
compatible = "zephyr,panel-timing";
clock-frequency = <148500000>;
hsync-len = <44>;
hfront-porch = <88>;
hback-porch = <148>;
vsync-len = <5>;
vfront-porch = <4>;
vback-porch = <36>;
hsync-active = <1>;
vsync-active = <1>;
de-active = <1>;
pixelclk-active = <1>;
};
};
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
Optional EDID I2C address. Default is the power-on reset value of the register.
Default value: |
|
|
Optional packet I2C address. Default is the power-on reset value of the register.
Default value: |
|
|
Optional CEC I2C address. Default is the power-on reset value of the register.
Default value: |
|
|
This should be set to a non-conflicting I2C address.
Default is the power-on reset value of the register.
Default value: |
|
|
Auxiliary adi,adv7535-dsi node describing the DSI link of this
bridge. It is a child of the MIPI DSI host the bridge is wired to.
This property is required. |
|
|
GPIO connected to the PD/AD power-down pin. The pin level when the
ADV7535 power supplies are applied selects both the main I2C address and
the power-down polarity. A low level selects address 0x39 and active-high
power-down, while a high level selects address 0x3d and active-low
power-down. The GPIO flags must match the selected power-down polarity.
Although this GPIO is optional, connecting it is strongly recommended
because toggling the PD/AD pin resets more registers than a
register-based reset. The I2C address and power-down polarity are sampled
when power is applied. To change either setting, set the pin to the
desired level and power-cycle the board.
|
|
|
Interrupt pin of ADV7535. Must be configured as active-low and pulled up.
This property is required. |
|
|
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 “adi,adv7535” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
Main register map I2C address. The address is 0x39 when PD/AD is pulled
low and 0x3d when PD/AD is pulled high as power is applied.
This property is required. Legal values: See Important properties for more information. |
|
|
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. |
|
|
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 used to define a mapping (or translation) between the address
space of a bus (the "child address space") and the address space of the
bus node's parent (the "parent address space").
The "ranges" property is typically empty, or a sequence of triplets
(child bus address, parent bus address, length).
If the "ranges" property is empty, it specifies that the parent and child
address spaces are identical and no address translation is required.
If the "ranges" property is not present in a bus node, it is assumed that
no mapping exists between children of the node and the parent address space.
For details, see "2.3.8 ranges" in Devicetree Specification v0.4.
|
|
|
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.
|
|
|
Indicates that the device is capable of coherent DMA operations.
For details, see "2.3.10 dma-coherent" in Devicetree Specification v0.4.
|
|
|
DMA channel specifiers relevant to the device.
|
|
|
Optional names given to the DMA channel specifiers in the "dmas" property.
|
|
|
The dma-ranges provides a means of defining a mapping or translation between the
physical address space of the bus and the physical address space of the parent of the bus.
For details, see "2.3.9 dma-ranges" in Devicetree Specification v0.4.
|
|
|
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.
|