From: Vignesh Viswanathan <quic_viswanat@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: <agross@kernel.org>, <konrad.dybcio@linaro.org>,
<mathieu.poirier@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <quic_srichara@quicinc.com>,
<quic_varada@quicinc.com>, <quic_kathirav@quicinc.com>,
<quic_devipriy@quicinc.com>, <quic_sjaganat@quicinc.com>
Subject: Re: [PATCH] remoteproc: qcom: Add NOTIFY_FATAL event type to SSR subdevice
Date: Mon, 4 Sep 2023 22:23:47 +0530 [thread overview]
Message-ID: <509406eb-8093-4bcf-820f-8e5210e1539d@quicinc.com> (raw)
In-Reply-To: <egnmb647g7x7e74j4g2jddwho23ulmbap2q4eimcyj7y4qvdlz@zmaydxodu2a6>
On 7/16/2023 1:50 AM, Bjorn Andersson wrote:
> On Wed, May 03, 2023 at 11:51:46AM +0530, Vignesh Viswanathan wrote:
>> Currently the SSR subdevice notifies the client driver on crash of the
>> rproc from the recovery workqueue using the BEFORE_SHUTDOWN event.
>> However the client driver might be interested to know that the device
>> has crashed immediately to pause any further transactions with the
>> rproc. This calls for an event to be sent to the driver in the IRQ
>> context as soon as the rproc crashes.
>>
>
> Please make your argumentation more concrete, I can only guess what
> client driver you're referring to.
>
> You can do this either by spelling out which actual problem you're
> solving, or better yet, include some patches in the series that actually
> uses this interface.
>
Hi Bjorn,
Apologies for the delay in response.
The client driver in my scenario is a Wi-Fi driver which is continuously
queuing data to the remoteproc and needs to know if remoteproc crashes
as soon as possible to stop queuing further data and also dump some
debug statistics on the driver side that could potentially help in debug
of why the remoteproc crashed.
Also in the case with upcoming Wi-Fi 7 targets with multi-link
operation, the driver might need to know that the remoteproc has crashed
instantly to handle some multi-link specific handling.
The ath11k/ath12k WLAN drivers today partially have support for handling
such FATAL notification but it has not been upstreamed yet.
Reference patch:
https://git.codelinaro.org/clo/qsdk/oss/system/feeds/wlan-open/-/blob/win.wlan_host_opensource.1.0/mac80211/patches/031-ath11k-print-stats-on-crash.patch
-- event SUBSYS_PREPARE_FOR_FATAL_SHUTDOWN.
Also, Mukesh mentioned earlier that in some MSM targets with PCIe where
latency cannot be tolerated, a similar downstream patch adds support for
"early notifier". If this patch is accepted, the early notifier can also
be replaced to use the same NOTIFY_FATAL event from SSR Subdevice
https://git.codelinaro.org/clo/la/kernel/msm-5.15/-/commit/7583d24de337aa1bf7c375a7da706af9b995b9a1#a840754ebb0e24e88adbf48177e1abd0830b72d2
https://git.codelinaro.org/clo/la/kernel/msm-5.15/-/commit/257de41c63a5a51a081cc7887cdaa4a46e4d1744
Thanks,
Vignesh
> Regards,
> Bjorn
next prev parent reply other threads:[~2023-09-04 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 6:21 Vignesh Viswanathan
2023-05-03 11:26 ` Mukesh Ojha
2023-05-22 9:33 ` Mukesh Ojha
2023-05-29 3:57 ` Vignesh Viswanathan
2023-06-15 10:40 ` Vignesh Viswanathan
2023-07-11 8:00 ` Vignesh Viswanathan
2023-07-15 20:20 ` Bjorn Andersson
2023-09-04 16:53 ` Vignesh Viswanathan [this message]
2023-11-24 18:54 ` Vignesh Viswanathan
2024-02-07 16:21 ` Vignesh Viswanathan
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=509406eb-8093-4bcf-820f-8e5210e1539d@quicinc.com \
--to=quic_viswanat@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_devipriy@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.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 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®