Nikita Travkin
Nikita Travkin
I believe those devices have multi-sourced touchscreens, in which case it's non-trivial for lk2nd to detect which specific touchscreen is there. One could probably write a fixup driver and try...
Hi! Consider using msm8952 target: https://github.com/msm8916-mainline/lk2nd/tree/main/lk2nd/device/dts/msm8952
You're always free to ask questions in the chat https://github.com/msm8916-mainline/lk2nd/blob/main/README.md?plain=1#L92
> Or are these SoCs so similar that they're sharing lk2nd binary? Exactly. `lk2nd-msm8952` is a build target based on caf `msm8952` build target, which is compatible with multiple "similar...
Hi! This device probably have non-standard keys pins and it was never added to lk2nd, so lk2nd doesn't know how to handle it. You will need to add a node...
I've picked all of this up in `wip/msm8916/6.11-rc5` with an exception of the revert commit, not sure about that one being correct upstreamable fix yet... Thanks!
Hi! > How Can We Adapt lk2nd for MTK Unfortunately lk2nd project is /very/ qcom-centric and uses/relies on a significant amount of CAF code from old qcom's lk. This means...
Hi! I'd not be surprised if different firmware versions of the touch handle stuff slightly differently. You're probably best off duplicating this as a response to the patch you've mentioned...
> slbounce must be compiled with make SLBOUNCE_ALWAYS_SWITCH=1, without this flag it didn't boot FWIW new slbounce heuristic only allows el2 if zap-shader exists and explicitly disabled (which is a...
Applied this in `wip/msm8916/6.11-rc5`, thanks!