dc55ac3b52
Add very basic ti-tfp410 DVI transmitter driver. The only feature separating this from a completely dummy bridge is the EDID read support trough DDC I2C. Even that functionality should be in a separate generic connector driver. However, because of missing DRM infrastructure support the connector is implemented within the bridge driver. Some tfp410 HW specific features may be added later if needed, because there is a set of registers behind i2c if it is connected. This implementation is tested against my new tilcdc bridge support and it works with BeagleBone DVI-D Cape Rev A3. A DT binding document is also updated. Signed-off-by: Jyri Sarha <jsarha@ti.com> Acked-by: Rob Herring <robh@kernel.org>
47 lines
852 B
Plaintext
47 lines
852 B
Plaintext
TFP410 DPI to DVI encoder
|
|
=========================
|
|
|
|
Required properties:
|
|
- compatible: "ti,tfp410"
|
|
|
|
Optional properties:
|
|
- powerdown-gpios: power-down gpio
|
|
- reg: I2C address. If and only if present the device node
|
|
should be placed into the i2c controller node where the
|
|
tfp410 i2c is connected to.
|
|
|
|
Required nodes:
|
|
- Video port 0 for DPI input [1].
|
|
- Video port 1 for DVI output [1].
|
|
|
|
[1]: Documentation/devicetree/bindings/media/video-interfaces.txt
|
|
|
|
Example
|
|
-------
|
|
|
|
tfp410: encoder@0 {
|
|
compatible = "ti,tfp410";
|
|
powerdown-gpios = <&twl_gpio 2 GPIO_ACTIVE_LOW>;
|
|
|
|
ports {
|
|
#address-cells = <1>;
|
|
#size-cells = <0>;
|
|
|
|
port@0 {
|
|
reg = <0>;
|
|
|
|
tfp410_in: endpoint@0 {
|
|
remote-endpoint = <&dpi_out>;
|
|
};
|
|
};
|
|
|
|
port@1 {
|
|
reg = <1>;
|
|
|
|
tfp410_out: endpoint@0 {
|
|
remote-endpoint = <&dvi_connector_in>;
|
|
};
|
|
};
|
|
};
|
|
};
|