[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <egnmb647g7x7e74j4g2jddwho23ulmbap2q4eimcyj7y4qvdlz@zmaydxodu2a6>
Date: Sat, 15 Jul 2023 13:20:56 -0700
From: Bjorn Andersson <andersson@...nel.org>
To: Vignesh Viswanathan <quic_viswanat@...cinc.com>
Cc: agross@...nel.org, konrad.dybcio@...aro.org,
mathieu.poirier@...aro.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-remoteproc@...r.kernel.org,
quic_srichara@...cinc.com, quic_varada@...cinc.com,
quic_kathirav@...cinc.com, quic_devipriy@...cinc.com,
quic_sjaganat@...cinc.com
Subject: Re: [PATCH] remoteproc: qcom: Add NOTIFY_FATAL event type to SSR
subdevice
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.
Regards,
Bjorn
Powered by blists - more mailing lists