From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Fabio Aiuto <fabioaiuto83@gmail.com>
Cc: tiwai@suse.com, perex@perex.cz, broonie@kernel.org,
lgirdwood@gmail.com, Hans de Goede <hdegoede@redhat.com>,
gregkh@linuxfoundation.org, alsa-devel@alsa-project.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: config issue with SoundWire mockup device support
Date: Thu, 2 Sep 2021 10:02:05 -0500 [thread overview]
Message-ID: <10bb39d4-2560-4ceb-bf20-fe5a124142cb@linux.intel.com> (raw)
In-Reply-To: <20210902143632.GA1422@agape.jhs>
On 9/2/21 9:36 AM, Fabio Aiuto wrote:
> Dear Pierre and all sound developers,
>
> I work for some tests on a Lenovo ideapad Miix 300-10IBY,
> with fedora 34 workstation intalled on.
> After having pulled the last changes from staging tree I get
> the following issue by typing:
>
> $ make olddefconfig
>
> WARNING: unmet direct dependencies detected for SND_SOC_SDW_MOCKUP
> Depends on [n]: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
> && EXPERT [=n] && SOUNDWIRE [=y]
> Selected by [m]:
> - SND_SOC_INTEL_SOUNDWIRE_SOF_MACH [=m] && SOUND [=m] && !UML
> && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y]
> && SND_SOC_SOF_INTEL_SOUNDWIRE [=m] && I2C [=y] && ACPI [=y]
> && GPIOLIB [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n])
> && (SND_SOC_INTEL_USER_FRIENDLY_LONG_NAMES [=y] || COMPILE_TEST [=n])
> && SOUNDWIRE [=y] && SND_HDA_CODEC_HDMI [=m] && SND_SOC_SOF_HDA_AUDIO_CODEC [=y]
It's a known issue that was reported and fixed by Nathan Chancellor:
[PATCH v2] ASoC: Intel: boards: Fix CONFIG_SND_SOC_SDW_MOCKUP select
https://lore.kernel.org/alsa-devel/20210802212409.3207648-1-nathan@kernel.org/
I'll ack the missing patch, thanks for reporting this.
next prev parent reply other threads:[~2021-09-02 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 14:36 config issue with SoundWire mockup device support Fabio Aiuto
2021-09-02 15:02 ` Pierre-Louis Bossart [this message]
2021-09-02 15:16 ` Fabio Aiuto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10bb39d4-2560-4ceb-bf20-fe5a124142cb@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fabioaiuto83@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox