From: Mark Brown <broonie@kernel.org>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: Andrew Lunn <andrew@lunn.ch>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
lgirdwood@gmail.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Rob Clark <robdclark@gmail.com>,
Dave Airlie <airlied@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
Date: Wed, 2 Jul 2014 20:42:52 +0100 [thread overview]
Message-ID: <20140702194252.GN410@sirena.org.uk> (raw)
In-Reply-To: <20140702195154.47d6f6b4@armhf>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
On Wed, Jul 02, 2014 at 07:51:54PM +0200, Jean-Francois Moine wrote:
> I tested this CODEC with both DAPM and DPCM. If the audio subsystem
> asks for streaming on both I2S and S/PDIF, only the last call is served
> (this depends on the order of the DAI links in the audio card creation
> table).
I'd expect this to return an error for the busy DAI rather than just
silently ignore it failing to start or (better) implement some control
to let the user select which of the DAIs is active.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-02 19:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 16:38 [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter Jean-Francois Moine
2014-07-02 16:56 ` Andrew Lunn
2014-07-02 17:51 ` Jean-Francois Moine
2014-07-02 18:02 ` Russell King - ARM Linux
2014-07-02 19:37 ` Mark Brown
2014-07-02 19:42 ` Mark Brown [this message]
2014-07-03 5:49 ` Jean-Francois Moine
2014-07-03 10:44 ` Mark Brown
2014-07-03 11:34 ` Jean-Francois Moine
2014-07-03 11:59 ` Mark Brown
2014-07-03 13:28 ` Jean-Francois Moine
2014-07-03 13:43 ` Russell King - ARM Linux
[not found] ` <20140703134346.GW32514-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-07-03 15:29 ` Jean-Francois Moine
2014-07-03 15:43 ` Russell King - ARM Linux
2014-07-03 16:26 ` Jean-Francois Moine
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=20140702194252.GN410@sirena.org.uk \
--to=broonie@kernel.org \
--cc=airlied@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=moinejf@free.fr \
--cc=robdclark@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).