1366x768 HDMI resolution in toradex imx6q

We are using the same 15.6 display mentioned in the below post with Toradex imx6Q Apalis SOM but we have ported Android 7.1.2 to it

  1. We have enabled local EDID patch as mentioned - new driver and dts file changes

  2. We have configured 1366x768 as resolution in the hdmi driver // Tried with 1360x768 as well. Could you please suggest which is the better tool to get the display parameters to be filled for this resolution in the driver

  3. We made sure the bootargs are fine - video=mxcfb0:dev=hdmi,1366x768M@60,if=RGB24 //did try with rgb16 as well as rgb32

Are we missing anything here - which stops us in quickly validating this 15.6 display with Toradex imx6Q

Please help us get over this issue

I decoded the edid in the dts file which is 31cm and 17cm long display - is this edid generated using standard tools for the resolution or its display specific for that display

Thanks
Harish

Hi

  • Note that we do not provide support for Android. I do not know if Android uses the resolution that we set in the kernel or it tries to do some Android user space magic.
  • What version of the kernel did you base on?
  • Did you recompile kernel and device tree and then actually deploy it to the target?
  • Does the sysfs edid file exist? Does it contain the data you did set in the device tree?
  • How did the display provider answer your report that his EDID is broken?

I decoded the edid in the dts file which is 31cm and 17cm long display - is this edid generated using standard tools for the resolution or its display specific for that display

Note that EDID in the proposed device tree change has only a fixed ‘header pattern’ and ‘checksum’. No change to the data was done.

Max

Hi Max,
We have tried the same in Linux and we are getting some portion of display (1/4th of the 15.6" display) coming only for 1280x720 resolution

Linux kernel used is 4.9.11-76578-g26c437b53516-dirty
video=mxcfb0:dev=hdmi,1360x768M@60,if=RGB32
fbmem=32M tried 8M as well

Getting the EDID set in the device tree in the sysfs
0x00 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x00 0x06 0xAF 0x3C 0x10 0x00 0x00 0x00 0x00
0x00 0x16 0x01 0x04 0x90 0x1F 0x11 0x78 0x02 0x10 0xB5 0x97 0x58 0x57 0x92 0x26
0x00 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01
0x01 0x01 0x01 0x01 0x01 0x01 0xCE 0x1D 0x56 0xD2 0x50 0x00 0x26 0x30 0x10 0x10
0x3E 0x00 0x35 0xAD 0x10 0x00 0x00 0x18 0xDF 0x13 0x56 0xD2 0x50 0x00 0x26 0x30
0x10 0x10 0x3E 0x00 0x35 0xAD 0x10 0x00 0x00 0x18 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x02
0x00 0x0C 0x39 0xCC 0x0D 0x3C 0x64 0x0F 0x0C 0x1B 0x6F 0x20 0x20 0x20 0x00 0xD8

Attached the log file with the parameters you have asked for in the previous post for each resolution

link text

Thanks for the response Max. 4.1.44-2.7.4+gb1555bf is the kernel version we are using it for Android.

Though there are no differences it brings in android user space we can still quickly test the same in Linux and update you

Could you pls provide complete file mentioned in your device tree patches - since we are using different version of kernels just wanted to make it clear (patch gives slight doubts during manual patching for other revision of kernel)

Thanks
Redwan

Hi

Do NOT use mxc_hdmi.only_cea=1. Either leave the parameter away or set it to 0. With this you ask to only use CEA resolutions, i.e. to not use 1366x768.

Do use if=RGB24.

The used EDID only specifies timings for 1366x768 resolution. So you cannot simply ask for 1360x768 and expect that it just works.
So first make 1366x768 work with Linux. If Android has an issue to work on that resolution then you could try to create a working EDID with 1360x768.

Max

We have evaluated it in Linux and then Android as well successfully . Thanks Max