Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CAOMZO5AW4JUEFiaFgr8PvC5x3a5VWA4Ut8cXYYAme5-scgBV6Q@mail.gmail.com>
 <872024534.20587.1671097586476.JavaMail.zimbra@z.j-2.se>
In-Reply-To: <872024534.20587.1671097586476.JavaMail.zimbra@z.j-2.se>
From:   Fabio Estevam <festevam@gmail.com>
Date:   Fri, 16 Dec 2022 09:04:23 -0300
Message-ID: <CAOMZO5Bv+_2CN_CGeFswRCQp1-2fmuFZj26enxEeE5gpva160w@mail.gmail.com>
Subject: Re: ath10k: IRQ timeout after AP-STA-POLL-OK
To:     Patrik Arven <patrik.arven@j-2.se>
Cc:     kvalo@kernel.org, linux-wireless <linux-wireless@vger.kernel.org>,
        ath10k@lists.infradead.org, Bough Chen <haibo.chen@nxp.com>,
        Kevin Groeneveld <KGroeneveld@lenbrook.com>,
        Jakub Kicinski <kuba@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Patrik,

On Thu, Dec 15, 2022 at 6:46 AM Patrik Arven <patrik.arven@j-2.se> wrote:

> Solution in my case was to revert to a custom(?) qca driver:

Thanks for your reply.

Yes, I am aware of this out-of-tree driver, but my intention is to
keep using the mainline ath10k one.

Does anyone know what triggers the AP-STA-POLL-OK event?

It looks like whenever AP-STA-POLL-OK happens, then the eMMC interrupt
is no longer handled and causes the interrupt timeout.