From: Vinod Koul <vinod.koul@intel.com>
To: Hui Wang <hui.wang@canonical.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
tiwai@suse.de, Arnaud Pouliquen <arnaud.pouliquen@st.com>,
liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
broonie@kernel.org, Yakir Yang <ykk@rock-chips.com>
Subject: Re: [RFC 0/4] ASoC: Add HDA HDMI codec driver
Date: Thu, 5 Nov 2015 11:26:15 +0530 [thread overview]
Message-ID: <20151105055614.GQ12910@localhost> (raw)
In-Reply-To: <56284868.2040008@canonical.com>
On Thu, Oct 22, 2015 at 10:22:32AM +0800, Hui Wang wrote:
> On 10/09/2015 08:28 PM, 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.
> >
> >Question/Comments welcome...
> Hello Vinod,
>
> Is this driver supposed to be working for Bay Trail and Cherry Trail
> as well? Right now we have an OEM product based on the Cherry Trail
> platform, there is no analog audio codec on it, the only audio
> device on the product is the HDMI audio (just like this one http://mailman.alsa-project.org/pipermail/alsa-devel/2015-August/096979.html).
> So could you please share some information about the support status
> for Cherry Trail HDMI audio, e.g. is the driver developed by your
> team? Is it still an out-of-tree driver right now? And do you plan
> to upstream it under the hdac_hdmi.c framework?
Hello Hui,
No this driver is applicable to Skylake onwards. I believe canonical already
has a driver for HDMI BYT and you can use that and btw David knows about it
--
~Vinod
prev parent reply other threads:[~2015-11-05 5:52 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
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 [this message]
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=20151105055614.GQ12910@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=hui.wang@canonical.com \
--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 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.