From: Peng Fan <peng.fan@oss.nxp.com>
To: Tanmay Shah <tanmays@amd.com>,
andersson@kernel.org, mathieu.poirier@linaro.org,
arnaud.pouliquen@foss.st.com
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V8 0/2] remoteproc: support self recovery
Date: Thu, 29 Sep 2022 16:33:00 +0800 [thread overview]
Message-ID: <d708cc20-b575-e007-0ff2-106f7e585cdc@oss.nxp.com> (raw)
In-Reply-To: <08a9285e-4a4f-ff7f-0ec2-8958d0c11a08@amd.com>
On 9/28/2022 11:42 PM, Tanmay Shah wrote:
>
> On 9/27/22 11:47 PM, Peng Fan (OSS) wrote:
>> CAUTION: This message has originated from an External Source. Please
>> use proper judgment and caution when opening attachments, clicking
>> links, or responding to this email.
>>
>>
>> From: Peng Fan <peng.fan@nxp.com>
>>
>> V8:
>> Rebased on linux-next/master tag: next-20220927
>
> Hi Peng,
>
> Thanks for your patch.
>
> Tags are useful, but more accurate method is to use --base option of git
> format-patch.
>
> This can inform others what base-commit was used. It is also useful when
> you have prerequisite patches.
Yes, I see. linux-next/master would force update every day, so I am not
sure base-commit would work for linux-next/master branch.
Thanks,
Peng.
>
> Hope this helps.
>
> Thanks,
>
> Tanmay
>
>>
>> V7:
>> Per comments from Arnaud Pouliquen:
>> Typo fixes
>> Added A-b tag
>>
>> V6:
>> Rename rproc_firmware_recovery to rproc_boot_recovery
>> Drop the unlock/lock when do reproc_attach_recovery
>>
>> V5:
>> Rename RPROC_FEAT_ATTACH_RECOVERY to RPROC_FEAT_ATTACH_ON_RECOVERY
>> Add kerneldoc for rproc features
>> Change rproc_set_feature to return int type and add a max feature check
>> Use __rproc_detach and __rproc_attach when do attach recovery
>>
>> https://patchwork.kernel.org/project/linux-remoteproc/cover/20220615032048.465486-1-peng.fan@oss.nxp.com/
>>
>> V4:
>> Based on Bjorn's comments on V2-2
>> Move the rproc_has_feature/rproc_set_feature to
>> remoteproc_internal.h and
>> Keep rproc_features still in remoteproc.h, because we use
>> RPROC_MAX_FEATURES to declare bitmap.
>> Update commit log for patch 2/2, and add comments
>>
>>
>> https://patchwork.kernel.org/project/linux-remoteproc/cover/20220323034405.976643-1-peng.fan@oss.nxp.com/
>>
>> V3:
>> Resend the wrong labeled patchset
>>
>> https://patchwork.kernel.org/project/linux-remoteproc/list/?series=621311
>>
>> Write a cover-letter
>> To i.MX8QM/QXP, they have a M4 core self-recovery capability without
>> Linux loading firmware. The self recovery is done by
>> SCU(System Control Unit). Current remoteproc framework only support
>> Linux
>> help recovery remote processor(stop, loading firmware, start). This
>> patchset is support remote processor self recovery(attach recovery).
>>
>> In order to avoid introducing a new variable(bool
>> support_self_recovery),
>> patch 1 introduce a new function, rproc_has_feature to make code
>> easy to
>> extend, cleaner, such as we could move "bool has_iommu" to
>> rproc_has_feature(rproc, RPROC_FEAT_IOMMU).
>>
>> Patch 2 is introduce a new function rproc_attach_recovery for
>> self recovery, the original logic move to rproc_firmware_recovery
>> meaning
>> needs linux to help recovery.
>>
>> V2-version 2:
>>
>> https://patchwork.kernel.org/project/linux-remoteproc/list/?series=621311
>> Introduce rproc_has_feature
>>
>> V2-version 1:
>>
>> https://patchwork.kernel.org/project/linux-remoteproc/patch/20220126085120.3397450-1-peng.fan@oss.nxp.com/
>> Nothing change in V2.
>> Only move this patch out from
>>
>> https://patchwork.kernel.org/project/linux-remoteproc/list/?series=604364
>>
>> Peng Fan (2):
>> remoteproc: introduce rproc features
>> remoteproc: support attach recovery after rproc crash
>>
>> drivers/remoteproc/remoteproc_core.c | 62 ++++++++++++++++--------
>> drivers/remoteproc/remoteproc_internal.h | 15 ++++++
>> include/linux/remoteproc.h | 16 ++++++
>> 3 files changed, 74 insertions(+), 19 deletions(-)
>>
>> --
>> 2.37.1
>>
next prev parent reply other threads:[~2022-09-29 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 6:47 [PATCH V8 0/2] remoteproc: support self recovery Peng Fan (OSS)
2022-09-28 6:47 ` [PATCH V8 1/2] remoteproc: introduce rproc features Peng Fan (OSS)
2022-09-28 6:47 ` [PATCH V8 2/2] remoteproc: support attach recovery after rproc crash Peng Fan (OSS)
2022-09-28 15:42 ` [PATCH V8 0/2] remoteproc: support self recovery Tanmay Shah
2022-09-29 8:33 ` Peng Fan [this message]
2022-09-28 16:48 ` Mathieu Poirier
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=d708cc20-b575-e007-0ff2-106f7e585cdc@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=andersson@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=peng.fan@nxp.com \
--cc=tanmays@amd.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