From: patchwork-bot+linux-remoteproc@kernel.org
To: Sibi Sankar <sibis@codeaurora.org>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH 0/2] Drop all accesses to MPSS PERPH register space
Date: Wed, 13 May 2020 06:20:06 +0000 [thread overview]
Message-ID: <158935080691.26945.8757289230451414699.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200415145110.20624-1-sibis@codeaurora.org>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next).
On Wed, 15 Apr 2020 20:21:08 +0530 you wrote:
> 7C retail devices using MSA based boot will result in a fuse combination
> which will prevent accesses to MSS PERPH register space where the mpss
> clocks and halt-nav reside. Hence requesting a halt-nav as part of the
> SSR sequence will result in a NoC error. Issuing HALT NAV request and
> turning on the mss clocks as part of SSR will no longer be required
> since the modem firmware will have the necessary fixes to ensure that
> there are no pending NAV DMA transactions thereby ensuring a smooth
> SSR.
>
> [...]
Here is a summary with links:
- [1/2] dt-bindings: remoteproc: qcom: Replace halt-nav with spare-regs
https://git.kernel.org/andersson/remoteproc/c/e62e3acd61d36b07878cd33a868a5797fe1e25b5
- [2/2] remoteproc: qcom_q6v5_mss: Drop accesses to MPSS PERPH register space
https://git.kernel.org/andersson/remoteproc/c/a9fdc79d488623d36341f0f3d08f5aa1bedb9d53
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
prev parent reply other threads:[~2020-05-13 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 14:51 [PATCH 0/2] Drop all accesses to MPSS PERPH register space Sibi Sankar
2020-04-15 14:51 ` [PATCH 1/2] dt-bindings: remoteproc: qcom: Replace halt-nav with spare-regs Sibi Sankar
2020-04-15 14:51 ` Sibi Sankar
2020-04-15 14:51 ` [PATCH 2/2] remoteproc: qcom_q6v5_mss: Drop accesses to MPSS PERPH register space Sibi Sankar
2020-04-15 14:51 ` Sibi Sankar
2020-04-29 17:27 ` [PATCH 0/2] Drop all " Evan Green
2020-05-13 6:20 ` patchwork-bot+linux-remoteproc [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=158935080691.26945.8757289230451414699.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=sibis@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