Hi, On Mon, Aug 22, 2022 at 11:23 PM Yongqin Liu <yongqin.liu@xxxxxxxxxx> wrote: > > Hi, Douglas > > Just an update on the fix you pointed out previously here: > > > [1] https://lore.kernel.org/r/20220809142738.1.I91625242f137c707bb345c51c80c5ecee02eeff3@changeid > > With it I could boot the hikey960 build to the home screen if it does > not use the GKI kernel. > but the problem will be reproduced if it uses the GKI kernel. > > And if this change is reverted, then it could boot with the GKI kernel as well. > > I am not sure what's the reason there, but there seems to be some > difference with the fix above and the workaround of revert. > Not sure if you have any idea about that. > > Regarding the GKI kernel(Android Generic Kernel Image)[2], it's built > from the android-mainline tree(f51334eac4de) without any workaround. > (Neither the revert, nor the fix applied), and the regulator modules > used for the hikey960 build are hi6421v530-regulator.ko and > hi655x-regulator.ko > > I am still not sure if it would work with the GKI kernel that has the > fix that you pointed out in. the case that both the GKI kernel and > vendor tree have the fix. > Will update here when I have some results. > > [2]: https://source.android.com/docs/core/architecture/kernel/generic-kernel-image?hl=en That's not too surprising. The broken patch is in the core kernel so you need the fix in the core kernel. I think that means you'll have to wait until `android-mainline` gets the fix. I don't work on Android, so if there's some other route to get an expedited fix into android-mainline I'm not aware of it. -Doug -Doug
