devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Rohit Agarwal <quic_rohiagar@quicinc.com>,
	agross@kernel.org, andersson@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	dmitry.baryshkov@linaro.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] arm64: dts: qcom: Add interconnect nodes for SDX75
Date: Wed, 27 Sep 2023 12:47:09 +0200	[thread overview]
Message-ID: <35703a29-5c5a-47a8-9a4b-04953dc3faba@linaro.org> (raw)
In-Reply-To: <1695720564-2978-2-git-send-email-quic_rohiagar@quicinc.com>

On 26.09.2023 11:29, Rohit Agarwal wrote:
> Add interconnect nodes to support interconnects on SDX75.
> Also parallely add the interconnect property for UART required
> so that the bootup to shell does not break with interconnects
> in place.
> 
> Signed-off-by: Rohit Agarwal <quic_rohiagar@quicinc.com>
> ---
[...]

>  		scm: scm {
>  			compatible = "qcom,scm-sdx75", "qcom,scm";
> @@ -434,6 +448,8 @@
>  			clock-names = "m-ahb",
>  				      "s-ahb";
>  			iommus = <&apps_smmu 0xe3 0x0>;
> +			interconnects = <&clk_virt MASTER_QUP_CORE_0 0 &clk_virt SLAVE_QUP_CORE_0 0>;
0 -> QCOM_ICC_TAG_ALWAYS (dt-bindings/interconnect/qcom,icc.h)

Konrad

  reply	other threads:[~2023-09-27 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26  9:29 [PATCH v2 0/3] Add devicetree support of Interconnects and USB for SDX75 Rohit Agarwal
2023-09-26  9:29 ` [PATCH v2 1/3] arm64: dts: qcom: Add interconnect nodes " Rohit Agarwal
2023-09-27 10:47   ` Konrad Dybcio [this message]
2023-10-03  8:04     ` Rohit Agarwal
2023-10-01 20:56   ` kernel test robot
2023-09-26  9:29 ` [PATCH v2 2/3] arm64: dts: qcom: Add USB3 and PHY support on SDX75 Rohit Agarwal
2023-09-26  9:29 ` [PATCH v2 3/3] arm64: dts: qcom: sdx75-idp: Enable USB3 and PHY support Rohit Agarwal
2023-09-27 10:48   ` Konrad Dybcio

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=35703a29-5c5a-47a8-9a4b-04953dc3faba@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_rohiagar@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).