linux-kernel - Re: [PATCH] ASoC: Add MAX98089 CODEC driver

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 11 Nov 2010 21:18:02 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Jesse Marroquin <jesse.marroquin@...im-ic.com>
Cc:	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	Peter Hsiang <Peter.Hsiang@...im-ic.com>,
	Dimitris Papastamos <dp@...nsource.wolfsonmicro.com>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: Add MAX98089 CODEC driver

On Thu, Nov 11, 2010 at 02:21:07PM -0600, Jesse Marroquin wrote:
> This patch adds the initial driver for the MAX98089 CODEC.

I've not read this properly yet but on a first quick scan through this
bears a more than passing resemblance to the MAX98088 driver - are there
sufficient incompatibilities between the chips to warrant having a
separate driver?  http://datasheets.maxim-ic.com/en/ds/MAX98088.pdf
would suggest not...  

Keeping a single driver means less code to maintain, which is generally
a win.  Variations between the parts can be accommodated by registering
different controls and so on based on the I2C device ID that the system
registers.
--
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/