From: Mark Brown <broonie@kernel.org>
To: Matt Flax <flatmax@flatmax.org>
Cc: alsa-devel@alsa-project.org, lars@metafoo.de,
lgirdwood@gmail.com, pierre-louis.bossart@linux.intel.com
Subject: Re: [PATCH] ASoC: snd_soc_dai_set_fmt add substream independence.
Date: Tue, 31 Mar 2020 12:13:48 +0100 [thread overview]
Message-ID: <20200331111348.GA4802@sirena.org.uk> (raw)
In-Reply-To: <98c3a94a-9020-9a34-7bdf-0ce504573f79@flatmax.org>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Tue, Mar 31, 2020 at 06:40:26PM +1100, Matt Flax wrote:
> ok, I don't quite follow you, but I think what you are saying is that there
> is a trade off between simplifying things for the end user and core
> complexity leading to developer sloppiness ?
> I believe you are saying that it is a rare case to require format asymmetry
> in the same DAI link. For that reason introducing extra functionality into
> the core may not be worth while ?
What I am saying is that we already have a perfectly good way of
representing separate TX and RX DAIs which is far more flexible than
your bodge and that if there is something to be improved on the
userspace interface we should improve that rather than add this which
seems like a bodge.
> > No, my advice is to go down that route if you are doing this. I'm just
> > not convinced that it's going to work reliably since this all sounds
> > rather shaky.
> OK - I can try to go down that route. However I would like to confirm that
> having a codec to codec link doesn't require the original codec or CPU
> drivers to have separate DAIs for playback and capture ? In my case both the
> CPU and Codec drivers have single DAIs for both streams.
OK, that probably won't help then :/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-31 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 1:58 [PATCH] ASoC: snd_soc_dai_set_fmt add substream independence Matt Flax
2020-03-28 3:31 ` kbuild test robot
2020-03-28 3:44 ` kbuild test robot
2020-03-30 10:32 ` Mark Brown
2020-03-30 12:28 ` Matt Flax
2020-03-30 16:31 ` Mark Brown
2020-03-31 7:40 ` Matt Flax
2020-03-31 11:13 ` Mark Brown [this message]
2020-03-31 11:52 ` Matt Flax
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=20200331111348.GA4802@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=flatmax@flatmax.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.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.