linux-kernel - RE: [alsa-devel] [Device-drivers-devel] [PATCH] Add driver for Analog Devices ADAU1701 SigmaDSP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 11 Mar 2011 02:54:42 -0500
From:	"Cai, Cliff" <Cliff.Cai@...log.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	Cliff Cai <cliffcai.sh@...il.com>,
	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月10日 21:46
>To: Cai, Cliff
>Cc: Cliff Cai; Mike Frysinger; 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 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).

1.The default firmware is used when the chip is just powered-up,
Once driver gets the control,it should load the custom firmware to replace
The default one,
2.we don't need to worry about this case,the driver which needs loading firmware
Has to be compiled as a module,and of cause,we load it after the filesystem has been mounted.

Cliff