From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: Question about SuperH HDMI sound Date: Fri, 9 Jul 2010 10:52:59 +0900 Message-ID: <20100709015258.GA7774@opensource.wolfsonmicro.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource2.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 4B0D72441D for ; Fri, 9 Jul 2010 03:52:51 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Kuninori Morimoto Cc: Linux-ALSA , Guennadi List-Id: alsa-devel@alsa-project.org On Fri, Jul 09, 2010 at 09:19:24AM +0900, Kuninori Morimoto wrote: > HDMI "video" support file is under "drivers/video/sh_mobile_hdmi.c" > Should I add sound support in it ? or under "sound/soc/codecs" ? One or the other :) On PCs there is support for HDMI audio within the HDA subsystem so it would seem reasonable to add the support in ASoC if the hardware shares anything with the rest of the audio hardware in the SoC. It may also make sense to provide a driver which presents both video and audio interfaces, depending on how the hardware is structured. If the hardware doesn't share anything with the other audio hardware then it might be as easy to just implement outside ASoC as a regular ALSA driver since HDMI "CODECs" are usually the TVs or other remote devices that are plugged in to the system rather than a component of the system itself so the CODEC/CPU split of ASoC isn't such a clear benefit.