From: Arnaud Pouliquen <arnaud.pouliquen@st.com>
To: alsa-devel@alsa-project.org
Cc: broonie@kernel.org, lgirdwood@gmail.com
Subject: [RFC] question regarding codec DAI ops
Date: Fri, 20 Jun 2014 16:07:03 +0200 [thread overview]
Message-ID: <53A44007.1000008@st.com> (raw)
Hello,
I have a platform with several audio IOs (DAC , HDMI...) and I2S In/out
connectors.
I'm using my codec driver but for this I2S output i used dummy codec
driver with the snd-soc-dummy-dai dai.
On platform side I have several instances of CPU DAI, and i'm using
helpers function like snd_soc_dai_set_tdm_slot to configure associated
codec DAIs.
My issue is that these functions return error for my I2S output because
ops functions are not implemented in dummy driver.
I see 3 solutions:
- implement ops in dummy drivers ( soc-utils)
- return 0 instead of error when ops is not implemented ( soc-core)
- Add a test in my driver on ops before calling it.
First one seems the best compromise to avoid to accumulate tests in
platform drivers.
From your point of view, what should be best solution?
BR
Arnaud
next reply other threads:[~2014-06-20 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 14:07 Arnaud Pouliquen [this message]
2014-06-21 10:26 ` [RFC] question regarding codec DAI ops Mark Brown
2014-06-23 7:30 ` Arnaud Pouliquen
2014-06-30 10:31 ` Mark Brown
2014-07-01 9:28 ` Arnaud Pouliquen
2014-07-01 10:14 ` Mark Brown
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=53A44007.1000008@st.com \
--to=arnaud.pouliquen@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.