From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vinod Koul Subject: Re: [RFC 0/4] ASoC: Add HDA HDMI codec driver Date: Thu, 5 Nov 2015 11:26:15 +0530 Message-ID: <20151105055614.GQ12910@localhost> References: <1444393729-19745-1-git-send-email-vinod.koul@intel.com> <56284868.2040008@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by alsa0.perex.cz (Postfix) with ESMTP id 365A2260560 for ; Thu, 5 Nov 2015 06:52:45 +0100 (CET) Content-Disposition: inline In-Reply-To: <56284868.2040008@canonical.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Hui Wang Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen , Russell King - ARM Linux , tiwai@suse.de, Arnaud Pouliquen , liam.r.girdwood@linux.intel.com, patches.audio@intel.com, broonie@kernel.org, Yakir Yang List-Id: alsa-devel@alsa-project.org 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