From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC for TI OMAP - alsa-devel submission?
Date: Thu, 3 Apr 2008 08:56:10 +0300 [thread overview]
Message-ID: <20080403085610.c0141864.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <20080402110054.GA7977@rakim.wolfsonmicro.main>
On Wed, 2 Apr 2008 12:00:54 +0100
"ext Mark Brown" <broonie@opensource.wolfsonmicro.com> wrote:
> On Wed, Apr 02, 2008 at 01:45:30PM +0300, Jarkko Nikula wrote:
>
> > So what I mean that should I post the patch like as it now, rebased
> > to dev branch of linux-2.6-asoc tree and with some minor changes,
> > or wait a bit when all linux-omap and ASoC v2 evolve? What you
> > think?
>
> Whatever is most convenient for you. From the point of view of
> getting stuff in immediately it's best to base things on ASoC v1
> though from an ongoing development point of view ASoC v2 is a better
> target if you can cope with any churn and hopefully we should be
> starting to push it into the kernel within the next couple of release
> cycles so if it's going to take a while to get the required BSP
> changes in...
>
I'll think I have to go for both :-)
The first ASoC v1 based version I would mostly like to see as an
enabler for getting n different ALSA implementation we have in
linux-omap tree to be ported for ASoC. Especially codec drivers. Or to
have an another DAI link driver for EAC (Enhanced Audio Controller)
found in OMAP2420.
The v2 I see also as mandatory path. We already do have boards with
multiple DAI links and codecs: e.g. audio codec + audio link to
bluetooth chip.
I'll simplify a bit my patch, base it to alsa-dev and post it here soon.
--
Jarkko
prev parent reply other threads:[~2008-04-03 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 10:45 ASoC for TI OMAP - alsa-devel submission? Jarkko Nikula
2008-04-02 11:00 ` Mark Brown
2008-04-03 5:56 ` Jarkko Nikula [this message]
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=20080403085610.c0141864.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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