From: Chris Lew <quic_clew@quicinc.com>
To: <agross@kernel.org>, <bjorn.andersson@linaro.org>,
<konrad.dybcio@somainline.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_clew@quicinc.com>
Subject: [PATCH 0/4] Add smp2p retrigger support
Date: Tue, 5 Jul 2022 23:02:07 -0700 [thread overview]
Message-ID: <1657087331-32455-1-git-send-email-quic_clew@quicinc.com> (raw)
The remoteproc framework keeps interrupts disabled until it powers on a
remote proc to prevent spurious interrupts. There is a case where the
remote proc can finish booting before remoteproc enables the interrupt.
If this happens, the remoteproc framework will miss the notification
and eventually timeout waiting for the remoteproc to finish "booting".
Add support into smp2p to retrigger an interrupt if it was missed while
the interrupt was disabled. The interrupt should retrigger once the
interrupt is enabled. This will make the bootup sequence for remoteproc
less racy.
Chris Lew (3):
soc: qcom: smp2p: Introduce pending state for virtual irq
soc: qcom: smp2p: Add proper retrigger detection
soc: qcom: smp2p: Add memory barrier for irq_pending
Tao Zhang (1):
soc: qcom: smp2p: Add remote_id into irq name
drivers/soc/qcom/smp2p.c | 42 ++++++++++++++++++++++++++++++++++++------
1 file changed, 36 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2022-07-06 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 6:02 Chris Lew [this message]
2022-07-06 6:02 ` [PATCH 1/4] soc: qcom: smp2p: Introduce pending state for virtual irq Chris Lew
2022-07-13 15:32 ` Doug Anderson
2022-07-06 6:02 ` [PATCH 2/4] soc: qcom: smp2p: Add proper retrigger detection Chris Lew
2022-07-06 6:02 ` [PATCH 3/4] soc: qcom: smp2p: Add memory barrier for irq_pending Chris Lew
2022-07-06 12:52 ` Manivannan Sadhasivam
2022-07-13 15:32 ` Doug Anderson
2022-07-06 6:02 ` [PATCH 4/4] soc: qcom: smp2p: Add remote_id into irq name Chris Lew
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=1657087331-32455-1-git-send-email-quic_clew@quicinc.com \
--to=quic_clew@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®