All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, liam.r.girdwood@linux.intel.com,
	alsa-devel@alsa-project.org, broonie@kernel.org,
	vkoul@kernel.org
Subject: Re: [PATCH] ASoC: Intel: cht-bsw-rt5672: allow for topology-defined codec-dai setup
Date: Sat, 28 Apr 2018 13:15:17 +0530	[thread overview]
Message-ID: <20180428074516.GJ6014@localhost> (raw)
In-Reply-To: <20180427213600.22634-1-pierre-louis.bossart@linux.intel.com>

On Fri, Apr 27, 2018 at 04:36:00PM -0500, Pierre-Louis Bossart wrote:
> Hard-coded setups conflict with topology defined ones. Move this code to
> codec_fixup so that SOF can override codec dai settings, e.g. to only use
> 2 channels.

Acked-by: Vinod Koul <vkoul@kernel.org>

-- 
~Vinod

      reply	other threads:[~2018-04-28  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 21:36 [PATCH] ASoC: Intel: cht-bsw-rt5672: allow for topology-defined codec-dai setup Pierre-Louis Bossart
2018-04-28  7:45 ` Vinod Koul [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=20180428074516.GJ6014@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.