LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Lin, Mengdong" <email@example.com>
To: Mark Brown <firstname.lastname@example.org>, Guenter Roeck <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>,
Takashi Iwai <firstname.lastname@example.org>,
Liam Girdwood <email@example.com>,
"Patel, Chintan M" <firstname.lastname@example.org>,
Guenter Roeck <email@example.com>,
"Nc, Shreyas" <firstname.lastname@example.org>
Subject: RE: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files
Date: Fri, 25 May 2018 09:04:55 +0000 [thread overview]
Message-ID: <F46914AEC2663F4A9BB62374E5EEF8F88276C0ED@SHSMSX103.ccr.corp.intel.com> (raw)
> -----Original Message-----
> From: email@example.com [mailto:alsa-devel-bounces@alsa-
> project.org] On Behalf Of Mark Brown
> Sent: Thursday, May 24, 2018 11:12 PM
> On Thu, May 24, 2018 at 07:55:06AM -0700, Guenter Roeck wrote:
> > On Thu, May 24, 2018 at 7:18 AM Mark Brown <firstname.lastname@example.org> wrote:
> Your mail client formatting seems to be broken, the word wrapping is really
> funky (it looks like it's breaking longer than 80 column lines in the middle of
> paragraphs rather than flowing paragraphs within 80 columns).
> > > > I don't mind adding the structures to
> > > > sound/soc/intel/skylake/skl-tplg-interface.h,
> > > > but it seems a bit out of scope to tie this with moving the file
> > > > to include/uapi/sound.
> > > > I think that should be a separate discussion.
> > > Is there some reason not to just do it while we're looking at this?
> > > I don't see why we wouldn't want to do this.
> > I don't mind doing this. However, keeping the change local and in a
> > single patch would make it easier to backport, and I think that the
> > ability to backport would be essential to get more than one-person
> > test coverage. I also would have liked feedback from someone at Intel,
> > at least for the Skylake specific structures.
> Oh, of course - I'm just saying we should do this, not that everything needs to be
> in one patch. Obviously the code motion would be a separate patch.
> > Anyway, what file do you have in mind for the structure definitions,
> > both for the ones in soc-tolopogy.c and the ones needed in
> > skl-topology.c ? Everything into asoc.h, or something else ?
> All of those that can appear in a firmware file, I don't super care where they end
> up but possibly a separate header file or files to the kernel specific ones as they
> might get used with Windows.
Please put the Skylake specific structures in a separate header file, not in asoc.h.
The file asoc.h is for generic topology structures which are platform independent. The topology code in alsa-lib never parses the platform specific structures.
The Skylake specific structures are needed by vendor applications like Intel topology tool (ITT) to define topology for different platforms. The applications can include both asoc.h, skl-tplg-interface.h and other device specific headers.
next prev parent reply other threads:[~2018-05-25 9:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 16:58 Guenter Roeck
2018-05-22 17:14 ` Mark Brown
2018-05-22 19:59 ` [alsa-devel] " Pierre-Louis Bossart
2018-05-23 8:24 ` Mark Brown
2018-05-23 13:42 ` Pierre-Louis Bossart
2018-05-23 13:56 ` Takashi Iwai
[not found] ` <CABXOdTdGyfBdZUzG-DzGgfr0Afrh9dtgdXibQreOZm7nb4z3email@example.com>
2018-05-23 14:58 ` Takashi Iwai
2018-05-23 15:52 ` Mark Brown
[not found] ` <CABXOdTd5+QJHOZ6BcSO-TfJCqcLzdd+Gbnf4HYh9i9cG+UHfirstname.lastname@example.org>
2018-05-23 9:49 ` Mark Brown
2018-05-23 13:54 ` Takashi Iwai
2018-05-23 13:56 ` Mark Brown
[not found] ` <CABXOdTeCr-ExO9O3XAHK-DnNf5yLGO0TPkXgs60TB90jGNB2_Q@mail.gmail.com>
2018-05-23 15:58 ` Mark Brown
2018-05-23 16:17 ` Guenter Roeck
2018-05-24 9:52 ` Takashi Iwai
2018-05-24 14:18 ` Mark Brown
2018-05-24 14:55 ` Guenter Roeck
2018-05-24 15:11 ` Mark Brown
2018-05-25 9:04 ` Lin, Mengdong [this message]
2018-05-25 13:20 ` [alsa-devel] " Guenter Roeck
2018-05-23 16:29 ` Guenter Roeck
2018-05-23 20:28 ` [alsa-devel] " Pierre-Louis Bossart
2018-05-23 21:22 ` Guenter Roeck
2018-05-24 3:38 ` Pierre-Louis Bossart
2018-05-25 13:40 ` Shreyas NC
2018-05-25 14:09 ` Guenter Roeck
2018-05-25 17:41 ` Guenter Roeck
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='RE: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).