From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: Re: Bad rever-select of CONFIG_SND_HDA_I915
Date: Fri, 18 Mar 2016 16:24:07 +0530 [thread overview]
Message-ID: <20160318105407.GJ2490@localhost> (raw)
In-Reply-To: <s5hfuvo5b3x.wl-tiwai@suse.de>
On Fri, Mar 18, 2016 at 11:33:38AM +0100, Takashi Iwai wrote:
> On Fri, 18 Mar 2016 11:28:06 +0100,
> Vinod Koul wrote:
> >
> > On Fri, Mar 18, 2016 at 10:22:45AM +0100, Takashi Iwai wrote:
> > > On Fri, 18 Mar 2016 09:06:49 +0100,
> > > Vinod Koul wrote:
> > > >
> > > > On Fri, Mar 18, 2016 at 08:34:49AM +0100, Takashi Iwai wrote:
> > > > > Hi,
> > > > >
> > > > > while build testing, I noticed the following warning:
> > > > > warning: (SND_SOC_INTEL_SKYLAKE) selects SND_HDA_I915 which has unmet direct dependencies (SOUND && !M68K && !UML && SND && DRM_I915 && SND_HDA_CORE)
> > > >
> > > > Thanks Takashi for reporting,
> > > >
> > > > > And it's indeed broken: you can't select CONFIG_SND_HDA_I915 from the
> > > > > driver side. This is the condition depending on DRM i915 driver.
> > > >
> > > > But who selects CONFIG_SND_HDA_I915. It is a bool symbol, so someone needs
> > > > to select it. I didn't see anyone select it, either from Gfx side or HDA
> > > > side?
> > >
> > > No, it's not a kconfig to be selected manually by others, but it
> > > adjusts itself automatically depending on DRM_I915. That is, it's a
> > > read-only value.
> >
> > Okay then
> >
> > > > > Fixing this doesn't look too trivial, though. Since
> > > > > SND_SOC_INTEL_SKYLAKE is the item to be selected, it can't have
> > > > > "depends on". So, the top-level configs that select
> > > > > SND_SOC_INTEL_SKYLAKE need to have "depends on DRM_I915" lines, or
> > > > > modify the driver to be built without i915 binding.
> > > >
> > > > can you please share the config where you saw this...
> > >
> > > Just set DRM_I915=n and run config again on your machine.
> >
> > Yes saw this now. I made depends on DRM_I915 to make it disappear.
>
> OTOH, this makes impossible to use the driver without graphics, even
> if you want only Realtek codec.
>
> > I will check again for compilation fix and get back on proper patch either
> > which depends on DRM or ensure we compile clean
>
> I guess the build failure won't happen even if you rip off
> SND_HDA_I915 dependency from SND_SOC_INTEL_SKYLAKE. Let's check.
It doesn't. So both work well :)
Depends on DRM_I915 as well as removing current select.
FWIW, the removing the DRM will not work as HDMI will fail so dailinks wont
be there and sound card will not get registered :)
So which one to do in above?
--
~Vinod
next prev parent reply other threads:[~2016-03-18 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 7:34 Bad rever-select of CONFIG_SND_HDA_I915 Takashi Iwai
2016-03-18 8:06 ` Vinod Koul
2016-03-18 9:22 ` Takashi Iwai
2016-03-18 10:28 ` Vinod Koul
2016-03-18 10:33 ` Takashi Iwai
2016-03-18 10:54 ` Vinod Koul [this message]
2016-03-18 11:23 ` Takashi Iwai
2016-03-18 14:41 ` Vinod Koul
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=20160318105407.GJ2490@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).