Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>,
	alsa-devel@alsa-project.org,  broonie@kernel.org
Cc: hdegoede@redhat.com, tiwai@suse.com, amadeuszx.slawinski@linux.intel.com
Subject: Re: [PATCH 0/4] ASoC: Intel: Mark BE DAIs as nonatomic for hsw and
Date: Fri, 24 Jun 2022 08:52:39 -0500	[thread overview]
Message-ID: <ac2b7d8b-a5be-4fac-169c-eaca185c9746@linux.intel.com> (raw)
In-Reply-To: <20220624134317.3656128-1-cezary.rojewski@intel.com>



On 6/24/22 08:43, Cezary Rojewski wrote:
> 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.

I don't think this is necessary, I was planning to demote this warning
to a simple dev_dbg or possibly remove this message entirely.

The BE DAIs can perfectly be declared as non-atomic in all Intel machine
drivers, except for SoundWire where there's a known delay during the
.trigger.

> 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(+)
> 

  parent reply	other threads:[~2022-06-24 14:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 13:43 [PATCH 0/4] ASoC: Intel: Mark BE DAIs as nonatomic for hsw and Cezary Rojewski
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 ` Pierre-Louis Bossart [this message]
2022-06-25  8:29   ` [PATCH 0/4] ASoC: Intel: Mark BE DAIs as nonatomic for hsw and 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=ac2b7d8b-a5be-4fac-169c-eaca185c9746@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=hdegoede@redhat.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