From: "Koul, Vinod" <vinod.koul@intel.com>
To: "tiwai@suse.de" <tiwai@suse.de>
Cc: "liam.r.girdwood@linux.intel.com"
<liam.r.girdwood@linux.intel.com>,
Patches Audio <patches.audio@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"Nc, Shreyas" <shreyas.nc@intel.com>
Subject: Re: [PATCH v2 2/2] conf: topology: Generate Private data binary blobs
Date: Tue, 5 Apr 2016 15:52:19 +0000 [thread overview]
Message-ID: <1459871538.3136.42.camel@intel.com> (raw)
In-Reply-To: <s5hh9fgm7vy.wl-tiwai@suse.de>
On Tue, 2016-04-05 at 16:45 +0200, Takashi Iwai wrote:
> > There is no special dependency here, so we can just add
> > > src/conf/toplogty/*/data/Makefile.am in the toplevel configure.ac?
> >
> > Yes that seems better. Also please note if we do that alsa-lib can
> > compile the data before it compiles skl topology so we can get rid
> > of
> > bnary blobs whcih are prebuilt and get them generated on alsa-lib
> > compile.
>
> Yeah, that's nicer, too.
One thing though we need to run the binary to generate blobs, am
thinking of hooking that up with install step.
>
> > This will solve above header patch and will use std path in lib
> >
> > Is that okay with you?
>
> Sure.
>
>
> thanks,
>
> Takashi
--
~Vinod
next prev parent reply other threads:[~2016-04-05 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 5:20 [PATCH v2 0/2] conf: topology: Add the conf for SKL-rt286 Vinod Koul
2016-04-05 5:20 ` [PATCH v2 2/2] conf: topology: Generate Private data binary blobs Vinod Koul
2016-04-05 12:00 ` Takashi Iwai
2016-04-05 14:38 ` Koul, Vinod
2016-04-05 14:45 ` Takashi Iwai
2016-04-05 15:52 ` Koul, Vinod [this message]
2016-04-05 16:05 ` Takashi Iwai
2016-04-05 16:08 ` Koul, Vinod
2016-04-05 20:10 ` Takashi Iwai
2016-04-05 21:24 ` Mark Brown
2016-04-06 13:03 ` Koul, Vinod
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=1459871538.3136.42.camel@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=shreyas.nc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.