On Mon, Nov 8, 2021 at 3:13 PM Daniel Baluta daniel.baluta@nxp.com wrote:
On 11/8/21 3:39 PM, Pierre-Louis Bossart wrote:
On 11/8/21 5:11 AM, Arnd Bergmann wrote:
From: Arnd Bergmann arnd@arndb.de
Fixes: 858f7a5c45ca ("ASoC: SOF: Introduce fragment elapsed notification API") Signed-off-by: Arnd Bergmann arnd@arndb.de
It's Monday morning and my memory is still foggy but I think we fixed this problem with https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com..., where we changed the Kconfigs for i.MX. We haven't sent this update upstream for some reason.
Arnd, can you share the configuration that breaks with the existing upstream code, I can check if the problem still exists.
Maybe someone forgot :) to send https://github.com/thesofproject/linux/pull/3180/commits/7122edc88d13db8ba83... upstream.
I think that's me.
Arnd can you run your scripts with https://github.com/thesofproject/linux/pull/3180/commits/7122edc88d13db8ba83.... I also attached the patch
I added that to my randconfig tree now. I did a cherry-pick of that commit, I tried a 'git merge' first, but that pulled in a lot of other stuff that conflicts with linux-next.
Your patch does not fix the link error though, I'm fairly sure we need my one-liner on top still. In this case, SND_SOC_SOF=y gets selected by SND_SOC_SOF_INTEL_COMMON=y, while SND_SOC_SOF_COMPRESS=m gets selected by SND_SOC_SOF_IMX_COMMON=m, and then ignored because the Makefile only cares about =y objects built into the common module.
Arnd