From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: balajitk@ti.com
Cc: linux-omap@vger.kernel.org, sameo@linux.intel.com, wim@iguana.be,
timo.t.kokkonen@nokia.com, ben-linux@fluff.org,
lrg@slimlogic.co.uk, p_gortmaker@yahoo.com, a.zummo@towertech.it,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Rajendra Nayak <rnayak@ti.com>,
x0052729@ti.com
Subject: Re: [PATCH v3 01/04] ARM: OMAP: Rename twl4030* driver files to enable re-use
Date: Thu, 1 Oct 2009 13:38:20 +0100 [thread overview]
Message-ID: <20091001123819.GA21973@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1254399409-3473-1-git-send-email-balajitk@ti.com>
On Thu, Oct 01, 2009 at 05:46:49PM +0530, balajitk@ti.com wrote:
> The upcoming TWL6030 is companion chip for OMAP4 like the current TWL4030
> for OMAP3. The common modules like RTC, Regulator creates opportunity
> to re-use the most of the code from twl4030.
> This patch renames few common drivers twl4030* files to twl* to enable
> the code re-use.
> sound/soc/codecs/twl4030.c | 2 +-
Nack on this part of the change.
The TWL6030 audio architecture is noticably different to the TWL4030
audio architecture, most of the digital functionality has been moved
into the OMAP and the I2S/DSP DAIs replaced by PDM links. Merging the
two drivers was previously suggested in response to the TWL6030 CODEC
driver postings but Misael Lopez Cruz (who is doing the driver) wasn't
happy with the idea.
next prev parent reply other threads:[~2009-10-01 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 12:16 [PATCH v3 01/04] ARM: OMAP: Rename twl4030* driver files to enable re-use balajitk
2009-10-01 12:38 ` Mark Brown [this message]
2009-10-01 12:56 ` Krishnamoorthy, Balaji T
2009-10-01 13:06 ` Mark Brown
2009-10-01 13:06 ` Shilimkar, Santosh
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=20091001123819.GA21973@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=a.zummo@towertech.it \
--cc=balajitk@ti.com \
--cc=ben-linux@fluff.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=p_gortmaker@yahoo.com \
--cc=rnayak@ti.com \
--cc=sameo@linux.intel.com \
--cc=santosh.shilimkar@ti.com \
--cc=timo.t.kokkonen@nokia.com \
--cc=wim@iguana.be \
--cc=x0052729@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.