Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Jaroslav Kysela <perex@perex.cz>,
	ALSA development <alsa-devel@alsa-project.org>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>,
	Jie Yang <yang.jie@linux.intel.com>,
	Mengdong Lin <mengdong.lin@linux.intel.com>,
	Pan Xiuli <xiuli.pan@linux.intel.com>
Subject: Re: [alsa-devel] topology file broadwell.conf
Date: Thu, 2 Jan 2020 11:53:38 -0600	[thread overview]
Message-ID: <3f231650-094d-e755-b686-c3f8650dda84@linux.intel.com> (raw)
In-Reply-To: <2cae9b3c-8634-7aff-3d76-7a16b1807abf@perex.cz>


>      I am working on some (major) cleanups for the topology library and 
> I hit the issue with the topology file broadwell.conf in upstream. It 
> cannot be compiled with the latest alsatplg / libatopology, because the 
> SectionPCMConfig was removed in commit 
> 368e4f2a897b5500573a2ee525f5504c135cfca2 in alsa-lib.
>      Which driver is using this topology in the current linux kernel?

IIRC, the broadwell/SST driver does not use the topology/DPCM parts so 
it's likely there is no user for this topology file. Keyon/Liam, can you 
confirm?

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2020-01-02 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 18:15 [alsa-devel] topology file broadwell.conf Jaroslav Kysela
2020-01-02 17:53 ` Pierre-Louis Bossart [this message]

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=3f231650-094d-e755-b686-c3f8650dda84@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=mengdong.lin@linux.intel.com \
    --cc=perex@perex.cz \
    --cc=subhransu.s.prusty@intel.com \
    --cc=xiuli.pan@linux.intel.com \
    --cc=yang.jie@linux.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