devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sibi Sankar <quic_sibis@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	quic_psodagud@quicinc.com, bjorn.andersson@linaro.org,
	agross@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	eberman@codeaurora.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [RFC 1/3] dt-bindings: firmware: qcom-scm: Add interconnects property
Date: Thu, 2 Jun 2022 08:03:09 -0500	[thread overview]
Message-ID: <20220602130309.GA2103167-robh@kernel.org> (raw)
In-Reply-To: <1653289258-17699-2-git-send-email-quic_sibis@quicinc.com>

On Mon, 23 May 2022 12:30:56 +0530, Sibi Sankar wrote:
> Add interconnects as an optional property for SM8450 SoCs.
> 
> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
> ---
> 
> Since the interconnect requirements could either be specified in the
> individual remoteprocs or directly in the scm interface, will perform
> the yaml conversion in the next re-spin based on the consensus.
> 
>  Documentation/devicetree/bindings/firmware/qcom,scm.txt | 1 +
>  1 file changed, 1 insertion(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-06-02 13:03 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 [this message]
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 ` (subset) " Bjorn Andersson

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=20220602130309.GA2103167-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.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).