On Wed, Aug 19, 2020 at 2:36 PM John Stultz john.stultz@linaro.org wrote:
On Wed, Aug 19, 2020 at 4:46 AM Mauro Carvalho Chehab mchehab+huawei@kernel.org wrote:
So, IMO, the best is to keep it on staging for a while, until those remaining bugs gets solved.
I added this series, together with the regulator driver and a few other patches (including a hack to fix a Kernel 5.8 regression at WiFi ) at:
https://gitlab.freedesktop.org/mchehab_kernel/hikey-970/-/commits/masterSorry, one more small request: Could you create a branch that only has the DRM driver changes in it?
The reason I ask, is that since the HiKey960 isn't affected by the majority of the problems you listed as motivation for going through staging. So if we can validate that your tree works fine on HiKey960, the series can be cleaned up and submitted properly upstream to enable that SoC, and the outstanding 970 issues can be worked out afterwards against mainline.
Just as a heads up, I tried testing your tree with my HiKey960, and after fixing the compat string inconsistency, the drivers seem to load properly. However the drm_hwcomposer seems to have some trouble with the driver: 01-01 00:12:41.456 345 345 E hwc-drm-display-compositor: Commit test failed for display 0, FIXME 01-01 00:12:41.456 345 345 E hwc-drm-two: Failed to apply the frame composition ret=-22 01-01 00:12:41.456 351 351 E HWComposer: presentAndGetReleaseFences: present failed for display 0: BadParameter (4)
I'll dig in a bit further as to why, but wanted to give you a heads up.
thanks -john