From: Brent Lu <brent.lu@intel.com>
To: alsa-devel@alsa-project.org
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Ben Zhang <benzh@chromium.org>,
Mac Chiang <mac.chiang@intel.com>,
Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Brent Lu <brent.lu@intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] add channel constraint for BDW machine drivers
Date: Mon, 27 Apr 2020 16:37:15 +0800 [thread overview]
Message-ID: <1587976638-29806-1-git-send-email-brent.lu@intel.com> (raw)
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.
Brent Lu (3):
ASoC: bdw-rt5677: channel constraint support
ASoC: bdw-rt5650: channel constraint support
ASoC: broadwell: channel constraint support
sound/soc/intel/boards/bdw-rt5650.c | 34 ++++++++++++++++++++++++++++++++++
sound/soc/intel/boards/bdw-rt5677.c | 33 +++++++++++++++++++++++++++++++++
sound/soc/intel/boards/broadwell.c | 33 +++++++++++++++++++++++++++++++++
3 files changed, 100 insertions(+)
--
2.7.4
next reply other threads:[~2020-04-27 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 8:37 Brent Lu [this message]
2020-04-27 8:37 ` [PATCH 1/3] ASoC: bdw-rt5677: channel constraint support Brent Lu
2020-04-27 10:58 ` Cezary Rojewski
2020-04-27 8:37 ` [PATCH 2/3] ASoC: bdw-rt5650: " Brent Lu
2020-04-27 10:58 ` Cezary Rojewski
2020-04-27 15:30 ` Lu, Brent
2020-04-27 8:37 ` [PATCH 3/3] ASoC: broadwell: " Brent Lu
2020-04-27 10:58 ` Cezary Rojewski
2020-04-27 11:01 ` [PATCH 0/3] add channel constraint for BDW machine drivers Cezary Rojewski
2020-04-27 11:15 ` Cezary Rojewski
2020-04-27 15:10 ` Lu, Brent
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=1587976638-29806-1-git-send-email-brent.lu@intel.com \
--to=brent.lu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=benzh@chromium.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mac.chiang@intel.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.com \
/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