From: Neil Armstrong <neil.armstrong@linaro.org>
To: Akhil P Oommen <akhilpo@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Rob Clark <robin.clark@oss.qualcomm.com>,
Sean Paul <sean@poorly.run>,
Konrad Dybcio <konradybcio@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jessica.zhang@oss.qualcomm.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Subject: Re: [PATCH RFC RFT] drm/msm: adreno: attach the GMU device to a driver
Date: Wed, 14 Jan 2026 09:45:06 +0100 [thread overview]
Message-ID: <e879d3a1-45d9-46f0-adaf-6bea243ab807@linaro.org> (raw)
In-Reply-To: <3149158c-a6c4-4c5d-9011-de4db8d1220c@oss.qualcomm.com>
Hi,
On 1/14/26 07:37, Akhil P Oommen wrote:
> On 10/22/2025 6:14 PM, Neil Armstrong wrote:
>> Due to the sync_state is enabled by default in pmdomain & CCF since v6.17,
>> the GCC and GPUCC sync_state would stay pending, leaving the resources in
>> full performance:
>> gcc-x1e80100 100000.clock-controller: sync_state() pending due to 3d6a000.gmu
>> gpucc-x1e80100 3d90000.clock-controller: sync_state() pending due to 3d6a000.gmu
>>
>> In order to fix this state and allow the GMU to be properly
>> probed, let's add a proper driver for the GMU and add it to
>> the MSM driver components.
>>
>> Only the proper GMU has been tested since I don't have
>> access to hardware with a GMU wrapper.
>>
>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>> ---
>> drivers/gpu/drm/msm/adreno/a6xx_gmu.c | 354 ++++++++++++++---------------
>> drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 6 -
>> drivers/gpu/drm/msm/adreno/a6xx_gpu.h | 3 -
>> drivers/gpu/drm/msm/adreno/adreno_device.c | 4 +
>> drivers/gpu/drm/msm/adreno/adreno_gpu.h | 4 +
>> drivers/gpu/drm/msm/msm_drv.c | 16 +-
>> 6 files changed, 192 insertions(+), 195 deletions(-)
>>
>
> Niel,
>
> Could you please send the follow up revision of this patch? Lets get
> this fix merged.
I'm really struggling on the separate_gpu_kms part, it's not trivial at all.
I'll try again and report my current status.
Neil
>
> -Akhil.
>
prev parent reply other threads:[~2026-01-14 8:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 12:44 Neil Armstrong
2025-10-22 17:09 ` Konrad Dybcio
2025-10-23 8:27 ` Neil Armstrong
2025-10-24 8:55 ` Konrad Dybcio
2025-10-24 9:11 ` Neil Armstrong
2025-10-30 9:52 ` Konrad Dybcio
2025-10-30 10:02 ` Neil Armstrong
2025-10-26 1:31 ` Jens Reidel
2025-10-29 10:25 ` Neil Armstrong
2025-11-04 1:30 ` Jens Reidel
2025-11-04 12:43 ` Neil Armstrong
2025-10-30 21:29 ` Akhil P Oommen
2025-10-31 8:38 ` Neil Armstrong
2026-01-14 6:37 ` Akhil P Oommen
2026-01-14 8:45 ` Neil Armstrong [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=e879d3a1-45d9-46f0-adaf-6bea243ab807@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=akhilpo@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jessica.zhang@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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®