| 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
| ||
|
Date: Mon, 26 Sep 2011 22:47:38 +0100 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Leo Yan <leoy@...vell.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "alsa-devel@...a-project.org" <alsa-devel@...a-project.org> Subject: Re: Questions for dummy codec driver On Thu, Sep 22, 2011 at 09:42:14AM +0800, Leo Yan wrote: > On our platform, there have some devices (like hdmi/bt) do not need > config from the CODEC driver, they have their own s/w stack and > interface to configure; for the audio driver, just need to set the > I2S/PCM timing for them. So if there have a common dummy codec > driver, then it can meet our requirement well. Otherwise, there will > have some duplicate codes for these dummy codecs. The general thought here has been that for dumb CODECs the boilerplate is sufficiently small and simple to mean that the discoverability from writing a skeletal driver outweighs the cost of having it kicking around - while there is some boilerplate there it's easier for someone to grab and use this code than it is to work out how exactly to translate the datasheets into code each time they encounter the part. However, a sufficiently well written generic driver would maintain that advantage while reducing the duplication. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists