alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Cliff Cai <cliffcai.sh@gmail.com>
Cc: cliff.cai@analog.com, Mike Frysinger <vapier.adi@gmail.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	device-drivers-devel@blackfin.uclinux.org,
	akpm@linux-foundation.org, lrg@slimlogic.co.uk
Subject: Re: [Device-drivers-devel] [PATCH] Add driver for Analog Devices ADAU1701 SigmaDSP
Date: Wed, 9 Mar 2011 10:00:55 +0000	[thread overview]
Message-ID: <20110309100055.GB6923@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTik=wEyCEY5xsrdGJw6t_VHH9ByKt4mX348P8uD7@mail.gmail.com>

On Wed, Mar 09, 2011 at 03:25:05PM +0800, Cliff Cai wrote:
> On Mon, Mar 7, 2011 at 8:29 PM, Mike Frysinger <vapier.adi@gmail.com> wrote:

> > i dont see the issue here.  the firmware is *optional* and does not
> > impair basic audio output.  further, the firmware is fully
> > written/compiled/maintained by the end customer, just like the
> > application.  which means there is no "magic" here -- the end customer
> > is the wizard.

> it's a DSP,so firmware is not optional,actually there is default
> internal program can be used
> if no external firmware is downloaded,of cause, the internal program
> is only used to test analog audio pass-through.

If there is default firmware then even if it's not particularly useful
the kernel should probably not *require* that additional firmware is
provided during driver startup - the system may wish to wait until later
in the boot to provide it, for example because it needs to mount media
to get to the firmware or because it needs to do additional work to
decide what firmware is required for the current system setup.

  reply	other threads:[~2011-03-09 10:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07  1:11 [PATCH] Add driver for Analog Devices ADAU1701 SigmaDSP cliff.cai
2011-03-07  2:44 ` [Device-drivers-devel] " Mike Frysinger
2011-03-07 11:44   ` Mark Brown
2011-03-07 11:01 ` Liam Girdwood
2011-03-07 11:41 ` Mark Brown
2011-03-07 11:50   ` [Device-drivers-devel] " Mike Frysinger
2011-03-07 12:15     ` Mark Brown
2011-03-07 12:29       ` Mike Frysinger
2011-03-07 14:59         ` Mark Brown
2011-03-07 15:33           ` Mike Frysinger
2011-03-07 15:55             ` Mark Brown
2011-03-09  6:08               ` Mike Frysinger
2011-03-09  7:39                 ` Cliff Cai
2011-03-09  9:55                 ` Mark Brown
2011-04-19  0:15           ` Andres Salomon
2011-04-19  8:06             ` Mark Brown
2011-03-09  7:25         ` Cliff Cai
2011-03-09 10:00           ` Mark Brown [this message]
2011-03-10  0:35             ` Mike Frysinger
2011-03-10  9:45             ` [alsa-devel] " Cai, Cliff
2011-03-10 13:46               ` Mark Brown
2011-03-11  7:54                 ` [alsa-devel] " Cai, Cliff
2011-03-11 11:53                   ` Mark Brown
2011-03-14  2:23                     ` [alsa-devel] " Cai, Cliff
2011-03-14 11:29                       ` Mark Brown
2011-03-09  7:04   ` Cliff Cai
2011-03-09 10:12     ` Mark Brown
2011-03-10 10:04       ` [alsa-devel] " Cai, Cliff

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=20110309100055.GB6923@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=cliff.cai@analog.com \
    --cc=cliffcai.sh@gmail.com \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=vapier.adi@gmail.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).