From: Bjorn Andersson <andersson@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Chris Lew <quic_clew@quicinc.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Johan Hovold <johan@kernel.org>,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org,
Bjorn Andersson <quic_bjorande@quicinc.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH v2 0/2] soc: qcom: pmic_glink: Resolve failures to bring up pmic_glink
Date: Thu, 24 Oct 2024 13:56:53 -0500 [thread overview]
Message-ID: <172979621232.309364.9966362822139382018.b4-ty@kernel.org> (raw)
In-Reply-To: <20241023-pmic-glink-ecancelled-v2-0-ebc268129407@oss.qualcomm.com>
On Wed, 23 Oct 2024 17:24:31 +0000, Bjorn Andersson wrote:
> With the transition of pd-mapper into the kernel, the timing was altered
> such that on some targets the initial rpmsg_send() requests from
> pmic_glink clients would be attempted before the firmware had announced
> intents, and the firmware reject intent requests.
>
> Fix this
>
> [...]
Applied, thanks!
[1/2] rpmsg: glink: Handle rejected intent request better
commit: a387e73fedd6307c0e194deaa53c42b153ff0bd6
[2/2] soc: qcom: pmic_glink: Handle GLINK intent allocation rejections
commit: f8c879192465d9f328cb0df07208ef077c560bb1
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-10-24 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 17:24 [PATCH v2 0/2] soc: qcom: pmic_glink: Resolve failures to bring up pmic_glink Bjorn Andersson
2024-10-23 17:24 ` [PATCH v2 1/2] rpmsg: glink: Handle rejected intent request better Bjorn Andersson
2024-10-23 22:21 ` Chris Lew
2024-10-23 17:24 ` [PATCH v2 2/2] soc: qcom: pmic_glink: Handle GLINK intent allocation rejections Bjorn Andersson
2024-10-23 22:26 ` Chris Lew
2024-10-24 6:39 ` Johan Hovold
2024-10-24 17:49 ` Bjorn Andersson
2024-10-24 18:56 ` 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=172979621232.309364.9966362822139382018.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_clew@quicinc.com \
--cc=stable@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).