ADV7511w : what will be the 'dts' file changes for am437x

Hello community,

Myself is using ADV7511W transmitter for HDMI connection. For this I am bit stuck and not able to figure-out to what changes should be done in the dts files to make this work.

Also, myself is using below snippet mentioned as example at path Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt  in kernel-source-tree to which I am getting the error. 

Request your assistance on this


adv7511w: hdmi@39 {
compatible = "adi,adv7511w";
reg = <39>;
interrupt-parent = <&gpio3>;
interrupts = <29 IRQ_TYPE_EDGE_FALLING>;

adi,input-depth = <8>;
adi,input-colorspace = "rgb";
adi,input-clock = "1x";
adi,input-style = <1>;
adi,input-justification = "evenly";

ports {
#address-cells = <1>;
#size-cells = <0>;

port@0 {
reg = <0>;
adv7511w_in: endpoint {
remote-endpoint = <&dpi_out>;

port@1 {
reg = <1>;
adv7511_out: endpoint {
remote-endpoint = <&hdmi_connector_in>;

Parents Reply
  • 0
    •  Analog Employees 
    on Nov 4, 2020 1:37 PM in reply to arg


    Because you used adi,input-colorspace = "rgb" properties adi,input-style = <1>; adi,input-justification = "evenly"; are ignored and set to default value. But that's not a problem. Have a look here.

    Just make sure that the output color space is RGB.

    Now can you please describe in more detail what's the problem? Is the driver probed? Can you read from sysfs the HDMI connected monitor EDID?



  • I am not seeing the device/driver in the file system after boot. Also I have built the module as builtin module as per the 

    Linux Kernel Configuration
    	Device Drivers  --->
    		Graphics support  --->  
    			<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)  ---> 
    			<*> AV7511 encoder

    Also the HDMI connector is connected to the device

    Please let me know if there are any more kernel configurations has to be modified for the same
  • 0
    •  Analog Employees 
    on Nov 9, 2020 7:19 AM in reply to arg

    Can you please check that input endpoint is correctly connected up to DSS?

    Can you also attach here the whole .DTB file that you are using to boot the system?

    If you see nothing on /sys/class/drm/ then incorrect devicetree mapping could be a cause

  • Hi,

    At this point of time I am not sure if I can share the dtb, because of privacy reasons , however I have attached the dts files above in my replies

    Scenario : I am compiling the kernel and dtb locally and replaced both in the target-device's file system


    1. I am not able to see anything in /sys/class/drm/

    2. Also can you share the some example 'dts' file to map endpoint to dss OR can you help on the existing ones which I have attached in previous replies in this thread

    3. While running insmod adv7511.ko it says "resource is busy" and I am not sure why this message since I am not able to see anything in /sys/class/drm/ 

  • 0
    •  Analog Employees 
    on Nov 11, 2020 7:49 AM in reply to arg


    For obvious reasons we don't have examples exactly for am437x CPU from TI but you can check for example our tested and functional implementation with adv7511 presented here.

    Please try command lsmod to check if adv7511 driver is not already probed.

    And also check DMESG for entries related to adv7511 and drm. Maybe there are some errors there.