From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Marek <jonathan@marek.ca>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8250-hdk: specify ZAP firmware name
Date: Tue, 16 Dec 2025 13:05:08 +0100 [thread overview]
Message-ID: <528ba93d-64b1-468c-9dff-04595becb7b3@oss.qualcomm.com> (raw)
In-Reply-To: <20251213-zap-names-v1-2-c889af173911@oss.qualcomm.com>
On 12/13/25 10:28 AM, Dmitry Baryshkov wrote:
> The DT file has GPU node enabled, but doesn't specify the file name of
> the ZAP firmware, which means using a default file name. Specify the
> name to the ZAP shader firmware, pointing to the file in the
> linux-firmware repo.
>
> Fixes: 04a3605b184e ("arm64: dts: qcom: add sm8250 GPU nodes")
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2025-12-16 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 9:27 [PATCH 0/2] arch: arm64: dts: qcom: specify ZAP shaders if GPU is enabled Dmitry Baryshkov
2025-12-13 9:28 ` [PATCH 1/2] arm64: dts: qcom: sm8150-hdk,mtp: specify ZAP firmware name Dmitry Baryshkov
2025-12-16 12:05 ` Konrad Dybcio
2025-12-13 9:28 ` [PATCH 2/2] arm64: dts: qcom: sm8250-hdk: " Dmitry Baryshkov
2025-12-16 12:05 ` Konrad Dybcio [this message]
2026-01-05 14:07 ` [PATCH 0/2] arch: arm64: dts: qcom: specify ZAP shaders if GPU is enabled 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=528ba93d-64b1-468c-9dff-04595becb7b3@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jonathan@marek.ca \
--cc=konradybcio@kernel.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