From: Jesse Marroquin <jesse.marroquin@maxim-ic.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Peter Hsiang <Peter.Hsiang@maxim-ic.com>,
Liam@alsa-project.org, Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: Add MAX98089 CODEC driver
Date: Thu, 11 Nov 2010 17:16:12 -0600 [thread overview]
Message-ID: <4CDC793C.2040406@maxim-ic.com> (raw)
In-Reply-To: <20101111211801.GA3399@opensource.wolfsonmicro.com>
Thanks for pointing out the I2C device ID. After looking at the existing
drivers that have multiple I2C IDs, I see that the devices can be uniquely
identified. With this we should be able to accommodate both devices with
the same driver.
On 11/11/2010 03:18 PM, Mark Brown wrote:
> 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.
>
prev parent reply other threads:[~2010-11-11 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 20:21 [PATCH] ASoC: Add MAX98089 CODEC driver Jesse Marroquin
2010-11-11 21:18 ` Mark Brown
2010-11-11 23:16 ` Jesse Marroquin [this message]
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=4CDC793C.2040406@maxim-ic.com \
--to=jesse.marroquin@maxim-ic.com \
--cc=Liam@alsa-project.org \
--cc=Peter.Hsiang@maxim-ic.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=tiwai@suse.de \
/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).