From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Cai, Cliff" <Cliff.Cai@analog.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mike Frysinger <vapier.adi@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"device-drivers-devel@blackfin.uclinux.org"
<device-drivers-devel@blackfin.uclinux.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Cliff Cai <cliffcai.sh@gmail.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [Device-drivers-devel] [PATCH] Add driver for Analog Devices ADAU1701 SigmaDSP
Date: Thu, 10 Mar 2011 13:46:05 +0000 [thread overview]
Message-ID: <20110310134605.GC22195@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <DB904C5425BA6F4E8424B3B51A1414D16649F4A546@NWD2CMBX1.ad.analog.com>
On Thu, Mar 10, 2011 at 04:45:48AM -0500, Cai, Cliff wrote:
> >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 -
> I'm afraid it's not the real use case,the test mode just for test,
> In practice,people always want the DSP to run some algrithm at the beginning,
> Although they may change it later.
I'd be surprised if people wanted to actually play audio through a
passthrough firmware in a shipping system but consider cases like board
bringup (where just verifying that everything is physically connected is
useful) and early boot (where you might not have mounted all filesystems
yet but the driver is trying to start up).
next prev parent reply other threads:[~2011-03-10 13:46 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
2011-03-10 0:35 ` Mike Frysinger
2011-03-10 9:45 ` [alsa-devel] " Cai, Cliff
2011-03-10 13:46 ` Mark Brown [this message]
2011-03-11 7:54 ` 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=20110310134605.GC22195@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Cliff.Cai@analog.com \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--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).