From: Vedang Nagar <quic_vnagar@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <cros-qcom-dts-watchers@chromium.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: sc7280: enable venus node
Date: Tue, 12 Nov 2024 11:47:09 +0530 [thread overview]
Message-ID: <78e6ff6b-efe1-496c-a1fb-c9a0a4aba2d2@quicinc.com> (raw)
In-Reply-To: <kezh3lmysij56g2tjwwuas5r26ro5i777yxxitsdcjeg7zp67v@oknrdbkzison>
On 10/7/2024 1:20 AM, Dmitry Baryshkov wrote:
> On Fri, Oct 04, 2024 at 04:22:31PM GMT, Vedang Nagar wrote:
>> Enable the venus node on Qualcomm sc7280. It was made disabled
>> earlier to avoid bootup crash, which is fixed now with [1].
>
> NAK, there might be other reasons to keep venus disabled, like the lack
> of the vendor-signed firmware for the particular device.
Can you pls elaborate more on this? Any device with sc7280 SOC can use
venus.mbn which is already present in linux-firmware git.
Regards,
Vedang Nagar
>
>>
>> [1]
>> https://lore.kernel.org/linux-media/20231201-sc7280-venus-pas-v3-2-bc132dc5fc30@fairphone.com/
>>
>> Signed-off-by: Vedang Nagar <quic_vnagar@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/sc7280.dtsi | 2 --
>> 1 file changed, 2 deletions(-)
>
next prev parent reply other threads:[~2024-11-12 6:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 10:52 [PATCH] arm64: dts: qcom: sc7280: enable venus node Vedang Nagar
2024-10-06 3:32 ` Bjorn Andersson
2024-10-06 8:26 ` Krzysztof Kozlowski
2024-10-06 19:50 ` Dmitry Baryshkov
2024-11-12 6:17 ` Vedang Nagar [this message]
2024-11-12 13:13 ` Dmitry Baryshkov
2024-11-12 14:39 ` Vedang Nagar
2024-11-12 15:19 ` Luca Weiss
2024-11-13 7:01 ` Vedang Nagar
2024-11-13 8:03 ` Luca Weiss
2025-01-07 4:11 ` Vedang Nagar
2025-01-07 7:32 ` Luca Weiss
2025-01-07 22:36 ` Dmitry Baryshkov
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=78e6ff6b-efe1-496c-a1fb-c9a0a4aba2d2@quicinc.com \
--to=quic_vnagar@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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