alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.de>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"Harsha, Priya" <priya.harsha@intel.com>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
	Alan Cox <alan@linux.intel.com>
Subject: Re: sst: Intel SST audio driver
Date: Tue, 19 Oct 2010 06:13:40 -0700	[thread overview]
Message-ID: <20101019131340.GB7498@suse.de> (raw)
In-Reply-To: <438BB0150E931F4B9CE701519A44630104BE811785@bgsmsx502.gar.corp.intel.com>

On Tue, Oct 19, 2010 at 12:05:38PM +0530, Koul, Vinod wrote:
>  
> > ... so the whole messages can be reduced to a sentense:
> >   "Rewrite the driver based on ASoC!"
> > 
> > Then it's a question to Intel guys.  If they would like to support for
> > it, we can happily wait for it before merging.  If they don't want but
> > keep as is, then questions are:
> >  - whether to keep it in upstream or not
> >  - where to keep it, in staging or in sound tree
> > 
> > and, the latter question is nothing but a bikeshedding; in anyway it's
> > a second choice, after all.  We should spend time for more useful
> > things :)
> 
> Yes Intel is planning to rewrite the sound card driver for ASoC.
> I will take us little time for that :-)
> 
> Meanwhile IMO it would be great to have this driver in staging or in sound 
> whichever you guys agree to

As the userspace api is going to change, and Intel is committed to redo
the api to use ASoC, I suggest it goes into the staging tree.  That will
force Intel to live up to that promise, otherwise the code will be
dropped from the tree.

thanks,

greg k-h

      reply	other threads:[~2010-10-19 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1287396001.20373.alsa-devel@alsa-project.org>
2010-10-19  6:35 ` sst: Intel SST audio driver Koul, Vinod
2010-10-19 13:13   ` Greg KH [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=20101019131340.GB7498@suse.de \
    --to=gregkh@suse.de \
    --cc=alan@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=priya.harsha@intel.com \
    --cc=tiwai@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).