From: Cezary Rojewski <cezary.rojewski@intel.com>
To: alsa-devel@alsa-project.org, broonie@kernel.org
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
pierre-louis.bossart@linux.intel.com, tiwai@suse.com,
hdegoede@redhat.com, amadeuszx.slawinski@linux.intel.com
Subject: [PATCH 0/4] ASoC: Intel: Mark BE DAIs as nonatomic for hsw and
Date: Fri, 24 Jun 2022 15:43:13 +0200 [thread overview]
Message-ID: <20220624134317.3656128-1-cezary.rojewski@intel.com> (raw)
Address the warning: "Codec: dpcm_be_connect: FE is nonatomic but BE is
not, forcing BE as nonatomic" by marking BE DAI as nonatomic. Aligns
with what is already done for FE DAIs.
This patchset iterates the change over all HSW and BDW related machine
board drivers.
Cezary Rojewski (4):
ASoC: Intel: hsw_rt5640: Mark BE DAI as nonatomic
ASoC: Intel: bdw_rt286: Mark BE DAI as nonatomic
ASoC: Intel: bdw_rt5650: Mark BE DAI as nonatomic
ASoC: Intel: bdw_rt5677: Mark BE DAI as nonatomic
sound/soc/intel/boards/bdw-rt5650.c | 1 +
sound/soc/intel/boards/bdw-rt5677.c | 1 +
sound/soc/intel/boards/bdw_rt286.c | 1 +
sound/soc/intel/boards/hsw_rt5640.c | 1 +
4 files changed, 4 insertions(+)
--
2.25.1
next reply other threads:[~2022-06-24 13:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 13:43 Cezary Rojewski [this message]
2022-06-24 13:43 ` [PATCH 1/4] ASoC: Intel: hsw_rt5640: Mark BE DAI as nonatomic Cezary Rojewski
2022-06-24 13:43 ` [PATCH 2/4] ASoC: Intel: bdw_rt286: " Cezary Rojewski
2022-06-24 13:43 ` [PATCH 3/4] ASoC: Intel: bdw_rt5650: " Cezary Rojewski
2022-06-24 13:43 ` [PATCH 4/4] ASoC: Intel: bdw_rt5677: " Cezary Rojewski
2022-06-24 13:52 ` [PATCH 0/4] ASoC: Intel: Mark BE DAIs as nonatomic for hsw and Pierre-Louis Bossart
2022-06-25 8:29 ` Cezary Rojewski
2022-06-27 14:45 ` Pierre-Louis Bossart
2022-06-27 15:41 ` Cezary Rojewski
2022-06-27 15:59 ` Pierre-Louis Bossart
2022-06-27 16:13 ` Cezary Rojewski
2022-07-08 15:44 ` Mark Brown
2022-07-09 8:51 ` Cezary Rojewski
2022-07-15 18:56 ` Mark Brown
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=20220624134317.3656128-1-cezary.rojewski@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=hdegoede@redhat.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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