linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Sibi Sankar <sibis@codeaurora.org>
Cc: ohad@wizery.com, linux-remoteproc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	tsoni@codeaurora.org, sricharan@codeaurora.org,
	akdwived@codeaurora.org, kyan@codeaurora.org
Subject: Re: [PATCH v5 0/5] Add coredump support for Q6v5 Modem remoteproc
Date: Fri, 19 Oct 2018 11:35:16 -0700	[thread overview]
Message-ID: <20181019183514.GU12063@builder> (raw)
In-Reply-To: <20181017135527.30592-1-sibis@codeaurora.org>

On Wed 17 Oct 06:55 PDT 2018, Sibi Sankar wrote:

> This patch series add coredump support for modem on SDM845, MSM8996
> and MSM8916 SoCs. Modem requires the mba to be loaded before a
> coredump can be performed and this is achieved using a custom per
> segment dump function.
> 
> V5:
>   Add software bypass to avoid high MX current in mpss_load error path.
>   Remove the proxy votes of clk/regs only after the active/reset clks/regs.
>   Reclaim MBA memory after mpss_load failure in mba_reclaim func.
>   Revert to dump_fn to as done with v3 with a mask based approach.
> 
> V4:
>   Addressed Bjorn's comments.
> 
> V3:
>   [bjorn]:replace prepare/unprepare ops with a more generalised per segment
>   dump function
> 
> V2:
>   Introduce prepare/unprepare ops for rproc coredump
> 

Applied

Regards,
Bjorn

> Sibi Sankar (5):
>   remoteproc: Introduce custom dump function for each remoteproc segment
>   remoteproc: Add mechanism for custom dump function assignment
>   remoteproc: qcom: q6v5-mss: Refactor mba load/unload sequence
>   remoteproc: qcom: q6v5-mss: Add custom dump function for modem
>   remoteproc: qcom: q6v5-mss: Register segments/dumpfn for coredump
> 
>  drivers/remoteproc/qcom_q6v5_mss.c   | 379 +++++++++++++++++----------
>  drivers/remoteproc/remoteproc_core.c |  55 +++-
>  include/linux/remoteproc.h           |  11 +
>  3 files changed, 303 insertions(+), 142 deletions(-)
> 
> -- 
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
> 

      parent reply	other threads:[~2018-10-19 18:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 13:55 [PATCH v5 0/5] Add coredump support for Q6v5 Modem remoteproc Sibi Sankar
2018-10-17 13:55 ` [PATCH v5 1/5] remoteproc: Introduce custom dump function for each remoteproc segment Sibi Sankar
2018-10-17 13:55 ` [PATCH v5 2/5] remoteproc: Add mechanism for custom dump function assignment Sibi Sankar
2018-10-17 13:55 ` [PATCH v5 3/5] remoteproc: qcom: q6v5-mss: Refactor mba load/unload sequence Sibi Sankar
2018-10-17 13:55 ` [PATCH v5 4/5] remoteproc: qcom: q6v5-mss: Add custom dump function for modem Sibi Sankar
2018-10-17 13:55 ` [PATCH v5 5/5] remoteproc: qcom: q6v5-mss: Register segments/dumpfn for coredump Sibi Sankar
2018-10-19 18:35 ` Bjorn Andersson [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=20181019183514.GU12063@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=akdwived@codeaurora.org \
    --cc=kyan@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=sibis@codeaurora.org \
    --cc=sricharan@codeaurora.org \
    --cc=tsoni@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).