From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
<alsa-devel@alsa-project.org>
Cc: upstream@semihalf.com, harshapriya.n@intel.com, rad@semihalf.com,
tiwai@suse.com, hdegoede@redhat.com, broonie@kernel.org,
amadeuszx.slawinski@linux.intel.com, cujomalainey@chromium.org,
lma@semihalf.com
Subject: Re: [PATCH 13/17] ASoC: Intel: avs: Dynamic firmware resources management
Date: Mon, 28 Feb 2022 16:30:07 +0100 [thread overview]
Message-ID: <05e48c88-6faf-fd67-e051-b628222824a0@intel.com> (raw)
In-Reply-To: <66c8d1f7-f181-03ae-d5b1-17ec60b2b798@linux.intel.com>
On 2022-02-25 9:21 PM, Pierre-Louis Bossart wrote:
>>>> +static int avs_dsp_enable(struct avs_dev *adev, u32 core_mask)
>>>> +{
>>>> + u32 mask;
>>>> + int ret;
>>>> +
>>>> + ret = avs_dsp_core_enable(adev, core_mask);
>>>> + if (ret < 0)
>>>> + return ret;
>>>> +
>>>> + mask = core_mask & ~AVS_MAIN_CORE_MASK;
>>>
>>> so here BIT(MAIN_CORE) is zero in mask
>>
>>
>> What's wrong with AVS_MAIN_CORE_MASK being used explicitly?
>>
>>>> + if (!mask)
>>>> + /*
>>>> + * without main core, fw is dead anyway
>>>> + * so setting D0 for it is futile.
>>>
>>> I don't get the comment, you explicitly discarded the main core with
>>> your logical AND above, so this test means that all other non-main cores
>>> are disabled.
>>
>> There is no setting D0 for MAIN_CORE as firmware is not operational
>> without it. Firmware needs to be notified about D3 -> D0 transitions
>> only in case of non-MAIN_COREs.
>
> the comment was about 'without main core'.
>
> This is difficult to follow, because you've discarded the main code in
> the if (!mask), so that's an always-true case, which makes the rest of
> the explanations not so clear.
I'm afraid, not seeing the problem. It's clearly not always-true
statement as 'mask' can be non-zero after discarding the MAIN_CORE.
next prev parent reply other threads:[~2022-02-28 15:31 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 12:20 [PATCH 00/17] ASoC: Intel: AVS - Audio DSP for cAVS Cezary Rojewski
2022-02-07 12:20 ` [PATCH 01/17] ALSA: hda: Add helper macros for DSP capable devices Cezary Rojewski
2022-02-07 12:20 ` [PATCH 02/17] ASoC: Export DAI register and widget ctor and dctor functions Cezary Rojewski
2022-02-07 12:20 ` [PATCH 03/17] ASoC: Intel: Introduce AVS driver Cezary Rojewski
2022-02-24 23:55 ` Pierre-Louis Bossart
2022-02-25 16:56 ` Cezary Rojewski
2022-02-25 20:23 ` Pierre-Louis Bossart
2022-02-28 14:52 ` Cezary Rojewski
2022-02-07 12:20 ` [PATCH 04/17] ASoC: Intel: avs: Inter process communication Cezary Rojewski
2022-02-25 0:56 ` Pierre-Louis Bossart
2022-02-25 18:06 ` Cezary Rojewski
2022-02-25 20:37 ` Pierre-Louis Bossart
2022-02-28 15:19 ` Cezary Rojewski
2022-02-28 15:39 ` Cezary Rojewski
2022-02-07 12:20 ` [PATCH 05/17] ASoC: Intel: avs: Add code loading requests Cezary Rojewski
2022-02-25 1:02 ` Pierre-Louis Bossart
2022-02-25 18:08 ` Cezary Rojewski
2022-02-07 12:20 ` [PATCH 06/17] ASoC: Intel: avs: Add pipeline management requests Cezary Rojewski
2022-02-25 1:11 ` Pierre-Louis Bossart
2022-02-25 18:31 ` Cezary Rojewski
2022-02-25 20:42 ` Pierre-Louis Bossart
2022-02-28 15:25 ` Cezary Rojewski
2022-02-07 12:20 ` [PATCH 07/17] ASoC: Intel: avs: Add module " Cezary Rojewski
2022-02-25 1:27 ` Pierre-Louis Bossart
2022-02-25 18:50 ` Cezary Rojewski
2022-02-25 20:44 ` Pierre-Louis Bossart
2022-02-28 15:26 ` Cezary Rojewski
2022-02-07 12:20 ` [PATCH 08/17] ASoC: Intel: avs: Add power " Cezary Rojewski
2022-02-25 1:37 ` Pierre-Louis Bossart
2022-02-25 19:08 ` Cezary Rojewski
2022-02-25 20:46 ` Pierre-Louis Bossart
2022-02-28 15:28 ` Cezary Rojewski
2022-02-07 12:21 ` [PATCH 09/17] ASoC: Intel: avs: Add ROM requests Cezary Rojewski
2022-02-25 1:42 ` Pierre-Louis Bossart
2022-02-25 19:19 ` Cezary Rojewski
2022-02-07 12:21 ` [PATCH 10/17] ASoC: Intel: avs: Add basefw runtime-parameter requests Cezary Rojewski
2022-02-07 12:21 ` [PATCH 11/17] ASoC: Intel: avs: Firmware resources management utilities Cezary Rojewski
2022-02-25 1:53 ` Pierre-Louis Bossart
2022-02-25 19:20 ` Cezary Rojewski
2022-02-07 12:21 ` [PATCH 12/17] ASoC: Intel: avs: Declare module configuration types Cezary Rojewski
2022-02-07 12:21 ` [PATCH 13/17] ASoC: Intel: avs: Dynamic firmware resources management Cezary Rojewski
2022-02-25 2:02 ` Pierre-Louis Bossart
2022-02-25 19:27 ` Cezary Rojewski
2022-02-25 20:21 ` Pierre-Louis Bossart
2022-02-28 15:30 ` Cezary Rojewski [this message]
2022-02-28 17:20 ` Pierre-Louis Bossart
2022-02-07 12:21 ` [PATCH 14/17] ASoC: Intel: avs: General code loading flow Cezary Rojewski
2022-02-25 2:15 ` Pierre-Louis Bossart
2022-02-25 19:37 ` Cezary Rojewski
2022-02-07 12:21 ` [PATCH 15/17] ASoC: Intel: avs: Implement CLDMA transfer Cezary Rojewski
2022-02-25 2:18 ` Pierre-Louis Bossart
2022-02-25 19:38 ` Cezary Rojewski
2022-02-07 12:21 ` [PATCH 16/17] ASoC: Intel: avs: Code loading over CLDMA Cezary Rojewski
2022-02-25 2:21 ` Pierre-Louis Bossart
2022-02-25 19:38 ` Cezary Rojewski
2022-02-07 12:21 ` [PATCH 17/17] ASoC: Intel: avs: Code loading over HDA Cezary Rojewski
2022-02-21 11:51 ` [PATCH 00/17] ASoC: Intel: AVS - Audio DSP for cAVS Cezary Rojewski
2022-02-25 2:35 ` Pierre-Louis Bossart
2022-02-25 15:44 ` Cezary Rojewski
2022-02-25 16:33 ` Pierre-Louis Bossart
2022-02-25 18:07 ` 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=05e48c88-6faf-fd67-e051-b628222824a0@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cujomalainey@chromium.org \
--cc=harshapriya.n@intel.com \
--cc=hdegoede@redhat.com \
--cc=lma@semihalf.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rad@semihalf.com \
--cc=tiwai@suse.com \
--cc=upstream@semihalf.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.