From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Mark Brown <broonie@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: hdegoede@redhat.com, alsa-devel@alsa-project.org, tiwai@suse.com,
amadeuszx.slawinski@linux.intel.com
Subject: Re: [PATCH 0/4] ASoC: Intel: Mark BE DAIs as nonatomic for hsw and
Date: Sat, 9 Jul 2022 10:51:19 +0200 [thread overview]
Message-ID: <925a59e0-41d6-07d1-b9f5-8d8afbcedca0@intel.com> (raw)
In-Reply-To: <YshQ8N8Rx7Hizk8B@sirena.org.uk>
On 2022-07-08 5:44 PM, Mark Brown wrote:
> On Mon, Jun 27, 2022 at 09:45:30AM -0500, Pierre-Louis Bossart wrote:
>> On 6/25/22 03:29, Cezary Rojewski wrote:
>
>>> Warning is one thing, but will you be also getting rid of the
>>> if-statement in soc-pcm.c that actually forces nonatomic=1 on BE when FE
>>> is already declared as such? If the if-statement stays, I believe the
>>> declaring BE DAIs 'correctly' in the way to go.
>
>> I meant just removing the dev_warn() only.
>
>> See https://github.com/thesofproject/linux/pull/3723
>
> Is something going to be upstreamed here? I don't really mind which
> solution is adopted here but right now Cezary's patches are the ones
> that were posted upstream.
My 2 cents:
Both series can co-exist. We should still encourage people to configure
their DAIs properly so the if-statements like the one forcing
->nonatomic=1 in time are gone.
next prev parent reply other threads:[~2022-07-09 8:52 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 ` [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 [this message]
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=925a59e0-41d6-07d1-b9f5-8d8afbcedca0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.