A320 hangs on 4.12rc1 and up

[freedreno-zz]

A320 hangs on 4.12rc1 and up

[robclark]

My suspicion is that maybe the iommu dma-ops are getting wired up after these patches, making msm_gem.c's use of dma_{map,unmap}_sg() cause unintended iommu map/unmap conflicting with our management of the iova space.. I haven't had time yet to look again at 8064, but it is on my todo list

[montvid]

The problem persists in 4.14.14. I can boot the device no problem but the gpu throws the same errors when trying to load a GUI. We at postmarketos are trying to use your freedreno driver to run KDE Plasma Mobile, LuneOS and other Linux GUI's like XFCE4, MATE on older phones and a lot of them use A3** gpu so we depend on you and your freedreno driver support. As I said before 4.11.12 is the last kernel everything was working. Well I am glad I can use that.

[robclark]

sorry that I haven't had time to look at ifc6410 yet.. although if the issue is what I think it is (with the iommu) it should at least be restricted to the msm_iommu+mdp4+a3xx combo (so wouldn't apply to anything 8x74 and later).. so basically it would only be 8064.

I guess if the older kernel is working, sticking with that is a reasonable short-term solution.

[robclark]

"freedreno" is mainly the userspace part.. it normally uses upstream drm/msm kernel module. There is some support for an ancient downstream kgsl kernel driver, but it is nearly impossible to support all the different versions of the downstream kgsl driver on various/random android kernel branches. Most of my development work focuses on community boards (ifc6540/db410c/db820c/etc) since they are easier to work with.

For folks who want to use freedreno on phones/tablets, especially devices w/ SoC's that have reasonable support upstream, I tend to encourage getting an upstream kernel working. The downside is low level bring-up work, in terms of digging thru downstream kernel and converting things to upstream DT bindings.. plus writing a dsi panel driver. The upside is that old kgsl kernel support was a complete hack and pretty fragile.

The good news is qcom seems to move closer to upstream drivers (clk/genpd/etc) in newer things so hopefully this problem goes away eventually ;-)

[okias]

Any progress on that? Also having issues with Nexus 7 2013 flo (kernel 5.6-rc4-next)

[1] https://github.com/apq8064-mainline/linux/commits/qcom-apq8064-next