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: Mon, 30 Mar 2020 11:32:13 +0100 [thread overview]
Message-ID: <20200330103213.GA4792@sirena.org.uk> (raw)
In-Reply-To: <20200328015831.6230-1-flatmax@flatmax.org>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On Sat, Mar 28, 2020 at 12:58:31PM +1100, Matt Flax wrote:
> This patch is aims to start a stronger discussion on allowing both CPU
> and Codec dais to set formats independently based on direction.
If the DAIs support completely separate formats they're not a single DAI
and should be represented as two DAIs.
> One example of a sound card which requires independent stream formats is
> an isolated sound card, such as the Audio Injector Isolated sound card.
> The magnetic isolation chips on the sound card require stream fomats to
> be different because of digital latency variations on the I2S lines.
Honestly I'm not convinced this is ever going to work reliably - there
is in general an assumption in the code that the formats on both ends of
the link are the same, it seems you'll have to break that as well as
having an asymmetric configuration. You probably need to represent
these isolators as a CODEC and do a CODEC to CODEC link and even then it
seems worrying.
> /* Digital Audio interface formatting */
> -int snd_soc_dai_set_fmt(struct snd_soc_dai *dai, unsigned int fmt);
> +int snd_soc_dai_set_fmt(struct snd_soc_dai *dai, unsigned int fmt, int stream);
This will break the build.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-30 10:33 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 [this message]
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
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=20200330103213.GA4792@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.