diff options
| author | Mukesh Ojha <quic_mojha@quicinc.com> | 2022-12-14 19:06:23 +0530 |
|---|---|---|
| committer | Bjorn Andersson <andersson@kernel.org> | 2022-12-28 10:52:44 -0600 |
| commit | cf5865e72236c239317d6c5829ab170419b400a4 (patch) | |
| tree | 88aaad6fdc42efc220204341c894f04a6de47f7a /tools/perf/scripts/python/task-analyzer.py | |
| parent | 4a0510a46c4447ad3e807a1e4d6cf195fd604c1d (diff) | |
remoteproc: qcom: pas: Fix subdevice add order
Currently, the notification like QCOM_SSR_BEFORE_SHUTDOWN is not exactly
sent before starting shutdown activity on remote subsystem but it is
getting sent after sysmon shutdown request to remote.
On getting QCOM_SSR_BEFORE_SHUTDOWN, some client want remote subsystem
to be alive to communicate but as sysmon shutdown request is getting
sent to remote before QCOM_SSR_BEFORE_SHUTDOWN notification sent to
kernel client due to which remote is not in a condition to communicate
with kernel clients.
Fixing the subdevice ordering will fix this as ssr subdevice will be
first one to get triggered in shutdown/stop path.
Signed-off-by: Mukesh Ojha <quic_mojha@quicinc.com>
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
Link: https://lore.kernel.org/r/1671024983-22634-1-git-send-email-quic_mojha@quicinc.com
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions