From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "ext Lopez Cruz, Misael" <x0052729@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"Krishnamoorthy, Balaji T" <balajitk@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCHv3 1/7] OMAP4: PMIC: Add support for twl6030 codec
Date: Wed, 7 Oct 2009 10:32:36 +0300 [thread overview]
Message-ID: <200910071032.36999.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <67059DBF19D7214F9C66BB0EA91BA90E90C2F931@dlee04.ent.ti.com>
On Tuesday 06 October 2009 19:53:03 ext Lopez Cruz, Misael wrote:
> Peter Ujfalusi wrote:
> > How does the twl4030 series would fit with this modification?
> > I have also added the twl4030 codec as a child for the twl
> > MFD, but I have not finished the cleanup of the codec fully.
>
> twl6030 codec data won't conflict with twl4030's as it's dependent of
> TWL6030_CORE. We can add parallely the required data for twl4030 codec.
I see. I think I'll wait till the twl6030 codec and it's dependencies are in
place, than I can start adding the needed code for the twl4030 codec as well.
Obviously this is needed for the clean up of twl4030 codec and get it to more
sane form.
Thanks,
Péter
next prev parent reply other threads:[~2009-10-07 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 7:29 [PATCHv3 1/7] OMAP4: PMIC: Add support for twl6030 codec Lopez Cruz, Misael
2009-10-06 8:46 ` Peter Ujfalusi
2009-10-06 16:35 ` Mark Brown
2009-10-07 6:26 ` [alsa-devel] " Shilimkar, Santosh
2009-10-07 9:37 ` Mark Brown
2009-10-07 9:40 ` [alsa-devel] " Shilimkar, Santosh
2009-10-06 16:53 ` Lopez Cruz, Misael
2009-10-07 7:32 ` Peter Ujfalusi [this message]
2009-10-07 5:20 ` [alsa-devel] " Krishnamoorthy, Balaji T
2009-10-07 7:41 ` Peter Ujfalusi
2009-10-08 1:30 ` Lopez Cruz, Misael
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=200910071032.36999.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=balajitk@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox