From: "Koul, Vinod" <vinod.koul@intel.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: "lars@metafoo.de" <lars@metafoo.de>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
Patches Audio <patches.audio@intel.com>,
"arnaud.pouliquen@st.com" <arnaud.pouliquen@st.com>,
"liam.r.girdwood@linux.intel.com"
<liam.r.girdwood@linux.intel.com>,
"tiwai@suse.de" <tiwai@suse.de>,
"broonie@kernel.org" <broonie@kernel.org>,
"ykk@rock-chips.com" <ykk@rock-chips.com>
Subject: Re: [RFC 0/4] ASoC: Add HDA HDMI codec driver
Date: Tue, 13 Oct 2015 13:08:27 +0000 [thread overview]
Message-ID: <1444741706.2926.16.camel@intel.com> (raw)
In-Reply-To: <1444393729-19745-1-git-send-email-vinod.koul@intel.com>
On Fri, 2015-10-09 at 13:28 +0100, Vinod Koul wrote:
> Yes, this patch series attempts to add yet another HDMI driver to
> ASoC. This codec appears as HDA codec over HDA link. Although
> the codec reside in display we have a HDA link from audio block
> to this codec. The communication to codec is over HDA link
>
> Thanks to i915 component infrastructure, we do not need to worry
> about keeping the codec on, this is done by i915 for us.
>
> Based on discussion with Mark here at ELCE and other attempts by
> various folks on HDMI, I wanted to show on list the stuff we have
> done and discuss and try to see how we converge various attempts
>
> The driver here only supports stereo and doesn't do multichannel
> just yet, will add later once we converge here. The support for
> using i915 component notification by David will be added later
> on.
Apart from comments from Russell I didn't get any other comments.
So as a solution for many HDMI approaches in ASoC should we converge on usage of
component framework for talking to display and not have hard dependency to display
code. That sounds okay on X86 but I am not sure if other arch's can do this...
Also as discussed with Russell, we should use drivers/video/hdmi.c for HDMI
infoframes and sound/core/pcm_drm_eld.c for eld parsing. No open coding these :)
Lastly, sink properties should be the properties of the connected device as read from
ELD. That seems okay to me, other please chime in
I will send updated patchset based on above.
Thanks
--
~Vinod
next prev parent reply other threads:[~2015-10-13 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 12:28 [RFC 0/4] ASoC: Add HDA HDMI codec driver Vinod Koul
2015-10-09 12:28 ` [RFC 1/4] ASoC: hdac-hdmi: Add hdmi driver Vinod Koul
2015-10-09 12:28 ` [RFC 2/4] ASoC: hdac_hdmi: Add PM support for HDMI Vinod Koul
2015-10-09 12:28 ` [RFC 3/4] ASoC: hdac_hdmi: Add hdac hdmi dai ops Vinod Koul
2015-10-09 12:28 ` [RFC 4/4] ASoC: hdac_hdmi: Setup and start infoframe Vinod Koul
2015-10-09 12:49 ` Russell King - ARM Linux
2015-10-09 14:51 ` Vinod Koul
2015-10-09 12:52 ` [RFC 0/4] ASoC: Add HDA HDMI codec driver Russell King - ARM Linux
2015-10-09 15:17 ` Vinod Koul
2015-10-09 15:28 ` Russell King - ARM Linux
2015-10-09 15:33 ` Vinod Koul
2015-10-13 13:08 ` Koul, Vinod [this message]
2015-10-20 0:15 ` Mark Brown
2015-10-20 3:29 ` Vinod Koul
2015-10-22 2:22 ` Hui Wang
2015-11-05 5:56 ` Vinod Koul
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=1444741706.2926.16.camel@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux@arm.linux.org.uk \
--cc=patches.audio@intel.com \
--cc=tiwai@suse.de \
--cc=ykk@rock-chips.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