From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolin Chen Subject: ASoC: codec: SPDIF only works with Tx/Rx seperate codec drivers? Date: Fri, 12 Jul 2013 16:30:31 +0800 Message-ID: <20130712083030.GA28555@MrMyself> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by alsa0.perex.cz (Postfix) with ESMTP id 8D8E3265109 for ; Fri, 12 Jul 2013 10:49:52 +0200 (CEST) Content-Disposition: inline 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: broonie@kernel.org Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Hi Mark, I've a little question about SPDIF codec drivers. I found there're spdif_receiver.c and spdif_transmitter.c, two files, in sound/soc/codecs directory. So it looks like SPDIF module would work separately as one IN device and one OUT device, for example: dts/spear1340.dtsi: spdif-in@d0100000 { dts/spear1340.dtsi: compatible = "st,spdif-in"; dts/spear1340.dtsi: spdif-out@d0000000 { dts/spear1340.dtsi: compatible = "st,spdif-out"; But the question is what if a SPDIF module have both Tx and Rx function in one simple CPU DAI. Is that okay to add a new codec driver for this situation? Actually I'm gonna prepare some patches to add Freescale SPDIF drivers. But this needs to create a brand new dummy SPDIF codec driver, which's some kinda same as spdif_receiver/transmitter.c but quite different in the supports of SAMPLE_RATE/FORMAT and IN/OUT-in-one integration. So I just want to make sure if this'll be okay. Thank you. And looking forward to your reply. Nicolin Chen