From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
cros-qcom-dts-watchers@chromium.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] arm64: dts: qcom: cleanup GPU's zap-shader node
Date: Thu, 30 Oct 2025 13:46:46 -0500 [thread overview]
Message-ID: <176185000295.492730.10106519443122331720.b4-ty@kernel.org> (raw)
In-Reply-To: <20251028-dt-zap-shader-v1-0-7eccb823b986@oss.qualcomm.com>
On Tue, 28 Oct 2025 22:59:59 +0200, Dmitry Baryshkov wrote:
> Historically all devices manually defined GPU zap-shader node in their
> board DT files. This practice is frowned upon. Add the zap-shader node
> on all platforms, define a label for it and use the label in order to
> patch the node with the firmware name.
>
>
Applied, thanks!
[1/7] arm64: dts: qcom: sdm670: create common zap-shader node
commit: f85592223d5bf983b6c495f33cfa0344a9930d5b
[2/7] arm64: dts: qcom: sdm845: create common zap-shader node
commit: 8464b804bd35cf4068e3a7cd19163c0f8a063852
[3/7] arm64: dts: qcom: sc8180x: create common zap-shader node
commit: e3f81bdd46dc4120e9ee373aa8794b84c7dfd2f1
[4/7] arm64: dts: qcom: sc8280xp: create common zap-shader node
commit: 6e9612ced0c90fc19d9b27508f84ebcf5718b8a2
[5/7] arm64: dts: qcom: sm8250: drop duplicate memory-region defs
commit: 00d3f7b0536dec3b5660e25d0767f61ee38941a7
[6/7] arm64: dts: qcom: sc7180: add gpu_zap_shader label
commit: d994ae0427a83087bedcfbb8afabe620529ef594
[7/7] arm64: dts: qcom: add gpu_zap_shader label
commit: 2377626fd216ebdf17294ac0cabc27614fff07d1
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-10-30 18:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 20:59 Dmitry Baryshkov
2025-10-28 21:00 ` [PATCH 1/7] arm64: dts: qcom: sdm670: create common " Dmitry Baryshkov
2025-10-30 10:57 ` Konrad Dybcio
2025-10-28 21:00 ` [PATCH 2/7] arm64: dts: qcom: sdm845: " Dmitry Baryshkov
2025-10-30 10:57 ` Konrad Dybcio
2025-10-28 21:00 ` [PATCH 3/7] arm64: dts: qcom: sc8180x: " Dmitry Baryshkov
2025-10-30 10:58 ` Konrad Dybcio
2025-10-30 10:59 ` Konrad Dybcio
2025-10-30 17:28 ` Bjorn Andersson
2025-10-30 17:50 ` Dmitry Baryshkov
2025-10-30 17:58 ` Dmitry Baryshkov
2025-10-30 18:45 ` Bjorn Andersson
2025-10-31 9:30 ` Konrad Dybcio
2025-11-01 17:04 ` Bjorn Andersson
2025-10-28 21:00 ` [PATCH 4/7] arm64: dts: qcom: sc8280xp: " Dmitry Baryshkov
2025-10-30 10:59 ` Konrad Dybcio
2025-10-28 21:00 ` [PATCH 5/7] arm64: dts: qcom: sm8250: drop duplicate memory-region defs Dmitry Baryshkov
2025-10-30 10:59 ` Konrad Dybcio
2025-10-28 21:00 ` [PATCH 6/7] arm64: dts: qcom: sc7180: add gpu_zap_shader label Dmitry Baryshkov
2025-10-30 11:03 ` Konrad Dybcio
2025-10-28 21:00 ` [PATCH 7/7] arm64: dts: qcom: " Dmitry Baryshkov
2025-10-30 11:04 ` Konrad Dybcio
2025-10-28 22:21 ` [PATCH 0/7] arm64: dts: qcom: cleanup GPU's zap-shader node David Heidelberg
2025-10-29 9:33 ` Konrad Dybcio
2025-10-29 9:35 ` Dmitry Baryshkov
2025-10-29 9:36 ` Konrad Dybcio
2025-10-29 12:35 ` Dmitry Baryshkov
2025-10-30 11:04 ` Konrad Dybcio
2025-10-30 18:46 ` Bjorn Andersson [this message]
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=176185000295.492730.10106519443122331720.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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
all inboxes | Powered by JetHome®