From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: "ext George G. Davis" <gdavis@mvista.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Nikula Jarkko (Nokia-D/Helsinki)" <jarkko.nikula@nokia.com>,
Mark Brown <broonie@sirena.org.uk>,
ext Anuj Aggarwal <anuj.aggarwal@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
ext Misael Lopez Cruz <mesak82@gmail.com>
Subject: Re: [PATCH] ASoC: Add support for OMAP3 EVM
Date: Thu, 26 Feb 2009 09:36:54 +0200 [thread overview]
Message-ID: <200902260936.54301.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <20090225202559.GO4368@mvista.com>
On Wednesday 25 February 2009 22:25:59 ext George G. Davis wrote:
> Hi,
>
> On Tue, Nov 25, 2008 at 02:52:58PM +0000, Mark Brown wrote:
> > On Tue, Nov 25, 2008 at 01:21:20PM +0200, Jarkko Nikula wrote:
> > > Or if those EVM's & SDP's can route TWL4030 audio connections more
> > > flexible than Beagle but somewhat similar manner, then probably have
> > > one single machine driver for all EVM's?
> > >
> > > Otherwise it doesn't make very much sense to have n similar machine
> > > drivers where only functions and variable names differ.
> >
> > Yes, it looks like a lot of these drivers could be redone along the
> > lines of s3c24xx_uda134x.c with platform data specifying the differences
> > between the boards.
>
> Is someone working on updating ASoC drivers for OMAP TWL4030 based
> boards as recommended above? Just curious since I already made the
> mistake of creating my own OMAP3 EVM ASoC driver w/o checking the
> list first. : /
Well, I have checked the s3c24xx_uda134x.c and the corresponding uda134x.c
codec driver. In case of the uda134x codec - since it does not have DAPM
implementation, the board file does not need to deal with the output/input
pins.
In case of boards using the TWL4030 codec it is not that simple IMHO.
You see TWL4030 has nine output 'pins' and six (plus 2x stereo digital mic)
input 'pins'.
So, yes it is doable, but will it make things cleaner and more manageable?
Few things came to my mind, which needs to be addressed:
1. Who is the master (OMAP McBSP or TWL4030)?
2. What is the reference clock in the given board
3. Connected pins (or not connected pins)
4. I2S or TDM mode (this is not implemented yet, but it is coming at some
point)
It easy to provide 1, 2 and 4. But when it comes to 3... One needs to build up
the DAPM routes in the common board file for the supported boards, which again
doable based on - for example - some model/board ID, but I think it will look
ugly.
Or I might over complicate things ;)
> --
> Regards,
> George
--
Péter
next prev parent reply other threads:[~2009-02-26 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 5:39 [PATCH] ASoC: Add support for OMAP3 EVM Anuj Aggarwal
2008-11-25 11:21 ` Jarkko Nikula
2008-11-25 14:52 ` Mark Brown
2009-02-25 20:25 ` [alsa-devel] " George G. Davis
2009-02-25 20:27 ` Mark Brown
2009-02-26 7:18 ` Jarkko Nikula
2009-02-26 7:36 ` Peter Ujfalusi [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-21 12:11 Anuj Aggarwal
2008-11-21 16:33 ` David Brownell
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=200902260936.54301.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=broonie@sirena.org.uk \
--cc=gdavis@mvista.com \
--cc=jarkko.nikula@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=mesak82@gmail.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