[mk01]

@CurlyMo

you are kicking wrong grave there.
I really don't feel like Encyclopedia Britannica to repeat the same over and over again or to explain simple consequences A -> B -> C. You showed many times before ability to Read and Study so maybe this should be followed most time before rushing bugs and BUGS.

Specially for you I wrote:

Code:

because of various things (for instance HDMI/nHDMI problems of HW signals and HW design - tiny things with huge impacts)

Three of your BUGS are simply consequence of that. How the FB driver is initialised, clocks started and stopped, pins handled and IRQs/events being generated.
I will not go into details because anyhow you are not interested. Otherwise this brave discussion about Bugs(B) would not be there.
You got the device for free as a community developer so don't ask the community when the functionality will be delivered to YOU.

You can rebase my work (my repo, imx6 kernel, DVI branch) which was even part of standard XBian Cubox-i kernel and looked promising. I stopped on DVI events test (as I don't have real DVI device - only HDMI with DVI port and that is pushing HDMI edid to it so my testing would be not conclusive for FSCs FB HDMI implementation) and another developer told me he has completely different and more straight forward solution - that happened maybe 6-8w ago. That code is not 100% perfect - at kernel level there are some overflow events - but not affecting userspace. Despite that it was miles ahead of current (stable) status of the kernel.

Feel free to continue. There are many options how-to also on another ©Bugs(with a capital B) front.
1) be checking FSC development (don't take it as main source tree with fixing needed - it mostly even don't boot at all - but you can find some working parts there and try to backport / rebase
2) follow upstream (vanilla) imx6 fixes/changes/development. I told you yesterday most of DTB code and stuff is pushed there. So find the right patches and backport - this could be targeted to GPIO, Radios(BT/WIFI), SDHCI and maybe others.

I did great part of CMA from 3.14 and have in testing kernel/irq parts backporting to allow newer drivers to run (for instance things around DRM). There are so many ways how to show your anticipation.