[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CF33C36214C39B4496568E5578BE70C74031B9FD@PGSMSX108.gar.corp.intel.com>
Date: Mon, 21 Oct 2019 02:47:34 +0000
From: "Lu, Brent" <brent.lu@...el.com>
To: "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>
CC: "Rojewski, Cezary" <cezary.rojewski@...el.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
Jie Yang <yang.jie@...ux.intel.com>,
"Mark Brown" <broonie@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
"Zavras, Alexios" <alexios.zavras@...el.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@...esas.com>,
Thomas Gleixner <tglx@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] ASoC: bdw-rt5677: enable runtime channel merge
> Subject: [PATCH] ASoC: bdw-rt5677: enable runtime channel merge
>
> In the DAI link "Capture PCM", the FE DAI "Capture Pin" supports 4-channel
> capture but the BE DAI supports only 2-channel capture. To fix the channel
> mismatch, we need to enable the runtime channel merge for this DAI link.
>
Hi Pierre,
This patch is for the same issue discussed in the following thread:
https://patchwork.kernel.org/patch/11134167/
We enable the runtime channel merge for the DMIC DAI instead of adding a
machine driver constraint. It's working good on chrome's 3.14 branch (which
requires some backport for the runtime channel merge feature). Please let
me know if this implementation is correct for the FE/BE mismatch problem.
Thanks.
Regards,
Brent
Powered by blists - more mailing lists