linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Sibi Sankar <quic_sibis@quicinc.com>
Cc: quic_psodagud@quicinc.com, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	eberman@codeaurora.org, krzysztof.kozlowski+dt@linaro.org,
	agross@kernel.org, robh+dt@kernel.org
Subject: Re: (subset) [RFC 0/3] Add interconnect support to the SCM interface
Date: Sat,  2 Jul 2022 22:56:45 -0500	[thread overview]
Message-ID: <165682055967.445910.14406038202679892253.b4-ty@linaro.org> (raw)
In-Reply-To: <1653289258-17699-1-git-send-email-quic_sibis@quicinc.com>

On Mon, 23 May 2022 12:30:55 +0530, Sibi Sankar wrote:
> Some of the SMC calls required by remoteproc PAS driver on SM8450 SoCs
> get a performance benefit from having a max vote to the crypto->ddr path.
> Add support for bandwidth (bw) voting for those SMC calls when the
> interconnects property is specified. Marking this as an RFC since the path
> could either be specified in the individual remoteprocs or directly in the
> scm interface.
> 
> [...]

Applied, thanks!

[3/3] arm64: dts: qcom: sm8450: Add interconnect requirements for SCM
      commit: 4c9fb8e89849db0f12fbfd4ad6a6ce036251a200

Best regards,
-- 
Bjorn Andersson <bjorn.andersson@linaro.org>

      parent reply	other threads:[~2022-07-03  4:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  7:00 [RFC 0/3] Add interconnect support to the SCM interface Sibi Sankar
2022-05-23  7:00 ` [RFC 1/3] dt-bindings: firmware: qcom-scm: Add interconnects property Sibi Sankar
2022-06-02 13:03   ` Rob Herring
2022-05-23  7:00 ` [RFC 2/3] firmware: qcom_scm: Add bw voting support to the SCM interface Sibi Sankar
2022-05-23  7:00 ` [RFC 3/3] arm64: dts: qcom: sm8450: Add interconnect requirements for SCM Sibi Sankar
2022-06-30  2:47 ` [RFC 0/3] Add interconnect support to the SCM interface Bjorn Andersson
2022-07-03  3:56 ` Bjorn Andersson [this message]

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=165682055967.445910.14406038202679892253.b4-ty@linaro.org \
    --to=bjorn.andersson@linaro.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eberman@codeaurora.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_psodagud@quicinc.com \
    --cc=quic_sibis@quicinc.com \
    --cc=robh+dt@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 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).