[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D5657B8E8DB8995E+aPt-p1EXhoFLm9aW@troy-wujie14pro-arch>
Date: Fri, 24 Oct 2025 21:27:03 +0800
From: Troy Mitchell <troy.mitchell@...ux.spacemit.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>
Cc: Jinmei Wei <weijinmei@...ux.spacemit.com>,
Troy Mitchell <troy.mitchell@...ux.spacemit.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the sound-asoc tree
On Wed, Oct 22, 2025 at 02:17:05PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the sound-asoc tree, today's linux-next build (powercp
> allyesconfig) produced this warning:
>
> WARNING: unmet direct dependencies detected for DMA_CMA
> Depends on [n]: HAVE_DMA_CONTIGUOUS [=n] && CMA [=y]
> Selected by [y]:
> - SND_SOC_K1_I2S [=y] && SOUND [=y] && SND [=y] && SND_SOC [=y] && (COMPILE_TEST [=y] || ARCH_SPACEMIT) && HAVE_CLK [=y]
>
> Probably introduced by commit
>
> fce217449075 ("ASoC: spacemit: add i2s support for K1 SoC")
Sorry, I didn't realize that this email ended up in my spam folder,
and I just saw it today.
I am considering directly selecting `HAVE_DMA_CONTIGUOUS`,
but another possibility is to make it depend on `DMA_CMA`.
Can anyone advise which approach would be better?
If there are no objections, I plan to send a patch on Monday:
select `HAVE_DMA_CONTIGUOUS`
- Troy
>
> --
> Cheers,
> Stephen Rothwell
Powered by blists - more mailing lists