From: Taniya Das <taniya.das@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Aaron Kling <webgeek1234@gmail.com>,
linux-arm-msm@vger.kernel.org,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>
Subject: Re: Questions About SM8550 Support
Date: Mon, 2 Feb 2026 15:05:27 +0530 [thread overview]
Message-ID: <60c970dc-141c-4a2e-aaee-719786371eee@oss.qualcomm.com> (raw)
In-Reply-To: <4d73907d-9915-44a7-99c7-2294c4be01b7@oss.qualcomm.com>
On 1/28/2026 7:33 PM, Konrad Dybcio wrote:
> On 1/27/26 11:48 PM, Aaron Kling wrote:
>> I am working on the AYN Odin 2 qcs8550 series of devices, specifically
>> for Android, using mainline kernel drivers. I have come across some
>> missing functionality and failures that I would like to inquire about.
>
> [...]
>
>> * Some gpu related clocks complain about being stuck off during boot,
>> causing stack traces, but the gpu does work. I tried to do some
>> research into this, but quickly got lost in the weeds and I have no
>> idea where to even look.
>> [ 0.367278] gpu_cc_cxo_clk status stuck at 'off'
>> [ 0.367962] gpu_cc_hub_cx_int_clk status stuck at 'off'
>> [ 0.368595] gpu_cc_cx_gmu_clk status stuck at 'off'
>> [ 0.369245] disp_cc_mdss_ahb1_clk status stuck at 'off'
>
Aaron, if you could share the boot up logs or stack traces it would be
helpful to see what is leading to stuck at 'off'.
--
Thanks,
Taniya Das
next prev parent reply other threads:[~2026-02-02 9:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 22:48 Questions About SM8550 Support Aaron Kling
2026-01-28 8:50 ` Neil Armstrong
2026-01-28 14:46 ` Rob Clark
2026-01-28 17:54 ` Aaron Kling
2026-01-29 23:11 ` Akhil P Oommen
2026-01-30 2:35 ` Aaron Kling
2026-02-05 8:01 ` Aaron Kling
2026-02-05 10:54 ` Konrad Dybcio
2026-02-05 13:29 ` Akhil P Oommen
2026-02-05 17:40 ` Aaron Kling
2026-03-10 21:33 ` Akhil P Oommen
2026-03-10 21:53 ` Aaron Kling
2026-03-11 8:47 ` Konrad Dybcio
2026-03-11 23:33 ` Aaron Kling
2026-02-05 14:43 ` Dmitry Baryshkov
2026-01-28 18:42 ` Aaron Kling
2026-02-06 15:04 ` Neil Armstrong
2026-01-28 14:03 ` Konrad Dybcio
2026-01-28 18:20 ` Aaron Kling
2026-02-02 9:35 ` Taniya Das [this message]
2026-02-02 23:01 ` Aaron Kling
2026-02-03 6:34 ` Jagadeesh Kona
2026-02-03 23:21 ` Aaron Kling
2026-02-04 16:53 ` Taniya Das
2026-02-04 18:18 ` Aaron Kling
2026-01-30 11:01 ` Konrad Dybcio
2026-01-30 17:13 ` Aaron Kling
2026-02-02 10:36 ` Konrad Dybcio
2026-02-02 23:12 ` Aaron Kling
2026-02-03 10:31 ` Konrad Dybcio
2026-02-03 17:31 ` Aaron Kling
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=60c970dc-141c-4a2e-aaee-719786371eee@oss.qualcomm.com \
--to=taniya.das@oss.qualcomm.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=webgeek1234@gmail.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