From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: alsa-devel@alsa-project.org
Subject: ASoC for TI OMAP - Multiformat ASoC DAI link driver?
Date: Wed, 2 Apr 2008 13:45:38 +0300 [thread overview]
Message-ID: <20080402134538.67d67d6e.jarkko.nikula@nokia.com> (raw)
Currently in ASoC v1 we have one DAI driver per one format? E.g.
separate drivers for I2S, AC97, etc and type field in cpu_dai
structure is not a bit field or at least not used such way in
soc-core.c and DAI link drivers.
struct snd_soc_cpu_dai pxa_i2s_dai = {
...
.type = SND_SOC_DAI_I2S,
...
I looked shortly asoc-v2-dev branch and now this type field is gone.
Does it mean that there you can have DAI link driver which supports
multiple formats in set_fmt callback?
I'm asking this since McBSP (Multichannel Buffered Serial Port) found
in OMAP processors can be configured to almost any imaginable format
and IMO it doesn't make a sense to have separate drivers for each of
them if there is a difference only in few configuration bits.
--
Jarkko
next reply other threads:[~2008-04-02 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 10:45 Jarkko Nikula [this message]
2008-04-02 11:48 ` ASoC for TI OMAP - Multiformat ASoC DAI link driver? Mark Brown
2008-04-03 6:13 ` Jarkko Nikula
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=20080402134538.67d67d6e.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=alsa-devel@alsa-project.org \
/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