From: "Rakesh Pillai" <pillair@codeaurora.org>
To: "'Kalle Valo'" <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
ath10k@lists.infradead.org,
'Youghandhar Chintala' <youghand@codeaurora.org>
Subject: RE: [PATCH v2 0/2] ath10k: Fixes during subsystem recovery
Date: Fri, 26 Feb 2021 20:10:48 +0530 [thread overview]
Message-ID: <002901d70c4d$6282e6c0$2788b440$@codeaurora.org> (raw)
In-Reply-To:
> -----Original Message-----
> From: Rakesh Pillai <pillair@codeaurora.org>
> Sent: Friday, January 15, 2021 6:56 PM
> To: 'Kalle Valo' <kvalo@codeaurora.org>
> Cc: 'ath10k@lists.infradead.org' <ath10k@lists.infradead.org>; 'linux-
> wireless@vger.kernel.org' <linux-wireless@vger.kernel.org>; 'linux-
> kernel@vger.kernel.org' <linux-kernel@vger.kernel.org>
> Subject: RE: [PATCH v2 0/2] ath10k: Fixes during subsystem recovery
>
>
> > -----Original Message-----
> > From: Kalle Valo <kvalo@codeaurora.org>
> > Sent: Tuesday, December 22, 2020 12:07 AM
> > To: Rakesh Pillai <pillair@codeaurora.org>
> > Cc: ath10k@lists.infradead.org; linux-wireless@vger.kernel.org; linux-
> > kernel@vger.kernel.org
> > Subject: Re: [PATCH v2 0/2] ath10k: Fixes during subsystem recovery
> >
> > Rakesh Pillai <pillair@codeaurora.org> writes:
> >
> > > This patch series includes some fixes when the device
> > > is in recovery mode, i.e. when the firmware goes down.
> > >
> > > - Pausing TX queues when FW goes down
> > > - Removed unwanted/extra error logging in pkt TX path
> > > - Skipping wait for FW response for delete cmds
> > > - Handling the -ESHUTDOWN error code in case of SSR.
> > >
> > > Rakesh Pillai (2):
> > > ath10k: Pause the tx queues when firmware is down
> > > ath10k: Skip wait for delete response if firmware is down
> >
> > This has been tested only on WCN3990. How do I know that this doesn't
> > break other hardware families?
>
> " ath10k: Pause the tx queues when firmware is down"
> This is done only for SNOC (wcn3990) target and does not affect other
> targets.
>
> " ath10k: Skip wait for delete response if firmware is down"
> The skip for wmi responses is done based on the flag
> "ATH10K_FLAG_CRASH_FLUSH", which is generic for all targets.
> Since if the FW is down, there wont be any response from the FW for any
> target.
>
Hi Kalle,
I see that these patches are in "deferred" state. Is there any info/change
needed in this patch ?
Thanks,
Rakesh Pillai.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2021-02-26 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 18:53 [PATCH v2 0/2] ath10k: Fixes during subsystem recovery Rakesh Pillai
2020-06-26 18:53 ` [PATCH v2 1/2] ath10k: Pause the tx queues when firmware is down Rakesh Pillai
2020-06-26 18:53 ` [PATCH v2 2/2] ath10k: Skip wait for delete response if " Rakesh Pillai
2020-09-15 7:47 ` [PATCH v2 0/2] ath10k: Fixes during subsystem recovery Rakesh Pillai
2020-09-15 14:28 ` Kalle Valo
2020-12-21 18:37 ` Kalle Valo
2021-01-15 13:25 ` Rakesh Pillai
2021-02-26 14:40 ` Rakesh Pillai [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='002901d70c4d$6282e6c0$2788b440$@codeaurora.org' \
--to=pillair@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=youghand@codeaurora.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;
as well as URLs for NNTP newsgroup(s).