From: Evan Green <evgreen@chromium.org>
To: Sibi Sankar <sibis@codeaurora.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-remoteproc@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Ohad Ben Cohen <ohad@wizery.com>
Subject: Re: [PATCH 0/2] Drop all accesses to MPSS PERPH register space
Date: Wed, 29 Apr 2020 10:27:39 -0700 [thread overview]
Message-ID: <CAE=gft5REvz+0JLHtEN1BXmvWzMxftdecxPedLizgS47x1Sq7w@mail.gmail.com> (raw)
In-Reply-To: <20200415145110.20624-1-sibis@codeaurora.org>
On Wed, Apr 15, 2020 at 7:51 AM Sibi Sankar <sibis@codeaurora.org> 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.
>
> Sibi Sankar (2):
> dt-bindings: remoteproc: qcom: Replace halt-nav with spare-regs
> remoteproc: qcom_q6v5_mss: Drop accesses to MPSS PERPH register space
I haven't tested things in the "production" fuse configuration yet,
but in my current configuration I've got a tree that's running the
modem well.
Tested-by: Evan Green <evgreen@chromium.org>
next prev parent reply other threads:[~2020-04-29 17:28 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 ` Evan Green [this message]
2020-05-13 6:20 ` [PATCH 0/2] Drop all " patchwork-bot+linux-remoteproc
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='CAE=gft5REvz+0JLHtEN1BXmvWzMxftdecxPedLizgS47x1Sq7w@mail.gmail.com' \
--to=evgreen@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.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=robh+dt@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;
as well as URLs for NNTP newsgroup(s).