From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Tj <tj.iam.tj@proton.me>, Srinivas Kandagatla <srini@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-sound@vger.kernel.org
Subject: Re: qcom_slim_ngd_ctrl_probe: blocked on a mutex
Date: Fri, 13 Mar 2026 13:03:08 +0100 [thread overview]
Message-ID: <fb08be02-e73f-4efd-ac55-85ebe60a6e18@oss.qualcomm.com> (raw)
In-Reply-To: <539a5f37-e06f-44be-abda-3afa69397711@proton.me>
On 3/13/26 1:00 PM, Tj wrote:
> On 13/03/2026 09:54, Konrad Dybcio wrote:
>> On 3/12/26 1:14 AM, Tj wrote:
>>> Currently working on sdm850 device (Samsung Galaxy Book2 W737) and
>>> seeing kernel hang early and never recover when probing qcom-ngd-ctrl
>>> platform driver. Only able to capture a photo of the stack traces as a
>>> result; I'll try to transcribe the important parts here. My diagnosis
>>> suggests that the module is calling __platform_driver_register() twice
>>> and may be the cause of the hang.
>> https://lore.kernel.org/all/20260309-slim-ngd-dev-v1-0-5843e3ed62a3@oss.qualcomm.com/
>>
>> should be able to help with some of that
>
> Thank-you. This morning I'd just resolved the platform_driver_register
> issue myself so now seeing
>
> qcom,slim-ngd-ctrl 171c0000.slim-ngd: SLIM SAT: Rcvd master capability
> qcom,slim-ngd-ctrl 171c0000.slim-ngd: SLIM controller Registered
>
> However the order of registration of the two drivers is important; ctrl
> should be last, so I'm surprised that Patch 1 works.
Please direct your findings to that thread.
Konrad
prev parent reply other threads:[~2026-03-13 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 0:14 qcom_slim_ngd_ctrl_probe: blocked on a mutex Tj
2026-03-13 9:54 ` Konrad Dybcio
2026-03-13 12:00 ` Tj
2026-03-13 12:03 ` Konrad Dybcio [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=fb08be02-e73f-4efd-ac55-85ebe60a6e18@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=srini@kernel.org \
--cc=tj.iam.tj@proton.me \
/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