From: Daniel Walker <dwalker@codeaurora.org>
To: Dima Zavin <dima@android.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 5/5] arm: msm: smd: fix SMD modem processor sync condition
Date: Mon, 19 Apr 2010 12:01:45 -0700 [thread overview]
Message-ID: <1271703705.15004.4.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <w2y404ea8001004191134p804a8c3an134456d3af6ba29d@mail.gmail.com>
On Mon, 2010-04-19 at 11:34 -0700, Dima Zavin wrote:
> Do we really need a formalized blocking point here? The apps processor
> can do other useful initialization work while the modem is booting.
> The first time you do a proc_comm call, it checks the PCOM_READY
> state, and will block anyway. Preventing the apps processor from
> continuing until then is suboptimal. If there are bugs in the modem
> code where it incorrectly stomps on shared resources, then those
> should be fixed. This patch looks like a hack to me.
Yes, we need to formalize a blocking point .. The apps processor waits
in this way no matter what you do .. Like your saying above "The first
time you do a proc_comm call, it checks the PCOM_READY state, and will
block anyway" that's a hack .. What your saying is _maybe_ there exists
a proc_comm call early enough to prevent a crash, or maybe not .. That's
not formal enough.
This patch makes this a formal process with a comment explain what is
happening, and we will never see a crash related to this again.
Daniel
next prev parent reply other threads:[~2010-04-19 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 18:03 [PATCH 5/5] arm: msm: smd: fix SMD modem processor sync condition Daniel Walker
2010-04-19 18:34 ` Dima Zavin
2010-04-19 19:01 ` Daniel Walker [this message]
2010-04-19 19:06 ` Dima Zavin
2010-04-19 19:11 ` Daniel Walker
2010-04-19 19:23 ` Dima Zavin
2010-04-19 19:42 ` Daniel Walker
2010-04-20 13:37 ` Pavel Machek
2010-04-20 15:44 ` [PATCH] " Daniel Walker
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=1271703705.15004.4.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--cc=dima@android.com \
--cc=linux-arm-msm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.