alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
	linux@arm.linux.org.uk, lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: imx-spdif: Use snd-soc-dummy CODEC driver to link card
Date: Wed, 1 Jan 2014 15:12:32 +0800	[thread overview]
Message-ID: <20140101071230.GA7436@MrMyself> (raw)
In-Reply-To: <20131231163422.GJ31886@sirena.org.uk>

On Tue, Dec 31, 2013 at 04:34:22PM +0000, Mark Brown wrote:
> On Mon, Dec 23, 2013 at 05:28:53PM +0800, Nicolin Chen wrote:
> > This is a quick fix for the below two issues when building spdif as modules.
> 
> Good thinking - this is a smart way of dealing with the issue.  It'll
> mean that we don't have the application specific constraints but those
> could be added back in the driver later or we could do an explicit
> S/PDIF CODEC in the same style as dummy.  Applied, thanks.

Yes, it can circumvent all the unnecessary problems we've been through here
even though the CODEC name 'dummy' doesn't look so flawless. The application
constraints, what I understand should be the supporting formats and rates,
have been already ensured in the CPU DAI driver, so we might not need to worry
for the CODEC one.

Thank you for the suggestion of dummy driver at the first place and..
Happy new year :)
Nicolin Chen

      reply	other threads:[~2014-01-01  7:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  9:28 [PATCH] ASoC: imx-spdif: Use snd-soc-dummy CODEC driver to link card Nicolin Chen
2013-12-31 16:34 ` Mark Brown
2014-01-01  7:12   ` Nicolin Chen [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=20140101071230.GA7436@MrMyself \
    --to=guangyu.chen@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux@arm.linux.org.uk \
    --cc=tiwai@suse.de \
    /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).