From: Tony Lindgren <tony@atomide.com>
To: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Cc: Suman Anna <s-anna@ti.com>,
Sarangdhar Joshi <spjoshi@codeaurora.org>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
Trilok Soni <tsoni@codeaurora.org>,
Dave Gerlach <d-gerlach@ti.com>
Subject: Re: [PATCH v2] soc: ti: Drop wait from wkup_m3_rproc_boot_thread
Date: Thu, 5 Jan 2017 14:03:06 -0800 [thread overview]
Message-ID: <20170105220305.GT4310@atomide.com> (raw)
In-Reply-To: <d98575a9-1863-88f0-d417-ae894db2dc55@oracle.com>
* Santosh Shilimkar <santosh.shilimkar@oracle.com> [170105 13:18]:
>
>
> On 1/5/2017 1:08 PM, Suman Anna wrote:
> > On 01/03/2017 05:41 PM, Sarangdhar Joshi wrote:
> > > The function wkup_m3_rproc_boot_thread waits for
> > > asynchronous firmware loading to parse the resource table
> > > before calling rproc_boot(). However, as the resource table
> > > parsing has been moved to rproc_boot(), there's no need to
> > > wait for the asynchronous firmware loading completion.
> > > So, drop this.
> > >
> > > CC: Dave Gerlach <d-gerlach@ti.com>
> > > CC: Suman Anna <s-anna@ti.com>
> > > CC: Bjorn Andersson <bjorn.andersson@linaro.org>
> > > Signed-off-by: Sarangdhar Joshi <spjoshi@codeaurora.org>
> >
> > + Tony and Santosh, not sure who is picking up the wkup_m3 related patches.
> >
> I think Tony has queued patches for wakeup_m3 before.
Sure I can queue it.
Thanks,
Tony
next prev parent reply other threads:[~2017-01-05 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 23:41 [PATCH v2] soc: ti: Drop wait from wkup_m3_rproc_boot_thread Sarangdhar Joshi
2017-01-05 21:08 ` Suman Anna
2017-01-05 21:17 ` Santosh Shilimkar
2017-01-05 22:03 ` Tony Lindgren [this message]
2017-01-05 21:58 ` Sarangdhar Joshi
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=20170105220305.GT4310@atomide.com \
--to=tony@atomide.com \
--cc=bjorn.andersson@linaro.org \
--cc=d-gerlach@ti.com \
--cc=linux-arm-kernel@lists.infradead.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=s-anna@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=sboyd@codeaurora.org \
--cc=spjoshi@codeaurora.org \
--cc=ssantosh@kernel.org \
--cc=tsoni@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).