All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Cc: patches.audio@intel.com, Vinod Koul <vinod.koul@intel.com>,
	alsa-devel@alsa-project.org, broonie@kernel.org,
	lgirdwood@gmail.com
Subject: Re: [PATCH] conf: topology: Add topolgy for skylake i2s configuration
Date: Tue, 09 Feb 2016 14:18:58 +0100	[thread overview]
Message-ID: <s5hpow6vx6l.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160209131415.GA26322@subhransu-desktop>

On Tue, 09 Feb 2016 14:14:19 +0100,
Subhransu S. Prusty wrote:
> 
> On Tue, Feb 09, 2016 at 12:54:39PM +0100, Takashi Iwai wrote:
> > On Tue, 09 Feb 2016 12:47:53 +0100,
> > Subhransu S. Prusty wrote:
> > > 
> > > On Tue, Feb 09, 2016 at 12:15:45PM +0100, Takashi Iwai wrote:
> > > > On Mon, 08 Feb 2016 04:55:56 +0100,
> > > > Subhransu S. Prusty wrote:
> > > > > 
> > > > > This patch adds basic playback/capture support for skylake i2s
> > > > > platform. DSP topology module data are passed through the binary
> > > > > files. The framework parses these files and puts the data in the
> > > > > widget private section for the corresponding widget. This is
> > > > > parsed by kernel driver and stored as module config for the DSP.
> > > > > Based on usecase these data are sent to the DSP through IPCs for
> > > > > further processing.
> > > > 
> > > > Can we have sources for these binaries, or do they have to be
> > > > binary-only?
> > > 
> > > Hi Takashi,
> > > 
> > > These are binary only data.
> > 
> > Then this isn't a good material for merging to alsa-lib.  How is the
> > license compatibility?
> 
> Each binary file here holds config for each module based on skl_dfw_module
> structure as expected by Skylake driver. The skl driver formats IPCs parsing
> this config.
> 
> This structure skl_dfw_module is already defined as part of
> skl-tplg-interface.h.

Well, the question is whether this IP is a programmed data block, not
some simple numbers.  If yes, it's always a question whether it's
compatible with GPL.  Although alsa-lib is LGPL, putting the binary
blob in the *code tree* doesn't look good to me.

IMO, this should go to firmware tree instead, unless you can give the
source code to build the binary.


Takashi

  reply	other threads:[~2016-02-09 13:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1454903756-2075-1-git-send-email-subhransu.s.prusty@intel.com>
     [not found] ` <s5ha8naxhge.wl-tiwai@suse.de>
     [not found]   ` <20160209114749.GA7243@subhransu-desktop>
2016-02-09 11:54     ` [PATCH] conf: topology: Add topolgy for skylake i2s configuration Takashi Iwai
2016-02-09 13:14       ` Subhransu S. Prusty
2016-02-09 13:18         ` Takashi Iwai [this message]
2016-02-09 13:34           ` Vinod Koul
2016-02-09 13:48             ` Takashi Iwai
2016-02-11  3:52               ` Vinod Koul
2016-02-11  8:38                 ` Takashi Iwai
2016-02-11 13:56                   ` Takashi Sakamoto
2016-02-11 15:35                     ` Takashi Iwai

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=s5hpow6vx6l.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=patches.audio@intel.com \
    --cc=subhransu.s.prusty@intel.com \
    --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 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.