mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Vinod Koul <vinod.koul@intel.com>,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	alsa-devel@alsa-project.org
Subject: Re: [GIT PULL] sound updates for 4.15-rc1
Date: Thu, 16 Nov 2017 16:10:25 +0100	[thread overview]
Message-ID: <s5hy3n61cpq.wl-tiwai@suse.de> (raw)
In-Reply-To: <8bcf9060-92b9-8058-cdee-4a222e796b3e@linux.intel.com>

On Thu, 16 Nov 2017 15:55:35 +0100,
Pierre-Louis Bossart wrote:
> 
> On 11/15/17 1:34 AM, Takashi Iwai wrote:
> > [Adding more people and alsa-devel to Cc]
> >
> > On Wed, 15 Nov 2017 03:40:09 +0100,
> > Linus Torvalds wrote:
> >>
> >> On Tue, Nov 14, 2017 at 6:51 AM, Takashi Iwai <tiwai@suse.de> wrote:
> >>>
> >>> please pull sound updates for v4.15-rc1 from:
> >>
> >> Hmm. Making "oldconfig" on my laptop with this, my
> >> SND_SOC_INTEL_SKYLAKE went away.
> >>
> >> And the reason seems to be that new SND_SOC_INTEL_SST_TOPLEVEL config option.
> >>
> >> Which has no help associated with it.
> >>
> >> This is not a friendly thing to do to people. It basically breaks
> >> existing setups for no documented reason, and with no explanation.
> >>
> >> Please fix the config situation. At the very least, add documentation.
> >
> > Sorry about that.  I saw Vinod already submitted a patch to add the
> > help text to CONFIG_SND_SOC_INTEL_SST_TOPLEVEL, so the least fix
> > should go in soon.
> >
> > But now looking at these changes, I noticed a few things, too:
> >
> > - With the introduction of SND_SOC_INTEL_SST_TOPLEVEL, keeping
> >    SND_SOC_INTEL_COMMON and SND_SOC_INTEL_MACH individually doesn't
> >    make much sense.  They can be dropped and replaced with
> >    SND_SOC_INTEL_SST_TOPLEVEL as a further cleanup.
> >
> > - ... or, make SND_SOC_INTEL_SST_TOPLEVEL=y as default, if this is
> >    considered to be a top-level filter config (like the network vendor
> >    kconfig items).  In that case, the reverse-selection of
> >    SND_SOC_INTEL_COMMON and SND_SOC_INTEL_MACH should be avoided, but
> >    they should be selected from the actual drivers instead.
> 
> This level was introduced as a shortcut to help select the platform
> drivers associated with the closed-source audio firmware.
> There will be a follow-up set of patches coming soon, and we'll need
> to have the corresponding top-level selector for the drivers handling
> the open-source audio firmware. Please don't make too many assumptions
> on this SND_SOC_INTEL_SST_TOPLEVEL, it is not going to be true for
> everyone moving forward.

OK, but *before* moving to that direction, please fix the current mess
at first.  If CONFIG_SND_SOC_INTEL_SST_TOPLEVEL is the entry to filter
the Intel ASoC drivers, it should be the one with default=y and
doesn't select / enable others as itself.  OTOH, if some explicit
selection by user becomes mandatory while it wasn't, it's already a
bad step.

> If you want look at the Kconfig setup, the latest code cherry-picked
> on top of v4.14 is here
> https://github.com/plbossart/sound/tree/backport/intel-audio-stable-v4.14

Thanks.  But I see only the very same content in sound/soc/intel/*...?


Takashi

> the menuconfig options are still in device drivers/sound/ASoC but now
> you have SST and SOF menus.
> 
> >
> >
> > And I believe there are a few more possible cleanups / fixes in the
> > messy Intel ASoC Kconfigs.  For example, SND_SOC_INTEL_SST is almost
> > always set.  The only exception is via SND_SST_ATOM_HIFI2_PLATFORM.
> > But all machine drivers using Atom Hifi2 do set SND_SST_IPC_ACPI,
> > which also requires SND_SOC_INTEL_SST.
> >
> > Further looking at this, we see that the only entry that does *not*
> > require SND_SOC_INTEL_SST is the case with SND_MFLD_MACHINE in
> > sound/soc/intel/boards.  And now more interesting part -- there is no
> > corresponding entry in Makefile.  That is, this kconfig is effectively
> > dead!  The source code mfld_machine.c exists, but it's just a place
> > holder now.  The code was supposed to be integrated into atom
> > directory by the commit b97169da0699, but it seems forgotten to be
> > updated.
> >
> > Hmm...
> >
> >
> > Takashi
> >
> 

  reply	other threads:[~2017-11-16 15:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 14:51 Takashi Iwai
2017-11-15  2:40 ` Linus Torvalds
2017-11-15  7:34   ` Takashi Iwai
2017-11-15 11:37     ` Mark Brown
2017-11-15 11:58       ` Takashi Iwai
2017-11-15 12:16         ` Mark Brown
2017-11-15 13:16           ` Takashi Iwai
2017-11-15 13:33             ` Mark Brown
2017-11-15 13:37               ` Takashi Iwai
     [not found]         ` <20171115152411.GI3187@localhost>
2017-11-15 15:37           ` Mark Brown
2017-11-15 16:19           ` [alsa-devel] " Pierre-Louis Bossart
2017-11-15 17:11             ` Linus Torvalds
2017-11-16 14:55     ` Pierre-Louis Bossart
2017-11-16 15:10       ` Takashi Iwai [this message]
2017-11-16 20:27         ` Pierre-Louis Bossart
2017-11-17 14:24           ` Mark Brown

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=s5hy3n61cpq.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vinod.koul@intel.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

all inboxes | Powered by JetHome®