From: Prasad Kumpatla <quic_pkumpatl@quicinc.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
<linux-kernel@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
'Linux Samsung SOC' <linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCH v2] regmap-irq: Use regmap_irq_update_bits instead of regmap_write
Date: Wed, 9 Feb 2022 14:11:13 +0530 [thread overview]
Message-ID: <c055e4e8-fd11-49e9-c7a9-bf2f1ec9de36@quicinc.com> (raw)
In-Reply-To: <39f1b598-58ca-1e3d-3065-8dd692ee7c9f@samsung.com>
On 2/8/2022 5:59 PM, Marek Szyprowski wrote:
> There is something wrong with this patch. Since it landed in linux-next
> (20220204) I get an interrupt storm on two of my test devices:
>
> 1. ARM 32bit Exynos4412-based Trats2 ("wm8994-codec wm8994-codec: FIFO
> error" message)
>
> 2. ARM 64bit Exynos5433-based TM2e ("arizona spi1.0: Mixer dropped
> sample" message)
>
> Definitely the interrupts are not acknowledged properly. Once I find
> some spare time, I will check it further which regmap configuration
> triggers the issue, but it is definitely related to this patch.
> Reverting it on top of current linux-next fixes the issue.
Change is needed to handle the interrupt ack properly to clear the ack.
I observed that the regmap_irq_update_bits() writes the register only if
it finds a difference b/w existing reg value to update reg value.
This may be causing the interrupt storm issue mentioned above.
Setting the mask_writeonly flag to 1, to force write the register may
resolve the interrupt storm issue.
--Prasad
prev parent reply other threads:[~2022-02-09 8:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 14:29 Prasad Kumpatla
2022-02-03 12:52 ` Mark Brown
[not found] ` <CGME20220208122955eucas1p2d4e32f51224242e9ebd0bce58b9c04ca@eucas1p2.samsung.com>
2022-02-08 12:29 ` Marek Szyprowski
2022-02-08 13:39 ` Charles Keepax
2022-02-08 13:50 ` Charles Keepax
2022-02-08 13:56 ` Mark Brown
2022-02-08 14:33 ` Charles Keepax
2022-02-08 14:41 ` Mark Brown
[not found] ` <22d9bf04-e069-c6a3-4d59-974a9402b0f7@quicinc.com>
2022-02-15 10:54 ` Charles Keepax
2022-02-08 13:44 ` Mark Brown
2022-02-09 8:41 ` Prasad Kumpatla [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=c055e4e8-fd11-49e9-c7a9-bf2f1ec9de36@quicinc.com \
--to=quic_pkumpatl@quicinc.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rafael@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
all inboxes | Powered by JetHome®