[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170527011208.GA1730@builder>
Date: Fri, 26 May 2017 18:12:08 -0700
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Sarangdhar Joshi <spjoshi@...eaurora.org>
Cc: Ohad Ben-Cohen <ohad@...ery.com>,
Loic Pallardy <loic.pallardy@...com>,
linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org, Stephen Boyd <sboyd@...eaurora.org>,
Trilok Soni <tsoni@...eaurora.org>
Subject: Re: [PATCH v3 1/2] remoteproc: Introduce rproc_{start,stop}()
functions
On Fri 26 May 16:51 PDT 2017, Sarangdhar Joshi wrote:
> In the context of recovering from crash, rproc_trigger_recovery() does
> rproc_shutdown() followed by rproc_boot(). The remoteproc resources are
> cleaned up in rproc_shutdown() and immediately reallocated in
> rproc_boot() which is an unnecessary overhead. Furthermore, we want the
> memory regions to be accessible after stopping the remote processor, to
> be able to extract the memory content for a coredump.
>
> This patch factors out the code in rproc_boot() and rproc_shutdown()
> path and introduces rproc_{start,stop}() in order to avoid resource
> allocation overhead.
>
> Signed-off-by: Sarangdhar Joshi <spjoshi@...eaurora.org>
Both patches applied.
Thanks,
Bjorn
Powered by blists - more mailing lists