From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
"Lambert, David" <dlambert@ti.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 1/5] ASoC: DMIC: Adding the OMAP DMIC driver
Date: Wed, 29 Dec 2010 12:11:04 +0000 [thread overview]
Message-ID: <20101229121103.GC3017@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20101229115924.GA2222@legolas.emea.dhcp.ti.com>
On Wed, Dec 29, 2010 at 01:59:24PM +0200, Felipe Balbi wrote:
> On Wed, Dec 29, 2010 at 11:56:28AM +0000, Mark Brown wrote:
> >The other thing with McBSP is that it's a generic programmable serial
> >port and so need not be tied to audio use (though as I understand it
> >other uses are very rare).
> So why is it still tied to OMAP-only ? There's no abstraction layer
> around McBSP so OMAP McBSP driver has to export a whole bunch of symbols
> for its users:
As far as I know the hardware has not been used on other platforms - all
the people who care specifically about the driver are using OMAP and
don't see any reason to do the work. There's really no pressure to do
this.
next prev parent reply other threads:[~2010-12-29 12:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 4:17 [PATCH 0/5] Adding OMAP DMIC driver to kernel David Lambert
2010-12-28 4:17 ` [PATCH 1/5] ASoC: DMIC: Adding the OMAP DMIC driver David Lambert
2010-12-28 11:14 ` Felipe Balbi
2010-12-29 1:13 ` Lambert, David
2010-12-29 9:47 ` Felipe Balbi
2010-12-29 10:35 ` Liam Girdwood
2010-12-29 10:44 ` Felipe Balbi
2010-12-29 11:52 ` Liam Girdwood
2010-12-29 11:56 ` Mark Brown
2010-12-29 11:59 ` Felipe Balbi
2010-12-29 12:11 ` Mark Brown [this message]
2010-12-29 12:04 ` Felipe Balbi
2010-12-29 13:00 ` Liam Girdwood
2010-12-29 13:07 ` Felipe Balbi
2010-12-28 14:18 ` Mark Brown
2011-01-05 13:56 ` Lambert, David
2011-01-05 14:03 ` Mark Brown
2010-12-28 4:17 ` [PATCH 2/5] ASoC: DMIC codec: Adding a generic DMIC codec David Lambert
2010-12-28 14:29 ` Mark Brown
2010-12-28 4:17 ` [PATCH 3/5] ASoC: DMIC: Adding OMAP DMIC driver to build David Lambert
2010-12-28 11:40 ` Mark Brown
2010-12-29 2:21 ` Lambert, David
2010-12-28 4:17 ` [PATCH 4/5] OMAP4: hwmod: add entries for DMIC driver David Lambert
2010-12-28 4:17 ` [PATCH 5/5] MAP4: DMIC: Add DMIC codec platform devices David Lambert
2010-12-28 11:23 ` Felipe Balbi
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=20101229121103.GC3017@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=balbi@ti.com \
--cc=dlambert@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=paul@pwsan.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).