From: Bjorn Andersson <bjorn.andersson@linaro.org> To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Cc: Andy Gross <agross@kernel.org>, Ohad Ben-Cohen <ohad@wizery.com>, Mathieu Poirier <mathieu.poirier@linaro.org>, Rob Herring <robh+dt@kernel.org>, linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 2/2] remoteproc: qcom: pas: Add SC8180X adsp, cdsp and mpss Date: Fri, 25 Jun 2021 17:42:50 -0500 [thread overview] Message-ID: <YNZb6geMr5nRMpqW@builder.lan> (raw) In-Reply-To: <20210625044736.GA4974@workstation> On Thu 24 Jun 23:47 CDT 2021, Manivannan Sadhasivam wrote: > On Tue, Jun 08, 2021 at 10:49:44AM -0700, Bjorn Andersson wrote: > > The Qualcomm SC8180X has the typical ADSP, CDSP and MPSS remote > > processors operated using the PAS interface, add support for these. > > > > Attempts to configuring mss.lvl is failing, so a new adsp_data is > > provided that skips this resource, for now. > > > > What is the impact of this skipped resource? I guess it is enabled by > the bootloader so we can't change it in runtime? > The reason for voting for the "proxy" resources is such that if apss power collapses we might cut the power before the firmware has had a chance to tell the RPMh to keep the power on. So, there is a chance that an unfortunately timed power collapse might cause the modem to loose power, but given that I can't poke mss.lvl I would expect that this is handled in some other way - if necessary... > > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> > > Given that adsp remoteproc works without configuring mss power domain, > > Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> > Thank you! Regards, Bjorn > Thanks, > Mani > > > --- > > > > Changes since v1: > > - None > > > > drivers/remoteproc/qcom_q6v5_pas.c | 22 ++++++++++++++++++++++ > > 1 file changed, 22 insertions(+) > > > > diff --git a/drivers/remoteproc/qcom_q6v5_pas.c b/drivers/remoteproc/qcom_q6v5_pas.c > > index b921fc26cd04..a79bee901e9b 100644 > > --- a/drivers/remoteproc/qcom_q6v5_pas.c > > +++ b/drivers/remoteproc/qcom_q6v5_pas.c > > @@ -689,6 +689,25 @@ static const struct adsp_data mpss_resource_init = { > > .ssctl_id = 0x12, > > }; > > > > +static const struct adsp_data sc8180x_mpss_resource = { > > + .crash_reason_smem = 421, > > + .firmware_name = "modem.mdt", > > + .pas_id = 4, > > + .has_aggre2_clk = false, > > + .auto_boot = false, > > + .active_pd_names = (char*[]){ > > + "load_state", > > + NULL > > + }, > > + .proxy_pd_names = (char*[]){ > > + "cx", > > + NULL > > + }, > > + .ssr_name = "mpss", > > + .sysmon_name = "modem", > > + .ssctl_id = 0x12, > > +}; > > + > > static const struct adsp_data slpi_resource_init = { > > .crash_reason_smem = 424, > > .firmware_name = "slpi.mdt", > > @@ -811,6 +830,9 @@ static const struct of_device_id adsp_of_match[] = { > > { .compatible = "qcom,qcs404-cdsp-pas", .data = &cdsp_resource_init }, > > { .compatible = "qcom,qcs404-wcss-pas", .data = &wcss_resource_init }, > > { .compatible = "qcom,sc7180-mpss-pas", .data = &mpss_resource_init}, > > + { .compatible = "qcom,sc8180x-adsp-pas", .data = &sm8150_adsp_resource}, > > + { .compatible = "qcom,sc8180x-cdsp-pas", .data = &sm8150_cdsp_resource}, > > + { .compatible = "qcom,sc8180x-mpss-pas", .data = &sc8180x_mpss_resource}, > > { .compatible = "qcom,sdm845-adsp-pas", .data = &adsp_resource_init}, > > { .compatible = "qcom,sdm845-cdsp-pas", .data = &cdsp_resource_init}, > > { .compatible = "qcom,sdx55-mpss-pas", .data = &sdx55_mpss_resource}, > > -- > > 2.29.2 > >
next prev parent reply other threads:[~2021-06-25 22:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 17:49 [PATCH v2 1/2] dt-bindings: " Bjorn Andersson 2021-06-08 17:49 ` [PATCH v2 2/2] " Bjorn Andersson 2021-06-25 4:47 ` Manivannan Sadhasivam 2021-06-25 22:42 ` Bjorn Andersson [this message] 2021-06-18 20:50 ` [PATCH v2 1/2] dt-bindings: " Rob Herring
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=YNZb6geMr5nRMpqW@builder.lan \ --to=bjorn.andersson@linaro.org \ --cc=agross@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=manivannan.sadhasivam@linaro.org \ --cc=mathieu.poirier@linaro.org \ --cc=ohad@wizery.com \ --cc=robh+dt@kernel.org \ --subject='Re: [PATCH v2 2/2] remoteproc: qcom: pas: Add SC8180X adsp, cdsp and mpss' \ /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
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).