If we apply the [1], it will make users easily reproduce the [2], that is why kernel maintainer reverted the [1].
I thought I backport the [2] to the kernel first, then backport [1] to the kernel, I tried to backport the [2] to the osp1 kernel myself, but it didn't work at all, so I asked for help to Intel, they estimated a couple of days then tell me it is not easy and they will not help backport the [2] to 5.0 and 5.3, and without [1], the dmic function will not be affected.
Because this bug will not affect the dmic function, just lower the priority, when I finish the more urgent bug, I will spend more time investigating backport [2], then resend the patch [1].
@ Rex,
If we apply the [1], it will make users easily reproduce the [2], that is why kernel maintainer reverted the [1].
I thought I backport the [2] to the kernel first, then backport [1] to the kernel, I tried to backport the [2] to the osp1 kernel myself, but it didn't work at all, so I asked for help to Intel, they estimated a couple of days then tell me it is not easy and they will not help backport the [2] to 5.0 and 5.3, and without [1], the dmic function will not be affected.
About the linux-firmware, already sru them to Eoan and Bionic with this bug: https:/ /bugs.launchpad .net/ubuntu/ +source/ linux-firmware/ +bug/1859387, the firmware under Eoan and Bionic can support the kernel both with [1] and without [1].
Because this bug will not affect the dmic function, just lower the priority, when I finish the more urgent bug, I will spend more time investigating backport [2], then resend the patch [1].