All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Dikshita Agarwal <dikshita@codeaurora.org>
Cc: linux-kernel@vger.kernel.org,
	Jeffrey Kardatzke <jkardatzke@google.com>,
	devicetree@vger.kernel.org,
	Stanimir Varbanov <stanimir.varbanov@linaro.org>,
	Atul Dhudase <adhudase@codeaurora.org>,
	linux-arm-msm@vger.kernel.org,
	Matthias Kaehlcke <mka@chromium.org>
Subject: [PATCH] arm64: dts: qcom: sc7180: Add interconnect paths for the video codec
Date: Thu,  9 Apr 2020 16:02:08 -0700	[thread overview]
Message-ID: <20200409160206.1.Icf877f5cd50ef5e56d14ee014ca196d76242cb89@changeid> (raw)

Add the interconnect path configuration for the venus video codec of
the SC7180.

Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
---
The interconnect paths were originally part of the patch "arm64: dts:
sc7180: Add Venus video codec DT node" (https://patchwork.kernel.org/patch/11332131/),
they were removed because the ICC provider nodes hadn't landed yet.

 arch/arm64/boot/dts/qcom/sc7180.dtsi | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi b/arch/arm64/boot/dts/qcom/sc7180.dtsi
index 998f101ad623b7..2e11d4ce995778 100644
--- a/arch/arm64/boot/dts/qcom/sc7180.dtsi
+++ b/arch/arm64/boot/dts/qcom/sc7180.dtsi
@@ -1475,6 +1475,9 @@ venus: video-codec@aa00000 {
 				      "vcodec0_core", "vcodec0_bus";
 			iommus = <&apps_smmu 0x0c00 0x60>;
 			memory-region = <&venus_mem>;
+			interconnects = <&mmss_noc MASTER_VIDEO_P0 &mc_virt SLAVE_EBI1>,
+					<&gem_noc MASTER_APPSS_PROC &config_noc SLAVE_VENUS_CFG>;
+			interconnect-names = "video-mem", "cpu-cfg";
 
 			video-decoder {
 				compatible = "venus-decoder";
-- 
2.26.0.110.g2183baf09c-goog


                 reply	other threads:[~2020-04-09 23:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200409160206.1.Icf877f5cd50ef5e56d14ee014ca196d76242cb89@changeid \
    --to=mka@chromium.org \
    --cc=adhudase@codeaurora.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dikshita@codeaurora.org \
    --cc=jkardatzke@google.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=stanimir.varbanov@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.