From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Jean-Francois Moine" <moinejf@free.fr>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"Russell King - ARM Linux " <linux@arm.linux.org.uk>,
"David Airlie" <airlied@linux.ie>,
"Arnaud Pouliquen" <arnaud.pouliquen@st.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"peter.ujfalusi@ti.com" <peter.ujfalusi@ti.com>,
"tomi.valkeinen@ti.com" <tomi.valkeinen@ti.com>,
"Jyri Sarha" <jsarha@ti.com>
Subject: Re: HDMI codec, way forward?
Date: Sun, 18 Oct 2015 20:37:39 +0530 [thread overview]
Message-ID: <20151018150739.GO27370@localhost> (raw)
In-Reply-To: <20151016141525.GM14956@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 773 bytes --]
On Fri, Oct 16, 2015 at 03:15:25PM +0100, Mark Brown wrote:
> On Fri, Oct 16, 2015 at 03:51:40PM +0200, Arnaud Pouliquen wrote:
>
> > - Does trigger is needed when CPU-DAI is master on bus?
> > Otherwise how to inform HDMI that I2S bus is no more clocked? I'm not
> > sure that mute is sufficient for all hardwares... For instance for my
> > hardware CTS parameter is hardware computed based on I2S L/R clock.
>
> I'd expect us to be always calling trigger - is there some debate on
> this? Obviously since it's called in atomic context it can be difficult
> to use but we should be notifying.
If the question is only on trigger being non atomic, we certainly allow that
now, we can specify that by having dailinks's nonatomic flag as true
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-10-18 15:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 11:50 HDMI codec, way forward? Jyri Sarha
2015-10-16 12:31 ` Lars-Peter Clausen
2015-10-16 12:43 ` [alsa-devel] " Takashi Iwai
2015-10-16 13:37 ` Russell King - ARM Linux
2015-10-16 14:12 ` Mark Brown
2015-10-18 15:08 ` Vinod Koul
2015-10-18 15:20 ` Russell King - ARM Linux
2015-10-18 16:13 ` Vinod Koul
2015-10-18 16:22 ` Russell King - ARM Linux
2015-10-18 17:16 ` Russell King - ARM Linux
2015-10-19 13:20 ` [alsa-devel] " Takashi Iwai
2015-10-20 3:38 ` Vinod Koul
2015-10-20 8:08 ` [alsa-devel] " Russell King - ARM Linux
2015-10-20 14:01 ` Vinod Koul
2015-10-21 9:11 ` [alsa-devel] " Jani Nikula
2015-10-21 15:52 ` Vinod Koul
2015-10-21 9:27 ` [alsa-devel] " Russell King - ARM Linux
2015-10-21 13:41 ` Takashi Iwai
2015-10-21 14:03 ` Russell King - ARM Linux
2015-10-21 14:10 ` Takashi Iwai
2015-10-21 14:37 ` Takashi Iwai
2015-10-21 15:36 ` Daniel Vetter
2015-10-21 16:46 ` Takashi Iwai
2015-10-21 16:48 ` Takashi Iwai
2015-10-21 16:50 ` Takashi Iwai
2015-10-21 14:37 ` Russell King - ARM Linux
2015-10-21 16:19 ` Vinod Koul
2015-10-21 17:34 ` Russell King - ARM Linux
2015-10-21 17:59 ` [alsa-devel] " Takashi Iwai
2015-10-21 18:19 ` Russell King - ARM Linux
2015-10-21 20:37 ` Takashi Iwai
2015-10-21 21:04 ` Russell King - ARM Linux
2015-10-22 7:18 ` Daniel Vetter
2015-10-16 14:06 ` Mark Brown
2015-10-18 15:02 ` Vinod Koul
2015-10-19 20:14 ` Jyri Sarha
2015-10-16 13:51 ` Arnaud Pouliquen
2015-10-16 14:15 ` Mark Brown
2015-10-18 15:07 ` Vinod Koul [this message]
2015-10-19 13:10 ` Jyri Sarha
2015-10-19 13:31 ` Russell King - ARM Linux
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=20151018150739.GO27370@localhost \
--to=vinod.koul@intel.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux@arm.linux.org.uk \
--cc=moinejf@free.fr \
--cc=peter.ujfalusi@ti.com \
--cc=tomi.valkeinen@ti.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.