From: Alex Elder <elder@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>,
djakov@kernel.org, okukatla@codeaurora.org,
quic_mdtipton@quicinc.com
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mike Tipton <mdtipton@codeaurora.org>,
mka@chromium.org, dianders@chromium.org
Subject: Re: [PATCH v3] interconnect: qcom: icc-rpmh: Add BCMs to commit list in pre_aggregate
Date: Mon, 11 Apr 2022 21:20:49 -0500 [thread overview]
Message-ID: <d39cc8a1-ca52-e902-e761-35e06a67aba9@linaro.org> (raw)
In-Reply-To: <CAE-0n51-hpG_5O11FbGrHaMr_mN0ZAky8CVzZNmDj29aK8wGog@mail.gmail.com>
On 4/11/22 2:06 PM, Stephen Boyd wrote:
>> I have a hunch about what might be happening here. There is
>> some synchronization that must occur between the AP and modem
>> when IPA is starting up. Until that synchronization step has
>> completed, we can't allow the IPA network device to be opened.
> Is there a commit that implements this? Or how is the synchronization
> done? I can debug more and see if that synchronization is happening.
After testing today it seems maybe my hunch wasn't
the root cause. If you disagree and I'm missing
something, say so. I will take a look at that
though--my hunch--to see if the thing I thought
could be causing a problem can actually occur.
If so, I'll figure out a fix.
-Alex
prev parent reply other threads:[~2022-04-12 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 17:47 [PATCH v3] interconnect: qcom: icc-rpmh: Add BCMs to commit list in pre_aggregate Georgi Djakov
2022-04-05 23:00 ` Stephen Boyd
2022-04-06 4:47 ` Stephen Boyd
2022-04-08 18:52 ` Stephen Boyd
2022-04-11 15:59 ` Alex Elder
2022-04-11 19:06 ` Stephen Boyd
2022-04-11 20:20 ` Stephen Boyd
2022-04-12 4:47 ` Stephen Boyd
2022-04-12 2:18 ` Alex Elder
2022-04-12 2:20 ` Alex Elder [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=d39cc8a1-ca52-e902-e761-35e06a67aba9@linaro.org \
--to=elder@linaro.org \
--cc=dianders@chromium.org \
--cc=djakov@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mdtipton@codeaurora.org \
--cc=mka@chromium.org \
--cc=okukatla@codeaurora.org \
--cc=quic_mdtipton@quicinc.com \
--cc=swboyd@chromium.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