alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Nicolin Chen <b42378@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: ASoC: codec: SPDIF only works with Tx/Rx seperate codec drivers?
Date: Fri, 12 Jul 2013 19:57:13 +0800	[thread overview]
Message-ID: <20130712115712.GG28915@MrMyself> (raw)
In-Reply-To: <20130712113353.GC24508@sirena.org.uk>

Thank you for the reply.

On Fri, Jul 12, 2013 at 12:33:53PM +0100, Mark Brown wrote:
> We could just merge them into a single driver easily enough.

Merge spdif_receiver.c and spdif_transmitter.c?
But each of them is being individually used by several drivers:
davinci/davinci-evm.c
samsung/smdk_spdif.c
spear/spdif_in.c
spear/spdif_out.c

If we merge these two files, it would break their functions.
Especially for spear's platform, seems they are using SPDIF
IN and OUT separately.

  reply	other threads:[~2013-07-12 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  8:30 ASoC: codec: SPDIF only works with Tx/Rx seperate codec drivers? Nicolin Chen
2013-07-12 11:33 ` Mark Brown
2013-07-12 11:57   ` Nicolin Chen [this message]
2013-07-12 14:29     ` Mark Brown
2013-07-12 14:26 ` Lars-Peter Clausen
2013-07-15  2:11   ` Nicolin Chen

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=20130712115712.GG28915@MrMyself \
    --to=b42378@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).