From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Lew Subject: Re: [PATCH v3 4/5] remoteproc: qcom: Introduce sysmon Date: Fri, 17 Nov 2017 17:27:21 -0800 Message-ID: References: <20171115201012.25892-1-bjorn.andersson@linaro.org> <20171115201012.25892-5-bjorn.andersson@linaro.org> <0ab5497e-94b4-6450-d680-14f002188714@codeaurora.org> <20171117055832.GR28761@minitux> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20171117055832.GR28761@minitux> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Bjorn Andersson Cc: Andy Gross , Ohad Ben-Cohen , Arun Kumar Neelakantam , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, linux-remoteproc@vger.kernel.org, runminw@codeaurora.org List-Id: linux-arm-msm@vger.kernel.org On 11/16/2017 9:58 PM, Bjorn Andersson wrote: > On Thu 16 Nov 12:05 PST 2017, Chris Lew wrote: >>> + req.event = SSCTL_SSR_EVENT_BEFORE_SHUTDOWN; >> >> Are there plans to add the other SSR events to sysmon notifiers? I think the >> SSCTL service expects to receive events about remote procs starting as well. >> > > We could easily add support here to send out the AFTER_BOOTUP > notification, beyond that we would need to extend the subdev notifiers > as well. > > But the downstream code paths does confuse me, can you confirm that > these messages are actually sent to the remote ssctl services? > > Regards, > Bjorn > Yea the other three events are definitely sent to the remote. The remote side posts the events for other modules to query. I'm not sure if all of the events are used by other other modules though. Thanks, Chris -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project