I’m trying to figure out the linkage between the dtb “display-timings” entries and enabling them via uboot and/or the kernel. We have a display we’ve been using on a different platform and I’d like to test it out using the colibri eval board (with imx7d installed) before we go making interface boards. It doesn’t match any of the entries in the imx7-colibri.dtsi file, so I need to add another (the max clock is only 15M for our board). I can just change the native mode to point to the new entry, but it would sure be great if I could just set a uboot var (vidargs/videomode), or even change the mode via some sort of sysfs write (fb modes/fbset?) We’ve got it wired up on the breakout connector.
Inside of imx7d-colibri.dtsi exists a few “display-timings” entries, which seem to be selected using the “native-mode” entry. It seems strange to have to change the native-mode entry and either recompile the device tree and load or do some sort of uboot magic to change the dtb to activate the different display-timings. Is there a way to select one using a uboot variable and/or something else via the kernel command line? I’ve got a couple of different displays I’m testing, and it would be nice to simply change to them. Here’s a snippet from that file:
Thanks…I’ve read that one a bunch of times. The line in there that says:
To support a specific display we recommend using the device tree to specify the exact display resolution and timings while also specifying the native-modeproperty. See the carrier board device tree file, e.g.arch/arm/boot/dts/imx7-colibri-eval-v3.dtsi`
Is what I do to get my display operational. Anyhow, just thought there was some sort of use of those different timing blocks in a simple fashion, but it doesn’t seem so. Once my display is all working, I’ll just have that one in the device tree anyhow, so it’s all good.