From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: "Austin, Brian" <Brian.Austin@cirrus.com>
Cc: Mark Brown <broonie@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
"Handrigan, Paul" <Paul.Handrigan@cirrus.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"rob@landley.net" <rob@landley.net>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v2] ASoC: cs42888: Add codec driver support
Date: Wed, 12 Mar 2014 10:03:35 +0800 [thread overview]
Message-ID: <20140312020334.GD1177@MrMyself> (raw)
In-Reply-To: <03E7E694-045D-4C8B-A1A4-98CC306D6D63@cirrus.com>
Hi Brian,
On Wed, Mar 12, 2014 at 02:05:00AM +0000, Austin, Brian wrote:
>
>
> >> On Mar 11, 2014, at 13:46, "Mark Brown" <broonie@kernel.org> wrote:
> >>
> >> On Tue, Mar 11, 2014 at 04:55:58PM +0100, Lars-Peter Clausen wrote:
> >> On 03/11/2014 04:41 PM, Brian Austin wrote:
> >
> >>> So WRT the CS42888, this is one device in a series of 2 devices that are
> >>> register compatible with the only difference being that the CS42488 has 2
> >>> extra ADC's. Same die and same DeviceID.
> >
> >>> Would it make more sense to submit the driver with the extra ADC's to make
> >>> it feature complete for both devices? Wouldn't be odd to have 2 drivers that
> >>> do the same for 98% of the code.
> >
> >> This should be in one driver. But support for the second device can
> >> always be added in a follow up patch.
> >
> > Yes, we can add support later. It might be helpful to name the driver
> > with some generic name I guess.
> CS42xx8 would work.
>
> We have a CS42448 and the CS42888. The difference is the 2 extra ADC's on the CS42448. I can add those later.
>
> I still would like to go over some of the v2 code though before a v3 is sent.
Actually I've already sent v3 right after this v2 due to some doc updating.
Anyway, I'd love to wait for your comments against the patch before I send v3.
Thank you,
Nicolin
prev parent reply other threads:[~2014-03-12 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 11:19 [PATCH v2] ASoC: cs42888: Add codec driver support Nicolin Chen
2014-03-11 11:30 ` Mark Rutland
2014-03-11 11:11 ` Nicolin Chen
[not found] ` <1394536791-8381-1-git-send-email-Guangyu.Chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-03-11 15:41 ` Brian Austin
2014-03-11 15:55 ` Lars-Peter Clausen
2014-03-11 18:46 ` Mark Brown
2014-03-12 1:54 ` Nicolin Chen
2014-03-12 2:05 ` Austin, Brian
2014-03-12 2:03 ` Nicolin Chen [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=20140312020334.GD1177@MrMyself \
--to=guangyu.chen@freescale.com \
--cc=Brian.Austin@cirrus.com \
--cc=Paul.Handrigan@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
/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).