From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: Dikshita Agarwal <dikshita@codeaurora.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
vgarodia@codeaurora.org, linux-arm-msm-owner@vger.kernel.org
Subject: Re: [PATCH 1/3] arm64: dts: sc7180: Add Venus video codec DT node
Date: Tue, 24 Dec 2019 17:42:33 +0530 [thread overview]
Message-ID: <8a43b13d0cd4a7bcb18e0f1f8259ec72@codeaurora.org> (raw)
In-Reply-To: <17a371c0-d73a-75eb-34f2-c9afb51d46f5@linaro.org>
Hi Stan,
On 2019-12-20 15:04, Stanimir Varbanov wrote:
>
> This subnode should be in sc7180-idp.dts, because we assume that by
> default the qcom platforms have TZ.
>
sc7180.dtsi will not be used on TZ based platforms which was the case
for SDM845
where sdm845.dtsi was common for TZ (dragonboards) and non TZ(cheza
boards) based platforms.
So in order to avoid duplicating this node in other board specific dts
files, it
would be better to have it here itself.
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2019-12-24 12:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 7:59 [PATCH v2,0/3] Enable video on sc7180 Dikshita Agarwal
2019-12-20 7:59 ` [PATCH 1/3] arm64: dts: sc7180: Add Venus video codec DT node Dikshita Agarwal
2019-12-20 9:34 ` Stanimir Varbanov
2019-12-23 9:50 ` dikshita
2019-12-24 12:12 ` Sai Prakash Ranjan [this message]
2019-12-24 13:24 ` Sai Prakash Ranjan
2019-12-29 3:18 ` Bjorn Andersson
2020-01-02 7:54 ` vgarodia
2019-12-20 7:59 ` [PATCH 2/3] dt-bindings: media: venus: Add sc7180 DT schema Dikshita Agarwal
2019-12-20 9:37 ` Stanimir Varbanov
2019-12-23 10:56 ` dikshita
2019-12-20 7:59 ` [PATCH 3/3] venus: core: add sc7180 DT compatible and resource struct Dikshita Agarwal
2019-12-20 9:33 ` Stanimir Varbanov
2019-12-23 10:04 ` dikshita
2019-12-23 10:43 ` Stanimir Varbanov
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=8a43b13d0cd4a7bcb18e0f1f8259ec72@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dikshita@codeaurora.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=stanimir.varbanov@linaro.org \
--cc=vgarodia@codeaurora.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).