From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Banajit Goswami <bgoswami@quicinc.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Vinod Koul <vkoul@kernel.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: wcd9335: fix order of Slimbus unprepare/disable
Date: Wed, 21 Sep 2022 17:11:24 +0200 [thread overview]
Message-ID: <fd74e77c-f3d3-1f09-2e5a-0a94e2a3eeea@linux.intel.com> (raw)
In-Reply-To: <9a210b04-2ff2-df98-ad1a-89e9d8b0f686@linaro.org>
On 9/21/22 17:08, Krzysztof Kozlowski wrote:
> On 21/09/2022 17:06, Krzysztof Kozlowski wrote:
>> On 21/09/2022 17:05, Pierre-Louis Bossart wrote:
>>>> diff --git a/sound/soc/codecs/wcd9335.c b/sound/soc/codecs/wcd9335.c
>>>> index 06c6adbe5920..d2548fdf9ae5 100644
>>>> --- a/sound/soc/codecs/wcd9335.c
>>>> +++ b/sound/soc/codecs/wcd9335.c
>>>> @@ -1972,8 +1972,8 @@ static int wcd9335_trigger(struct snd_pcm_substream *substream, int cmd,
>>>> case SNDRV_PCM_TRIGGER_STOP:
>>>> case SNDRV_PCM_TRIGGER_SUSPEND:
>>>> case SNDRV_PCM_TRIGGER_PAUSE_PUSH:
>>>> - slim_stream_unprepare(dai_data->sruntime);
>>>> slim_stream_disable(dai_data->sruntime);
>>>> + slim_stream_unprepare(dai_data->sruntime);
>>>
>>> This looks logical but different from what the kernel doc says:
>>>
>>> /**
>>> * slim_stream_disable() - Disable a SLIMbus Stream
>>> *
>>> * @stream: instance of slim stream runtime to disable
>>> *
>>> * This API will disable all the ports and channels associated with
>>> * SLIMbus stream
>>> *
>>> * Return: zero on success and error code on failure. From ASoC DPCM
>>> framework,
>>> * this state is linked to trigger() pause operation.
>>> */
>>>
>>> /**
>>> * slim_stream_unprepare() - Un-prepare a SLIMbus Stream
>>> *
>>> * @stream: instance of slim stream runtime to unprepare
>>> *
>>> * This API will un allocate all the ports and channels associated with
>>> * SLIMbus stream
>>
>> You mean this piece of doc? Indeed looks inaccurate. I'll update it.
>
> Wait, no, this is correct. Please point to what is wrong in kernel doc.
> I don't see it. :(
the TRIGGER_STOP and TRIGGER_PAUSE_PUSH do the same thing. There is no
specific mapping of disable() to TRIGGER_STOP and unprepare() to
TRIGGER_PAUSE_PUSH as the documentation hints at.
next prev parent reply other threads:[~2022-09-21 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 14:53 [PATCH 1/2] ASoC: wcd9335: fix order of Slimbus unprepare/disable Krzysztof Kozlowski
2022-09-21 14:53 ` [PATCH 2/2] ASoC: wcd934x: " Krzysztof Kozlowski
2022-09-22 21:38 ` Srinivas Kandagatla
2022-09-21 15:05 ` [PATCH 1/2] ASoC: wcd9335: " Pierre-Louis Bossart
2022-09-21 15:06 ` Krzysztof Kozlowski
2022-09-21 15:08 ` Krzysztof Kozlowski
2022-09-21 15:11 ` Pierre-Louis Bossart [this message]
2022-09-21 15:19 ` Krzysztof Kozlowski
2022-09-21 15:25 ` Pierre-Louis Bossart
2022-09-21 15:28 ` Krzysztof Kozlowski
2022-09-22 21:38 ` Srinivas Kandagatla
2022-09-23 17: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=fd74e77c-f3d3-1f09-2e5a-0a94e2a3eeea@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
/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