From: Bjorn Andersson <bjorn.andersson@linaro.org> To: Chris Lew <clew@codeaurora.org> Cc: Andy Gross <andy.gross@linaro.org>, Ohad Ben-Cohen <ohad@wizery.com>, Arun Kumar Neelakantam <aneela@codeaurora.org>, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, linux-remoteproc@vger.kernel.org Subject: Re: [PATCH v4 4/5] remoteproc: qcom: Introduce sysmon Date: Thu, 30 Nov 2017 21:31:41 -0800 [thread overview] Message-ID: <20171201053141.GY28761@minitux> (raw) In-Reply-To: <2a4cb3e2-16ea-49f4-e40d-ee1f2a56929b@codeaurora.org> On Thu 30 Nov 17:52 PST 2017, Chris Lew wrote: > > > On 11/29/2017 5:16 PM, Bjorn Andersson wrote: > > The sysmon client communicates either via a dedicated SMD/GLINK channel > > or via QMI encoded messages over IPCROUTER with remote processors in > > order to perform graceful shutdown and inform about other remote > > processors shutting down. > > > > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> > > --- > Acked-By: Chris Lew <clew@codeaurora.org> > Thanks > Looked into who is listening to the other notifications besides > BEFORE_SHUTDOWN and I think subsequent patches will need to add support for > at least AFTER_POWERUP. > Agreed. Regards, Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Andersson <bjorn.andersson@linaro.org> To: Chris Lew <clew@codeaurora.org> Cc: Andy Gross <andy.gross@linaro.org>, Ohad Ben-Cohen <ohad@wizery.com>, Arun Kumar Neelakantam <aneela@codeaurora.org>, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, linux-remoteproc@vger.kernel.org Subject: Re: [PATCH v4 4/5] remoteproc: qcom: Introduce sysmon Date: Thu, 30 Nov 2017 21:31:42 -0800 [thread overview] Message-ID: <20171201053141.GY28761@minitux> (raw) In-Reply-To: <2a4cb3e2-16ea-49f4-e40d-ee1f2a56929b@codeaurora.org> On Thu 30 Nov 17:52 PST 2017, Chris Lew wrote: > > > On 11/29/2017 5:16 PM, Bjorn Andersson wrote: > > The sysmon client communicates either via a dedicated SMD/GLINK channel > > or via QMI encoded messages over IPCROUTER with remote processors in > > order to perform graceful shutdown and inform about other remote > > processors shutting down. > > > > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> > > --- > Acked-By: Chris Lew <clew@codeaurora.org> > Thanks > Looked into who is listening to the other notifications besides > BEFORE_SHUTDOWN and I think subsequent patches will need to add support for > at least AFTER_POWERUP. > Agreed. Regards, Bjorn
next prev parent reply other threads:[~2017-12-01 5:31 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-30 1:16 [PATCH v4 0/5] In-kernel QMI helpers and sysmon Bjorn Andersson 2017-11-30 1:16 ` [PATCH v4 1/5] soc: qcom: Introduce QMI encoder/decoder Bjorn Andersson 2017-11-30 17:17 ` Chris Lew 2017-12-01 9:10 ` Jitendra Sharma 2017-12-05 17:33 ` Bjorn Andersson 2017-11-30 1:16 ` [PATCH v4 2/5] soc: qcom: Introduce QMI helpers Bjorn Andersson 2017-11-30 8:18 ` Philippe Ombredanne 2017-12-01 5:35 ` Bjorn Andersson 2017-12-01 7:48 ` Philippe Ombredanne 2017-11-30 17:33 ` Chris Lew 2017-11-30 1:16 ` [PATCH v4 3/5] remoteproc: Pass type of shutdown to subdev remove Bjorn Andersson 2017-11-30 17:35 ` Chris Lew 2017-12-01 14:50 ` Arnaud Pouliquen 2017-12-01 14:50 ` Arnaud Pouliquen 2017-12-05 6:46 ` Bjorn Andersson 2017-12-05 10:54 ` Arnaud Pouliquen 2017-12-05 10:54 ` Arnaud Pouliquen 2017-12-05 17:17 ` Bjorn Andersson 2017-12-06 8:55 ` Arnaud Pouliquen 2017-12-06 8:55 ` Arnaud Pouliquen 2017-12-06 21:53 ` Bjorn Andersson 2017-12-07 12:14 ` Arnaud Pouliquen 2017-12-07 12:14 ` Arnaud Pouliquen 2017-11-30 1:16 ` [PATCH v4 4/5] remoteproc: qcom: Introduce sysmon Bjorn Andersson 2017-12-01 1:52 ` Chris Lew 2017-12-01 5:31 ` Bjorn Andersson [this message] 2017-12-01 5:31 ` Bjorn Andersson 2017-11-30 1:16 ` [PATCH v4 5/5] samples: Introduce Qualcomm QMI sample client Bjorn Andersson 2017-11-30 17:36 ` 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=20171201053141.GY28761@minitux \ --to=bjorn.andersson@linaro.org \ --cc=andy.gross@linaro.org \ --cc=aneela@codeaurora.org \ --cc=clew@codeaurora.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=linux-soc@vger.kernel.org \ --cc=ohad@wizery.com \ /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: linkBe 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.