From: Paul Hollinsky <phollinsky@holtechnik.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Konrad Dybcio <konradybcio@gmail.com>
Cc: Sumit Garg <sumit.garg@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Akhil P Oommen <akhilpo@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>,
cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] qcom PAS TZ API migration breaks GPU and modem on TrustZone without PAS (sc7180 trogdor)
Date: Fri, 21 Aug 2026 01:27:30 -0700 [thread overview]
Message-ID: <20260821082730.89413-1-phollinsky@holtechnik.com> (raw)
In-Reply-To: <943d1db3-f117-4e9c-94db-7221b47d9d29@leemhuis.info>
On 8/21/26 08:33, Thorsten Leemhuis wrote:
> Just wondering: who will submit the proper fix to ideally fix this
> before the culprit hits mainline
I have now. I sent them as two separate patches, because the two culprits
are in different places:
drm/msm/adreno: Only check for PAS when a zap shader is present
https://lore.kernel.org/r/20260821081325.89088-1-phollinsky@holtechnik.com
0be72be03ca7 has in fact already reached mainline, in this merge
window, via the soc-drivers-7.3 pull (Linus' merge 368cf60c36a3).
So this one is based on Linus' tree rather than on msm-fixes, which
still predates the culprit - it went in through the qcom tree, not
through msm. It is addressed to the msm maintainers, but it can just
as easily go back through the tree the culprit came from.
remoteproc: qcom_q6v5_mss: Don't require PAS for memory protection
https://lore.kernel.org/r/20260821081540.89137-1-phollinsky@holtechnik.com
f3b1357673dd is still only in remoteproc/rproc-next, so this one is
based on that branch and would ideally be picked up there before it
is sent on.
Both are exactly the shapes Konrad agreed with in this thread, and both
are tested on the affected machine (Lenovo IdeaPad Duet 3,
sc7180-trogdor-wormdingler).
#regzbot monitor: https://lore.kernel.org/r/20260821081325.89088-1-phollinsky@holtechnik.com
#regzbot monitor: https://lore.kernel.org/r/20260821081540.89137-1-phollinsky@holtechnik.com
All the best,
Paul Hollinsky
next prev parent reply other threads:[~2026-08-23 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 3:47 [REGRESSION] qcom PAS TZ API migration breaks GPU and modem on TrustZone without PAS (sc7180 trogdor) Paul Hollinsky
2026-08-08 3:55 ` sashiko-bot
2026-08-17 15:41 ` Konrad Dybcio
2026-08-21 6:33 ` Thorsten Leemhuis
2026-08-21 8:27 ` Paul Hollinsky [this message]
2026-08-21 8:37 ` Thorsten Leemhuis
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=20260821082730.89413-1-phollinsky@holtechnik.com \
--to=phollinsky@holtechnik.com \
--cc=abhinav.kumar@linux.dev \
--cc=akhilpo@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=konradybcio@gmail.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=robin.clark@oss.qualcomm.com \
--cc=sumit.garg@oss.qualcomm.com \
/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