From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Krishnamoorthy, Balaji T" <balajitk@ti.com>,
"ext Lopez Cruz, Misael" <x0052729@ti.com>
Subject: Re: [PATCHv3 1/7] OMAP4: PMIC: Add support for twl6030 codec
Date: Tue, 6 Oct 2009 17:35:46 +0100 [thread overview]
Message-ID: <20091006163546.GA11062@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200910061146.05080.peter.ujfalusi@nokia.com>
On Tue, Oct 06, 2009 at 11:46:05AM +0300, 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.
The TWL6030 specific bits all look good but this change ought to go via
the MFD tree (probably as part of the big patch series adding twl6030
support that doesn't look to have been applied yet). Are people happy
that the interface to the twl6030 won't change as a result of the
twl4030 audio support? If so then I'll apply the ASoC side now, the
Kconfig dependencies will stop it being built too soon.
next prev parent reply other threads:[~2009-10-06 16:35 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 [this message]
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
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=20091006163546.GA11062@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=balajitk@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.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