[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <866ef71f-8794-558b-bd4d-c491ab4effc4@linux.intel.com>
Date: Mon, 27 Apr 2020 12:59:20 -0500
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Brent Lu <brent.lu@...el.com>, alsa-devel@...a-project.org
Cc: Guennadi Liakhovetski <guennadi.liakhovetski@...ux.intel.com>,
Cezary Rojewski <cezary.rojewski@...el.com>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
linux-kernel@...r.kernel.org, Takashi Iwai <tiwai@...e.com>,
Jie Yang <yang.jie@...ux.intel.com>,
Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
Ben Zhang <benzh@...omium.org>,
Mac Chiang <mac.chiang@...el.com>,
Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v2 0/3] add channel constraint for BDW machine drivers
On 4/27/20 12:13 PM, Brent Lu wrote:
> The machine driver bdw-rt5650 (for Google buddy) supports 2 or 4-channel
> recording while other two drivers support only 2-channel recording. HW
> constraints are implemented to reflect the hardware limitation on BDW
> platform.
>
> Changes since v1:
> - Change the patch title.
> - Remove the DUAL_CHANNEL and QUAD_CHANNEL macros which are too obvious.
> - Follow the naming convertion, using 'bdw_rt5650_' and 'bdw_rt5677_' to
> name startup functions.
> - Refine the comments in startup functions.
> - Redesign the bdw_rt5650_fe_startup() function for readability.
> - Add an assignment to initialize runtime->hw.channels_max variable.
For the series
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
> Brent Lu (3):
> ASoC: bdw-rt5677: add channel constraint
> ASoC: bdw-rt5650: add channel constraint
> ASoC: broadwell: add channel constraint
>
> sound/soc/intel/boards/bdw-rt5650.c | 29 +++++++++++++++++++++++++++++
> sound/soc/intel/boards/bdw-rt5677.c | 26 ++++++++++++++++++++++++++
> sound/soc/intel/boards/broadwell.c | 26 ++++++++++++++++++++++++++
> 3 files changed, 81 insertions(+)
>
Powered by blists - more mailing lists