[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB904C5425BA6F4E8424B3B51A1414D16649F4A546@NWD2CMBX1.ad.analog.com>
Date: Thu, 10 Mar 2011 04:45:48 -0500
From: "Cai, Cliff" <Cliff.Cai@...log.com>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>,
Cliff Cai <cliffcai.sh@...il.com>
CC: Mike Frysinger <vapier.adi@...il.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"device-drivers-devel@...ckfin.uclinux.org"
<device-drivers-devel@...ckfin.uclinux.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"lrg@...mlogic.co.uk" <lrg@...mlogic.co.uk>
Subject: RE: [alsa-devel] [Device-drivers-devel] [PATCH] Add driver for
Analog Devices ADAU1701 SigmaDSP
>-----Original Message-----
>From: Mark Brown [mailto:broonie@...nsource.wolfsonmicro.com]
>Sent: 2011年3月9日 18:01
>To: Cliff Cai
>Cc: Mike Frysinger; Cai, Cliff; alsa-devel@...a-project.org;
>linux-kernel@...r.kernel.org;
>device-drivers-devel@...ckfin.uclinux.org;
>akpm@...ux-foundation.org; lrg@...mlogic.co.uk
>Subject: Re: [alsa-devel] [Device-drivers-devel] [PATCH] Add
>driver for Analog Devices ADAU1701 SigmaDSP
>
>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@...il.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.
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.
Cliff
Powered by blists - more mailing lists