From: Srinivasa Rao Mandadapu <srivasam@codeaurora.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
agross@kernel.org, bjorn.andersson@linaro.org,
lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
plai@codeaurora.org, bgoswami@codeaurora.org, perex@perex.cz,
tiwai@suse.com, rohitkr@codeaurora.org,
linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
swboyd@chromium.org, judyhsiao@chromium.org
Subject: Re: [PATCH v2] ASoC: qcom: lpass-platform: Reset irq clear reg post handling interrupts
Date: Thu, 9 Sep 2021 17:41:18 +0530 [thread overview]
Message-ID: <49c8a61c-a0e3-3068-0f33-40eb18b56f79@codeaurora.org> (raw)
In-Reply-To: <c29802c9-4577-87bd-b843-8540588c6d06@linaro.org>
Thanks for Your time Srini!!
On 9/8/2021 9:37 PM, Srinivas Kandagatla wrote:
>
>
> On 08/09/2021 15:25, Srinivasa Rao Mandadapu wrote:
>> Update interrupt clear register with reset value after addressing
>> all interrupts. This is to fix playback or capture hanging issue in
>> simultaneous playback and capture usecase.
>
> Could explain bit more about the issue.
> Specifically which interrupt and which ports is this issue seen.
The test case is repeated test of simultaneous playback and capture on
audio jack. i.e. 10 sec playback and 10 secs Capture.
i.e. sequence is Capture --> Playback, Capture -> Playback
In interrupt handler reading IRQ status reg and processing all the bits
in loop. By the time loop ends in handler,
another capture interrupt is raised and it's never getting cleared and
whole test case is getting hanged.
>
>>
>> Fixes: 4f629e4b8705f ("ASoC: qcom: Add ability to handle interrupts
>> per dma channel")
>>
>> Signed-off-by: Srinivasa Rao Mandadapu <srivasam@codeaurora.org>
>> ---
>> Changes since v1:
>> -- Update comments Header information with fixes tag
>>
>> sound/soc/qcom/lpass-platform.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/sound/soc/qcom/lpass-platform.c
>> b/sound/soc/qcom/lpass-platform.c
>> index f9df76d37858..1a0a4b0b1a03 100644
>> --- a/sound/soc/qcom/lpass-platform.c
>> +++ b/sound/soc/qcom/lpass-platform.c
>> @@ -749,6 +749,12 @@ static irqreturn_t lpass_platform_lpaif_irq(int
>> irq, void *data)
>> }
>> }
>> + rv = regmap_write(drvdata->lpaif_map, LPAIF_IRQCLEAR_REG(v,
>> LPAIF_IRQ_PORT_HOST), 0x0);
>
> Writing 1 to a bit of this register will clear the corresponding
> latched interrupt. So I don't really understand how writing 0 is
> really helping here?
Yes. Your point is valid. But use-case passed with below patch and this
change. will revert this change and check again with only below patch .
https://patchwork.kernel.org/project/alsa-devel/patch/20210524142114.18676-1-srivasam@codeaurora.org/
<https://www.google.com/url?q=https://patchwork.kernel.org/project/alsa-devel/patch/20210524142114.18676-1-srivasam@codeaurora.org/&sa=D&usg=AOvVaw3VEq8XuEI8cJkNpAxTm3d2>
>
> Do you have this patch in your tree?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound/soc/qcom/lpass-cpu.c?h=v5.14&id=6a7f5bd6185e1c86256d5e52c3bb7a4d390d6e19
>
yes. This patch is available.
> --srini
>
>> + if (rv) {
>> + pr_err("error writing to irqstat reg: %d\n", rv);
>> + return IRQ_NONE;
>> + }
>> +
>> return IRQ_HANDLED;
>> }
>>
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.,
is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2021-09-09 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 14:25 [PATCH v2] ASoC: qcom: lpass-platform: Reset irq clear reg post handling interrupts Srinivasa Rao Mandadapu
2021-09-08 16:07 ` Srinivas Kandagatla
2021-09-09 12:11 ` Srinivasa Rao Mandadapu [this message]
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=49c8a61c-a0e3-3068-0f33-40eb18b56f79@codeaurora.org \
--to=srivasam@codeaurora.org \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=judyhsiao@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=plai@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=rohitkr@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.org \
--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.